Request reviews after appointments
When an appointment is completed in Launch27, send a review request from SoTellUs.
Google for Startups AcceleratorHow Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
SoTellUs Explore SoTellUs →
TriggersFires when a customer leaves a new review in SoTellUs.
Fires when a review is edited or answered in SoTellUs.
Fires when a customer answers a feedback survey in SoTellUs.
Invites a customer to leave a review with SoTellUs.
Adds or updates a customer contact in SoTellUs.
Posts a public reply to a review in SoTellUs.
Launch27 Explore Launch27 →
TriggersFires when a new booking or appointment is made in Launch27.
Fires when a booking in Launch27 is changed or canceled.
Fires when a new customer books for the first time in Launch27.
Creates a new booking or appointment in Launch27.
Cancels or moves a booking in Launch27.
Creates or updates a customer record in Launch27.
Adds a booking from Launch27 to a connected calendar.
More SoTellUs + Launch27 workflows
See all SoTellUs + Launch27 integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Request reviews after appointments” between SoTellUs and Launch27?
Yes — describe it in the box above and Knit's Integrations Agent researches SoTellUs and Launch27's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
Can a completed appointment trigger a review request?
Yes. When a booking ends in Launch27, SoTellUs can send a review request.
Are customers synced?
New booking customers in Launch27 can be created or updated in SoTellUs.