Cal.com + SalesCrew
Cal.com posts its booking webhook to the same inbound endpoint Calendly uses. You map the fields once, and bookings land on the record.
Want to see it first? Book a demo
- Webhook into the inbound endpoint
- Or via Zapier, Make or n8n
- Meetings readable over MCP
The short answer
- Point a Cal.com webhook at your instance's inbound endpoint, or route it through Zapier, Make or n8n and call meeting_create with the fields you want.
- Each booking becomes a meeting on the contact, with its source recorded. That keeps the join between spend and booked meetings in one database.
- The Cal.com connector syncs created, cancelled and rescheduled bookings onto the meeting record, and reminders go out by SMS and email at 24 hours and 2 hours before the start.
Mechanism
The routes a Cal.com booking takes into SalesCrew.
| What | Mechanism | Direction | Objects | Status |
|---|---|---|---|---|
| Booking into SalesCrew | Cal.com webhook to the inbound endpoint, fields mapped by you | Inbound | Meetings, contacts, leads | Available |
| Booking via an automation tool | Cal.com to Zapier, Make or n8n, then meeting_create over MCP | Inbound | Meetings, contacts | Available |
| Agent access to bookings | meeting_list and booking_list over MCP | Read | Meetings, bookings | Available |
| Cal.com connector | Booking sync for created, cancelled and rescheduled events | Inbound | Meetings, contacts | Available |
| Reminders that send | SMS and email at 24h and 2h | Outbound | Meetings | Available |
Mechanisms read from the SalesCrew integration table, September 2026. Cal.com's own documentation is the authority on its webhook payloads.
Setup, step by step
Roughly half an hour, most of it spent mapping fields.
- 1
Decide the route
Straight to the inbound endpoint if the payload maps cleanly, or through an automation tool if you want to reshape it first.
- 2
Create the Cal.com webhook
Subscribe to booking created, cancelled and rescheduled events and point it at the URL you chose.
- 3
Map to a meeting and a contact
You need at least the invitee email, the start time and the event type. The email is what matches or creates the contact.
- 4
Record the source
Put the booking source in the payload. Without it you lose the join between spend and booked meetings, which is the main reason bookings live in the CRM at all.
- 5
Test with a real booking
Book through the public link with a spare address. A synthetic payload proves the plumbing but not the matching.
- 6
Add a retry path
If you route through an automation tool, give it an error path so a failed delivery is visible rather than lost.
Questions
- Does Calendly connect the same way?
- Calendly has its own connector plus a reconcile job that re-reads missed bookings. Cal.com has its connector, or a webhook you wire once into the inbound endpoint.
- Can I self-host Cal.com and still connect?
- Yes, since the mechanism is an outgoing HTTP POST from your Cal.com to your SalesCrew instance. Both ends are yours, which suits teams that self-host on principle.
- What does SalesCrew cost?
- Tiers are $299, $699 and $1,200 a month, with unlimited seats on every tier. The trial runs 14 days and needs a card.
- Is the meeting visible to an agent?
- Yes. meeting_list and booking_list read the same rows any screen shows, under a token you scope and can revoke.
Wire the webhook once, and every booking lands
Cal.com through its connector or the inbound endpoint, Calendly through its own connector. Both end on the record.
Want to see it first? Book a demo