Calendly CRM Integration: Native CRMs and How to Wire the Rest
What Calendly's HubSpot, Salesforce and Dynamics 365 integrations do and which Calendly plan each needs, how to connect any other CRM, and how to handle reschedules, repeat bookers and no-shows.

by Benjamin WagnerCalendly has native integrations with three CRMs: HubSpot from its Standard plan, Salesforce on Teams or Enterprise, and Microsoft Dynamics 365 with Power Automate on Enterprise. Every other CRM connects through an app in that CRM's marketplace, a connector platform such as Zapier or Zoho Flow, or Calendly's webhooks. Webhooks need a paid Calendly plan, and you create them through Calendly's API, not in its settings.
Whichever route you take, decide before you build what one booking should create in the CRM and what a reschedule should change. The reschedule is the easy part to get wrong, because Calendly reports it as a cancellation plus a new booking.
Customermates, an AI-native CRM, publishes this guide. Customermates has no Calendly connector of its own; the section on it below shows the three routes that work instead. Vendor details were checked on 8 October 2026 on the vendors' own pages, linked at the end.
- HubSpot, Salesforce and Microsoft Dynamics 365, each tied to a specific Calendly plan.
- A marketplace app, a connector platform such as Zapier, Zoho Flow or n8n, or your own webhook receiver.
- Not on Calendly's Free plan, and created through the API. The core events are invitee.created, invitee.canceled and routing_form_submission.created.
- A reschedule fires a cancellation and a new booking. Check the rescheduled flag before you close a deal as cancelled.
- REST API on every plan, webhooks on every paid plan. On Pro and higher in Customermates Cloud, the booked meeting also arrives through the host's connected Google or Outlook calendar.
What Calendly's native CRM integrations do
| CRM | Calendly plan | What it does, according to Calendly |
|---|---|---|
| HubSpot | Standard, Teams or Enterprise | Creates and updates contacts and leads when a meeting is booked, logs activities including reschedules and cancellations, and adds answers to booking questions to the HubSpot record. Teams adds routing by HubSpot assignment. |
| Salesforce | Teams or Enterprise | Creates a lead, contact or opportunity for a new prospect, creates events or tasks on any Salesforce object, maps booking data to a custom object and routes known leads to their Salesforce owner. Enterprise can limit the sync to specific groups, such as the sales team. |
| Microsoft Dynamics 365 | Enterprise | Listed on the pricing page as "Microsoft Dynamics 365 and Power Automate for CRM workflows". Calendly gives no further detail there. |
Two details matter when you choose. Calendly's HubSpot page talks about contacts, leads, activities and routing, and says nothing about deals. If every booking should open a deal in HubSpot, test that before you rely on it. Both pages also describe logging meeting summaries from Calendly Notetaker to the record, which only applies to meetings recorded with it.
If your CRM is on this list and your Calendly plan qualifies, start with the native integration. There is nothing extra to run, and Calendly maintains it.
Connecting a CRM that Calendly does not support natively
Searches like "Calendly Pipedrive integration" or "Calendly Freshworks integration" end in one of four routes:
| Route | Example | Choose it if | Watch for |
|---|---|---|---|
| App in the CRM's marketplace | Pipedrive Marketplace lists Calendly Sync by Outfunnel, which creates contacts, leads, deals, activities or notes. The Freshworks Marketplace lists Calendly Events for CRM. | An app exists for your CRM and covers what you need | Third-party apps have their own terms. The Freshworks app works the other way round: it schedules, reschedules and cancels Calendly events from inside the CRM. |
| Connector platform | Zapier's trigger "Invitee Created or Rescheduled", or Zoho Flow from "Event scheduled by invitee" to "Create or update contact" in Zoho CRM | Nobody on the team writes code, and your CRM has a connector on the platform | One more account to pay for and watch. Check how the trigger treats reschedules. |
| Webhooks into n8n or your own code | n8n's Calendly Trigger node, with the events "Event created" and "Event canceled" | You need lookups and branching, or your CRM has no connector anywhere | Someone has to run and monitor it. n8n can be self-hosted or used as n8n Cloud. |
| AI client with two MCP connectors | Calendly's MCP server in Claude or ChatGPT, next to your CRM's connector | You review bookings in batches and want to confirm each write | It runs when someone asks. It is not a sync. |
The long tail of CRMs (Keap, Agile CRM, LeadConnector, Pipeline CRM and many more) usually sits in the first two rows. Search the CRM's own marketplace first, then Zapier's Calendly page.
What one booking should create
Calendly's API gives you the invitee's name, email and answers to custom questions, plus the event type, the host and the start time. Map them before you build anything:
| Calendly data | Where it goes in the CRM | Why |
|---|---|---|
| Invitee email | Contact email, used as the lookup key | Repeat bookers must find their existing contact |
| Invitee name | Contact first and last name | Most CRMs keep these as two fields |
| "Company" question | Organization, found or created | The contact and deal then sit under the account |
| Other questions with fixed choices | A select field on the deal | You can filter and group by it later |
| Free-text answers | The deal's notes | Free text in a select field breaks filtering |
| Event type | Deal name and a lead-source field | Shows which booking page brings deals |
| Host | Deal owner or assigned user | Round-robin bookings land with the right person |
| Start time | A date field on the deal | Lets you sort upcoming calls in a list view |
| Calendly invitee or event link | A text field on the deal | Lets a later cancellation find the right deal |
The last row is the one people skip, and it is the one the cancellation step needs.
Reschedules, repeat bookers and no-shows
- Reschedules. When an invitee reschedules, Calendly fires invitee.canceled for the old time and invitee.created for the new one. The cancellation carries
rescheduled: true, and the new booking points back to the old one throughold_invitee. A workflow that ignores the flag marks the deal as cancelled and then opens a second one. - Repeat bookers. Search the CRM for the email before you create a contact, and lowercase it first. People type their address differently from one booking to the next.
- No-shows. Zapier offers the Calendly trigger "Invitee No Show Created". Calendly's webhooks overview lists only bookings, cancellations and routing-form submissions, so if you build on webhooks, plan to mark no-shows by hand. Moving the deal to a no-show stage beats guessing from a timer.
- Routing forms. routing_form_submission.created fires when someone submits a routing form, even if no meeting is booked. Use it to capture people who qualified but never picked a time. The subscription has to use organization scope.
Where Customermates fits
Customermates is a source-available, AI-native CRM for small client-facing teams such as consultancies and agencies. It has no Calendly connector, so bookings come in through one of three routes.
Route 1: Calendly webhooks into the REST API
This works on every Customermates plan and on a self-hosted installation. You need a Calendly plan with webhooks and a place to run the workflow. The example uses n8n, which runs separately and is not part of Customermates.
Create an API key
In Customermates, open Settings › API keys & connectors, click Add and choose Standard API key. The key acts with your permissions. In n8n, store it as a Header Auth credential with the header name
x-api-key. See API keys.Prepare the deal fields
Open Deals in Data model and add a "Call booked" and a "Cancelled" option to the Stage field, which is a Single choice field. Add a Date and time field "Meeting", a Single choice field "Lead source" with one option per event type, and a Text field "Calendly booking".
POST /api/v1/model/discoverfinds the type IDs of Contacts and Deals, andPOST /api/v1/model/readreturns the schema revision and the field, option and relationship IDs the API expects. These IDs stay valid when someone renames a list or field.Receive the booking
Add n8n's Calendly Trigger with "Event created" and "Event canceled". Alternatively, use a Webhook node and subscribe its URL through Calendly's API.
Find or create the contact
Send
POST /api/v1/records/identities/resolvewith the invitee's email as amailidentifier; it returns only exact matches. If there is none, sendPOST /api/v1/records/mutatewith acreatemutation for Contacts: first and last name as typed field values andidentities: [{ "provider": "mail", "value": "<email>" }].Create the deal
Send a
createmutation for Deals toPOST /api/v1/records/mutate, with a name such as "Anna Weber, intro call", the host's Customermates user ID inassignedUserIds, and typed values for stage, meeting time, lead source and the Calendly link. Link the contact through the relationship ID frommodel/read. Free-text answers go into the deal's notes, a Formatted text field: add them with anupdatemutation whose field entry{ fieldId, append }takes Markdown. Use the Calendly event ID in theidempotencyKey, and map host emails to user IDs once, in the workflow.Handle the cancellation
On invitee.canceled, find the deal by its "Calendly booking" value with
POST /api/v1/records/queryand aneqfilter (see filter syntax). Ifrescheduledis true, update "Meeting" from the new booking. If it is false, send anupdatemutation with the deal's record reference and current version that sets the stage to "Cancelled".
Customermates does not block a second contact with the same address, because one email can belong to several records. Resolve the email before every create, and keep the Calendly event ID as the idempotency key, so a retried delivery returns the first result instead of creating a second record. The n8n guide lists every endpoint and the rules for links and retries.
Route 2: the calendar, on Pro and higher in Customermates Cloud
If Calendly is set to send Calendar Invitations, the host's Google or Outlook calendar creates the event and adds the invitee as a guest. Connect that same account in Customermates under Settings › Channels & calendars with Connect channel, and the meeting arrives without any workflow tool. Calendar events appear in an activity timeline, and on the record of a contact whose email matches a guest. Customermates only reads the calendar. It never books or changes meetings.
To turn bookings into records, a routine can sweep the calendar. Routines run in Customermates Cloud only and use hosted AI credits from the owner's monthly allowance. Choose On a schedule, set Repeats to Every hour, and give it instructions like these:
Look at my calendar events that start in the next 14 days. For each event with a guest whose email does not end in @ourfirm.com, find the contact by that email or create one with the guest's name and email. If that contact has no deal in stage "Call booked", create one named "[guest name], intro call", set "Meeting" to the event start and assign it to me. Copy the event description into the deal's notes. Do not send any email or message. List what you created.
The last two sentences matter. A routine runs as its owner, with the owner's channels, and it may send messages without asking unless its instructions say otherwise. There is also an event trigger for calendar changes, Calendar Event Changed. It fires on every change to the connected calendar, and events that arrive shortly after a run has started are ignored, so a schedule is the safer choice for bookings. Routines lists the current limits.
Route 3: your own AI client
Calendly runs an MCP server at https://mcp.calendly.com/ with tools that list scheduled events and their invitees. Calendly says no paid plan is needed to connect it, although some actions depend on your plan. Add it to Claude or ChatGPT next to the Customermates connector, then ask: "List the Calendly meetings booked since Monday with their invitees. Find or create each invitee as a contact in Customermates and create a deal in stage Call booked." The Customermates side works on every plan and on self-hosted installations, and it uses your own AI provider rather than hosted credits. Customermates executes what the client calls, so set approvals for write tools in your AI client.
What it costs for a three-person team
- Webhook route on Starter: €36 per month for Customermates, plus a Calendly plan that includes webhooks and wherever n8n runs.
- Calendar route on Pro: €87 per month. That includes the unified inbox and 5 routines per user. Routine runs draw on the monthly hosted AI credits per active user; see pricing.
A booking is where follow-up starts. With the calendar route on Pro, a routine you set up can put the booked meeting on the client record beside their email and LinkedIn threads, and Mate can draft the confirmation or the prep note for you to review and send, with the next step dated on the deal. To try it on your own Calendly bookings, start your 14-day trial. No credit card.
Test before you trust it
Run these six bookings against a test event type before you switch the integration on for real:
- A new invitee. The contact, the deal and every mapped field arrive.
- The same invitee again, with the email typed in capitals. No second contact appears.
- A reschedule. The deal's meeting time moves, and the stage does not change to cancelled.
- A real cancellation. The stage changes and nothing else is created.
- A booking with an optional question left empty. The workflow still completes.
- A no-show, if you track no-shows through Zapier.
FAQ
Does Calendly have a CRM?
No. Calendly is a scheduling platform. It keeps contacts for the people you meet (Zapier lists contact triggers that need a paid Calendly plan), but it has no pipeline. Its CRM integrations send bookings into HubSpot, Salesforce and Dynamics 365, where stages and deal reporting live.
Does Calendly work with Salesforce and HubSpot?
Yes, natively. The HubSpot integration is available on Calendly's Standard, Teams and Enterprise plans and creates contacts or leads and logs activities. The Salesforce integration needs Teams or Enterprise and can create a lead, contact or opportunity, plus events or tasks on any Salesforce object.
Which Calendly plan do I need for a CRM integration?
Not Free. HubSpot and webhooks start at Standard, Salesforce needs Teams or Enterprise, and Microsoft Dynamics 365 is listed for Enterprise. Calendly's MCP server for AI clients is the exception: Calendly says it needs no paid plan, though some actions depend on the plan.
How do I connect Calendly to Pipedrive, Freshworks or another CRM?
Look in the CRM's own marketplace first. Pipedrive lists Calendly Sync by Outfunnel, and the Freshworks Marketplace lists Calendly Events for CRM. If nothing fits, use a connector platform such as Zapier or Zoho Flow, or point Calendly's webhooks at n8n or your own code and call the CRM's API.
How should a rescheduled Calendly meeting update the CRM?
Calendly sends a cancellation for the old time and a new booking for the new one. The cancellation carries rescheduled set to true. Update the meeting time on the existing deal in that case, and only change the stage when the flag is false.
Does Customermates integrate with Calendly?
Not with a native connector. Bookings reach Customermates through Calendly webhooks and the REST API on any plan, through the host's connected Google or Outlook calendar on Pro and higher in Customermates Cloud, or through an AI client that has both Calendly's and Customermates' MCP connectors. Customermates does not book meetings or write calendar events.
Vendor details checked on 8 October 2026 against Calendly's pricing, HubSpot integration, Salesforce integration, webhooks overview, reschedule payloads, webhook subscriptions, scheduling notifications, AI tools guide and MCP tools, plus Pipedrive Marketplace, Freshworks, Zoho Flow, Zapier, the n8n Calendly Trigger and n8n hosting.
Start from one description
One description. A workspace your agent built.
This is what setup builds from one sentence. Sample data, the real product.
Describe your business
One sentence about your team, your clients and how you sell.
Mate builds it
It asks a few questions, then creates the lists, pipeline, dashboard and playbook.
Work in it
Connect LinkedIn and email. Click through a finished example below.
We're a four-person strategy consultancy. Track clients, engagements and proposals, and help us follow up with prospects on LinkedIn.
Widgets built from the workspace's own lists and fields
Every client conversation from email, LinkedIn and WhatsApp in one place. Mate sets up your workspace and drafts the follow-up, you review and send. Works with Claude, ChatGPT or any agent that speaks MCP.
Related pages
CRM Integrations
Connect Customermates to other tools: REST and MCP on every plan, signed webhooks and your own n8n on paid plans and self-hosted, with honest limits.
Connect n8n to Customermates: Webhooks, REST API
Build visual workflows from generic CRM record events and the record API.
Routines: Scheduled and Event-Driven Assistant Runs
Routines run Mate on a schedule or when a record changes, using the owner's Mate allowance, with limits, run statuses and approvals.
Gmail CRM Integration: How to Choose a CRM for Gmail
Gmail CRM integration explained: sidebar, mailbox sync or BCC, what each syncs, a checklist and CRMs for Gmail compared (checked 3 November 2026).
Customermates
Follow up on every client conversation
Start with one channel and one client on Customermates Cloud, or self-host the free Community Edition.
✓ No credit card required ✓ First 14 days free





