Niches · Calendars & scheduling

React when a booking is made, moved or cancelled

One company's docs show a full fit.

1companies, full fit
13companies, fit with a limit
14companies carry the tag
6share of the category's work
3first-hand accounts

What counts as done

Each create, change and cancel reaches the endpoint with enough data to act, or with a documented way to fetch it, and failed deliveries are retried on a published schedule with a visible signal when the subscription is disabled or expires.

How agents ask for it: tell me when someone books, when a slot is cancelled offer it to the waitlist, sync new bookings into the CRM, charge for the session once it is booked

Does the job 1

The docs show it meets the test above, and nothing we read says otherwise.

ListingWhy
Aurinko Calendar API F
Yoxel, Inc.
Calendar event subscriptions; retries at 1, 2, 4, 8 seconds capped at 10-minute intervals, and lifecycle events report error and active when a subscription breaks or recovers. Payload format documented per resource. source

Does the job, with a limit 13

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
Acuity Scheduling API E
Squarespace, Inc.
Scheduled, rescheduled, canceled and changed webhooks carry the id to fetch; retry table over 24 hours, disabled after 5 days with a status field on dynamic subscriptions. API and webhooks sit on Premium. source
Apiroc Unified Calendar API E
UTC Labs
calendar.event.changed webhooks through Svix, then fetch with syncToken. No retry schedule or expiry signal on Apiroc's pages, and no webhooks for iCloud or CalDAV. source
Cal.com API v2 + MCP D
Cal.com, Inc.
BOOKING_CREATED, RESCHEDULED and CANCELLED webhooks with versioned payloads and dedupe on payload.eventId. The guide says delivery can retry but publishes no schedule or disabled-subscription signal. source
Calendly API + MCP BB
Calendly, LLC
Invitee created and canceled webhooks, on all plans per the help centre (acc-26 says paid). No retry schedule or disabled-subscription alert on readable pages; acc-25 asked and got no answer. source
Cronofy API B
Cronofy Limited
Push channels send change notifications to fetch with changes_since, plus profile_disconnected. Delivery is retried for 24 hours with no published intervals, then the channel closes with no notice. source
Google Calendar API A
Google LLC
events.watch channels carry an expiration and must be renewed; notifications have no body, so the change is fetched with a sync token (acc-45, Stack Overflow, which robots.txt closed to me). No retry schedule found on the push guide. source
Microsoft Graph Calendar API C
Microsoft Corporation
Subscriptions retry failed deliveries with exponential backoff for up to 4 hours and send reauthorizationRequired, subscriptionRemoved and missed lifecycle events. Subscriptions expire and need renewal, and slow endpoints can have notifications dropped. source
Nylas Calendar and Scheduler API A
Nylas, Inc.
Webhooks retry temporary failures up to 5 attempts and drop other errors; endpoints marked failing or failed trigger an email to listed addresses. Attempt intervals aren't stated. source
Reclaim.ai E
Reclaim.ai Inc.
Signed webhooks fire on Scheduling Link bookings, reschedules and cancels with meeting and attendee data, on Business and Enterprise only. No retry schedule or disabled-subscription signal published. source
SavvyCal API + MCP C
SavvyCal, Inc.
Signed event.created, event.rescheduled and event.canceled webhooks with event payloads. No retry schedule or disabled-subscription signal documented. source
Truto Unified Calendar API C
Yin Yang Inc.
Truto webhooks retry five times within five minutes on a published schedule; calendar changes arrive only where a vendor-webhook mapping exists, which the calendar pages don't confirm. source
YouCanBookMe API F
AI Software (Capacity) UK Ltd
Notification webhooks fire on booking, reschedule, cancel, reminders, follow-ups and no-shows with a payload built from shorthand codes. No retry schedule or failure signal is described, and webhooks need Professional or Teams. source
Zoom Scheduler API D
Zoom Communications, Inc.
Only scheduled_event_created and scheduled_event_canceled webhooks, no reschedule event. Zoom retries three times at 5, 20 and 60 minutes and disables a subscription after failed revalidation. source

Doesn't do this job 2

Listings in the category that do something else, with the reason.

ListingWhy
Agenda Hero F
Agenda Hero, Inc.
No webhook or push subscription is documented. source
Cozi Family Organizer F
Cozi, Inc.
No webhooks or push; a subscribing calendar refreshes the feed on its own schedule. source

What stops agents finishing

  • webhooks only on a paid plan
  • subscription disabled silently after failed deliveries
  • push channel expires and must be renewed

Around it

Before: scheduling.book-slot. After: crm.log-activity, payment-platforms.charge, messaging.send-sms.

Where this comes from

Weight 6 of 100 in Calendars & scheduling: 3 of 51 links; Calendly community and Stack Overflow; thin evidence

The same as data: /api/v1/use-cases/scheduling.watch-changes.json, or the MCP tool get_use_case with id scheduling.watch-changes. Other jobs in this category: /api/v1/niches?category=scheduling.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.