Mirror booking cancellations across calendar tools
When a client reschedules or cancels a booking in CaptainBook.io, automatically update or cancel the corresponding booking in i-Reserve to keep schedules accurate.
See all i-Reserve + CaptainBook.io integrations or talk to a human
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.
i-Reserve Explore i-Reserve →
TriggersFires when a new booking or appointment is made in i-Reserve.
Fires when a booking in i-Reserve is changed or canceled.
Fires when a new customer books for the first time in i-Reserve.
Creates a new booking or appointment in i-Reserve.
Cancels or moves a booking in i-Reserve.
Creates or updates a customer record in i-Reserve.
Adds a booking from i-Reserve to a connected calendar.
CaptainBook.io Explore CaptainBook.io →
TriggersFires when a new booking or appointment is made in CaptainBook.io.
Fires when a booking in CaptainBook.io is changed or canceled.
Fires when a new customer books for the first time in CaptainBook.io.
Creates a new booking or appointment in CaptainBook.io.
Cancels or moves a booking in CaptainBook.io.
Creates or updates a customer record in CaptainBook.io.
Adds a booking from CaptainBook.io to a connected calendar.
More i-Reserve + CaptainBook.io workflows
Sync client appointments across scheduling platforms
When a new booking is made in i-Reserve, automatically create a corresponding booking and add it to the calendar in CaptainBook.io.
See details
Sync new customer profiles between booking systems
When a new customer books an appointment in i-Reserve, automatically create or update their customer record in CaptainBook.io.
See details
See all i-Reserve + CaptainBook.io integrations → · Browse the full workflow library →
Common questions
Can Knit build “Mirror booking cancellations across calendar tools” between i-Reserve and CaptainBook.io?
Yes — describe it in the box above and Knit's Integrations Agent researches i-Reserve and CaptainBook.io'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.
Why would I connect i-Reserve to CaptainBook.io if they both handle bookings?
Businesses often use separate tools for internal resources and client-facing bookings; syncing i-Reserve and CaptainBook.io ensures time slots and client details are consistent across both.
What happens in CaptainBook.io when a client reschedules in i-Reserve?
Rescheduling or canceling a meeting in i-Reserve automatically updates or cancels the matching booking in CaptainBook.io, freeing up availability immediately.