A built Cal.com connector is a later roadmap item. What works today is a generic webhook into the inbound endpoint, which you configure yourself.

Cal.com + SalesCrew

No connector yet. Cal.com can post its booking webhook to the same inbound endpoint Calendly uses, and you map the fields yourself.

app.salescrew.io/settings

The short answer

SalesCrew has a built connector for Calendly and not for Cal.com. Cal.com is a later roadmap item, so anything working today is your own webhook rather than a supported feature.
The workable path: 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 on the record.
The tested path is Calendly, including a reconcile job that re-reads bookings when a webhook fails to deliver. Cal.com has no equivalent safety net here yet.

What you can build today, and what is not built for you.

What	Mechanism	Direction	Objects	Status
Built Cal.com connector	Does not exist	None	None	Later on the roadmap
Booking into SalesCrew	Cal.com webhook to the inbound endpoint, fields mapped by you	Inbound	Meetings, contacts, leads	You configure it
Booking via an automation tool	Cal.com to Zapier, Make or n8n, then meeting_create over MCP	Inbound	Meetings, contacts	Available
Reconcile job for missed webhooks	Built for Calendly only	None	None	Not available for Cal.com
Writing availability back	Not built for any scheduler	None	None	Not available
Reminders that send	Not built for any scheduler	None	Meetings	On the roadmap

Mechanisms read from the SalesCrew integration table, September 2026. Cal.com's own documentation is the authority on its webhook payloads.

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 your own retry
There is no reconcile job for Cal.com. If you route through an automation tool, give it an error path so a failed delivery is visible rather than lost.

Should I use Calendly instead?: If bookings matter and you want a path that is built and tested, yes. Calendly has a connector plus a reconcile job. Cal.com is a webhook you wire yourself.
When will a Cal.com connector ship?: There is no date. It sits in the later group on the roadmap, and roadmap items are stated as intentions without dates.
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.
Do bookings trigger reminders?: Not yet. Meetings and reminder records exist, but reminders and no-show recovery that actually send are on the roadmap.
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.

Cal.com works if you build it; Calendly works because it was built and tested.