Solution
Fan out booking confirmations to calendars, notifications, and CRM
A scheduled appointment or reservation often needs to update a calendar, send a confirmation, and log into a CRM. API Rabbits turns that one booking event into all three, reliably.
The scenario
A scheduling tool, booking form, or internal system creates a confirmed booking. That single event needs to add or update a calendar entry, send the customer a confirmation, and record the booking in a CRM for follow-up — three destinations from one event.
Example routing rule
Only sync to the shared team calendar and notify the on-call Slack channel for bookings where "service" equals "consultation"; log every booking type to the CRM.
POST /v1/p/bookings-example
{
"booking_id": "bk_7712",
"customer_email": "morgan@example.com",
"start_time": "2026-09-02T15:00:00Z",
"service": "consultation"
}Fans out to:
- Calendly / Custom HTTP — Sync the booking into a calendar system.
- Email — Send a confirmation to the customer.
- HubSpot / Salesforce — Log the booking against the contact record for follow-up.
One booking event, every downstream system updated
The scheduling tool only has to know about your rabbit — everything downstream (calendar, confirmation email, CRM) is configured separately and can change without touching the booking flow.
Reliable confirmations
A slow email provider doesn't stop the calendar sync, and a calendar outage doesn't stop the confirmation email — each destination retries independently.
Full visibility into what was sent
The activity log shows exactly which bookings reached which systems and when, useful for tracking down a missed confirmation or calendar entry.