Real events, not polling
A Zap subscribes once and Boris pushes each new booking, payment or check-in as it occurs.
Integrations
Boris events in any Zap, with retries you can inspect
Boris publishes its operational events over REST hooks: a Zap subscribes to the events it cares about and receives them as they happen, with the same delivery log and retry behaviour as the webhook integration.
Integration status
Provider website ↗
Available Running against the provider’s production API.
What it gives you
Boris events in any Zap, with retries you can inspect
Deliveries you can audit
Every attempt is recorded, so a failed Zap is visible instead of silently missing.
No developer needed
Connect a CRM, a spreadsheet or an email sequence without touching the codebase.
How to connect it
How to connect it
- 1
Open Integrations, enable Zapier and copy your API key.
- 2
Create a Zap with Boris as the trigger and pick the event you want.
- 3
Map the payload fields into the app on the other side and turn the Zap on.
Frequently asked questions
Frequently asked questions
Which events can trigger a Zap?
The operational ones: bookings created, modified and cancelled, payments, check-ins and the automation events Boris already emits.
What happens if the Zap is down?
The delivery is retried and the attempts are kept in the delivery history, so nothing disappears without a trace.
Related integrations
Connect it to your own space
Create a workspace, add your resources and connect the tools you already pay for. No credit card required.
Create your workspace