When booking cancelled in Bokun, sync it to Connecteam.
Update shift schedules or task assignments in Connecteam when a booking is cancelled in Bokun.
4.9/5 on G2·
Google for Startups Accelerator
How 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.
Bokun Explore Bokun →
TriggersFires when a new booking or appointment is made in Bokun.
Fires when a booking in Bokun is changed or canceled.
Fires when a new customer books for the first time in Bokun.
Creates a new booking or appointment in Bokun.
Cancels or moves a booking in Bokun.
Creates or updates a customer record in Bokun.
Adds a booking from Bokun to a connected calendar.
Connecteam Explore Connecteam →
TriggersFires when a new employee is added in Connecteam.
Fires when a field on an employee's profile changes in Connecteam.
Fires when an employee is offboarded in Connecteam.
Fires when an employee requests time off in Connecteam.
Creates a new employee record in Connecteam.
Updates a field on an employee's record in Connecteam.
Syncs an employee's active/terminated status in Connecteam.
Approves or denies a time-off request in Connecteam.
Common questions
Can Knit build “When booking cancelled in Bokun, sync it to Connecteam.” between Bokun and Connecteam?
Yes — describe it in the box above and Knit's Integrations Agent researches Bokun and Connecteam'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.