A practical field guide from Automation Ace.
Short answer: to turn Cal.com bookings into fully automated workflows, map every booking event (created, rescheduled, cancelled, meeting ended, no-show), use Cal.com Workflows for reminders and follow-up messages, and use a Cal.com webhook or the Cal.com app in Zapier, Make, or n8n to update your CRM, notify your team, and create tasks. Store the booking's unique ID on every record so reschedules and cancellations update the same records, deduplicate webhook deliveries, and test every path, not just new bookings.
Short answer
- List each booking event and what should happen.
- Messages in Cal.com Workflows; multi-app steps in Zapier, Make, n8n, or code.
- Subscribe to the webhook triggers you need, with a secret.
- Key everything on the booking UID and the attendee email.
- Treat reschedules and cancellations as updates.
- Test, then monitor failures.
Step 1: Map the booking lifecycle
| Booking event | Cal.com webhook trigger | Typical automated actions |
|---|---|---|
| New booking | BOOKING_CREATED | Find or create CRM contact, log meeting, notify owner, create prep task |
| Booking needs approval | BOOKING_REQUESTED | Notify the approver; hold related steps until confirmed |
| Rescheduled | BOOKING_RESCHEDULED | Update dates in CRM and tasks; move reminders |
| Cancelled | BOOKING_CANCELLED | Update stage, release resources, send a rebook link |
| Meeting started | MEETING_STARTED | Start a timer or log attendance |
| Meeting ended | MEETING_ENDED | Send follow-up, request feedback, create next-step task |
| No-show marked | BOOKING_NO_SHOW_UPDATED | Send rebooking message, tag contact, alert host |
| Routing form submitted | FORM_SUBMITTED | Log the lead even if they never book |
Trigger names reflect Cal.com's API documentation at the time of writing; check the current list in your webhook settings. Webhook basics: what a webhook is.
Step 2: Choose the right layer for each step
| Layer | Best for | Examples |
|---|---|---|
| Cal.com Workflows | Messages tied to the booking | Confirmations, reminders, post-meeting emails, SMS or WhatsApp on eligible plans |
| Zapier, Make, or n8n | Multi-app steps without code | CRM updates, Slack alerts, tasks, spreadsheets, invoices |
| Webhooks to your code | Custom logic, high volume, your own systems | A serverless function that updates your database and calls APIs |
Keep messages to the attendee in Cal.com where possible, so they move automatically when a booking changes. Use automations for everything that touches other apps.
Step 3: Set up Cal.com Workflows for messages
- In Cal.com, open Workflows and create a new workflow.
- Pick the event types it applies to.
- Choose a trigger: new booking, before the event starts, after the event ends, cancelled, or rescheduled.
- Add actions: email the attendee or host, or SMS / WhatsApp where your plan allows (verify phone numbers first).
- Use variables such as the attendee name, event time, and location in the message.
Free plans may be limited to default reminder emails; custom workflows and SMS depend on your plan.
Step 4: Add a webhook or automation trigger
- No-code: use the Cal.com app trigger in Zapier, Make, or n8n, or a Catch Hook URL as a Cal.com webhook subscriber.
- Code: add a webhook in Cal.com's settings (or via API v2) pointing to your endpoint, choose the triggers, and set a secret so you can verify the
x-cal-signature-256header. - Scope: webhooks can be set per user, per event type, or per team, so subscribe only where needed.
Hosting a handler: receiving webhooks with Cloudflare Workers.
Example: a complete booking Zap
Zap: Cal.com booking -> CRM -> Slack -> task
Trigger Cal.com: New booking (or Webhooks by Zapier: Catch Hook)
Step 1 HubSpot: Find contact by attendee email
Step 2 Paths: found -> Update contact | not found -> Create contact
Step 3 HubSpot: Create meeting / engagement with start time and link
Step 4 Formatter: pull answers ("Company", "Goal") from responses
Step 5 Slack: post to #sales-meetings with name, company, time, prep notes
Step 6 Asana / Todoist: "Prep for call with {name}" due 1 hour before
Parsing booking answers: the same techniques as parsing Calendly questions in Zapier apply.
Example: a webhook handler
// Webhook handler sketch (Node.js). Check field names against Cal.com's docs.
export async function handleCalWebhook(rawBody, headers) {
verifySignature(rawBody, headers["x-cal-signature-256"], process.env.CAL_WEBHOOK_SECRET);
const evt = JSON.parse(rawBody);
const type = evt.triggerEvent; // e.g. "BOOKING_CREATED"
// Most booking events nest details under evt.payload; meeting started/ended
// events have been documented with booking fields at the top level.
const b = evt.payload ?? evt;
const key = `${type}:${b.uid ?? b.bookingId}`;
if (await alreadyProcessed(key)) return; // webhooks can repeat
switch (type) {
case "BOOKING_CREATED": return onCreated(b);
case "BOOKING_RESCHEDULED": return onRescheduled(b);
case "BOOKING_CANCELLED": return onCancelled(b);
case "MEETING_ENDED": return onEnded(b);
case "BOOKING_NO_SHOW_UPDATED": return onNoShow(b);
}
}
Step 5: Handle reschedules, cancellations, and no-shows
- Reschedule: look up records by booking UID and update dates; move prep tasks; do not create a second meeting.
- Cancel: update the CRM, cancel prep tasks, send a rebooking link if appropriate.
- No-show: trigger a rebooking message and tag the contact for follow-up.
- Pending meeting webhooks: Cal.com has documented that cancelling or rescheduling cancels scheduled meeting start and end webhooks for that booking, so your follow-ups stay in step.
Step 6: Reliability checklist
| Check | Why |
|---|---|
| Store the booking UID on every record you create | So reschedules, cancellations, and follow-ups update the right record |
| Use the attendee's email as the CRM match key | Avoids duplicate contacts |
| Convert times with the booking's time zone | Reminders and tasks land at the right local time |
| Deduplicate by event type plus booking UID | Webhooks and automations can run twice |
| Handle reschedules as updates, not new bookings | Otherwise you get two meetings in the CRM |
| Test cancel and reschedule paths, not just new bookings | Most bugs live there |
Related: why a webhook fires twice and duplicate records.
Step 7: Test and monitor
- Book, reschedule, cancel, and mark a no-show on a test event type.
- Confirm every record updates once and only once.
- Send errors to one alert channel; see error handling.
- Review a week of bookings for missed or duplicate steps.
Ideas for what to build first: 5 Cal.com automations that eliminate manual scheduling tasks. Adding AI: AI-powered appointment scheduling with Cal.com.
Frequently asked questions
How do I automate Cal.com bookings?
Use Cal.com Workflows for confirmations, reminders, and follow-up messages, and use a Cal.com webhook or the Cal.com app in Zapier, Make, or n8n to update your CRM, notify your team, and create tasks when bookings are created, rescheduled, cancelled, or end.
What webhook events does Cal.com support?
Cal.com’s documentation lists triggers such as BOOKING_CREATED, BOOKING_REQUESTED, BOOKING_RESCHEDULED, BOOKING_CANCELLED, MEETING_STARTED, MEETING_ENDED, BOOKING_NO_SHOW_UPDATED, and FORM_SUBMITTED, among others. Check your webhook settings for the current list.
How do I handle Cal.com reschedules in an automation?
Store the booking’s unique ID on every record you create, then look records up by that ID when a reschedule event arrives and update dates instead of creating a new meeting.
How do I verify Cal.com webhooks?
Set a secret when you create the webhook, then verify the signature header on each delivery (documented as x-cal-signature-256) using that secret before processing the payload.
Should I use Cal.com Workflows or Zapier?
Use Cal.com Workflows for messages tied to the booking, such as reminders, because they move with reschedules. Use Zapier, Make, or n8n for steps in other apps, such as CRM updates, Slack alerts, and tasks.
Disclaimer: Cal.com features, plans, API versions, and credit pricing change; details reflect public documentation and coverage at the time of writing, so confirm current details with each provider before building. Automation Ace is not affiliated with Cal.com beyond the referral links marked on this page. This article may include links to apps, products, or services; some links may be affiliate links, which means Automation Ace may earn a commission at no extra cost to you.