Skip cancelled bookings
When a booking is cancelled in Dispatch, remove the pending review request in pulseM.
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.
pulseM Explore pulseM →
TriggersFires when a customer leaves a new review in pulseM.
Fires when a review is edited or answered in pulseM.
Fires when a customer answers a feedback survey in pulseM.
Invites a customer to leave a review with pulseM.
Adds or updates a customer contact in pulseM.
Posts a public reply to a review in pulseM.
Dispatch Explore Dispatch →
TriggersFires when a new booking or appointment is made in Dispatch.
Fires when a booking in Dispatch is changed or canceled.
Fires when a new customer books for the first time in Dispatch.
Creates a new booking or appointment in Dispatch.
Cancels or moves a booking in Dispatch.
Creates or updates a customer record in Dispatch.
Adds a booking from Dispatch to a connected calendar.
More pulseM + Dispatch workflows
See all pulseM + Dispatch integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Skip cancelled bookings” between pulseM and Dispatch?
Yes — describe it in the box above and Knit's Integrations Agent researches pulseM and Dispatch'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 Dispatch, pulseM can send a review request.
Are customers synced?
New booking customers in Dispatch can be created or updated in pulseM.