Update records on reschedules
When a booking is rescheduled or cancelled in Dispatch, update the record in Adalo.
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.
Adalo Explore Adalo →
TriggersFires when a new record is added to an app built in Adalo.
Fires when a record changes in an Adalo app.
Fires when a record is deleted in an Adalo app.
Adds a new record to an app built in Adalo.
Updates an existing record in an Adalo app.
Removes a record from an Adalo app.
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 Adalo + Dispatch workflows
See all Adalo + Dispatch integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Update records on reschedules” between Adalo and Dispatch?
Yes — describe it in the box above and Knit's Integrations Agent researches Adalo 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 bookings create records?
Yes. When an appointment is booked in Dispatch, Adalo can create a record with the time, customer and service.
What happens on cancellations?
When a booking is cancelled or rescheduled in Dispatch, the matching record in Adalo can be updated.