Connect Calendly to Salesforce

What This Integration Does

This integration pushes Calendly bookings into Salesforce as Events on the right Lead, Contact, or Opportunity record. Intake form answers populate custom fields, and Opportunity stages advance automatically when meetings are booked, held, or no-showed. Reschedules and cancellations update the existing Event rather than creating duplicates.

For Salesforce-driven sales orgs, this turns Calendly from a calendar tool with limited CRM context into a proper feeder for the pipeline. It sits in our wider integrations work, where each connection is built to move real data between two systems rather than mirror it loosely.

The Workflow

When an invitee books a meeting through a Calendly link, the integration receives the webhook, identifies the relevant Salesforce record by email, and creates an Event on the Lead or Contact with the start time, owner, and meeting type. Intake form responses populate Salesforce custom fields. The prospect’s company headcount, current vendor, and primary use case go onto the Lead record so the rep can review before the call.

Take a specific chain. An Account Executive’s Calendly link is associated with the “Enterprise Discovery” Opportunity type. A prospect books, and the integration creates an Opportunity at “Discovery Booked” stage tied to the matched Account, populated with the intake answers. A pre-meeting flow fires: a Salesforce task to the AE to review and prep, a notification to the SDR who sourced the lead, and a calendar invite with the briefing document attached. When the meeting completes and the AE updates the next step in Salesforce, the Opportunity advances to “Discovery Complete” and the next stage automation runs. If the prospect no-shows, the Opportunity moves to “No Show” and an automated re-engagement sequence kicks off.

Round-robin and team-based Calendly bookings are routed correctly. When a team Calendly link is booked, the integration assigns the resulting Salesforce record to whichever rep Calendly assigned, keeping owner consistency across both systems.

Before and After

Before, Calendly bookings appear on the rep’s calendar but Salesforce only knows because someone manually creates the Event. Intake form data lives in Calendly. Opportunity stages do not move until the rep updates them by hand. No-show tracking is unreliable.

After, every booking, reschedule, and no-show writes itself onto the Salesforce record with full context. Opportunity stages move automatically. The pipeline report finally reflects what actually happened.

Who Needs This

Mid-market and enterprise B2B sales teams running Salesforce as the system of record with Calendly as the booking layer. This is typical of SaaS, professional services, fintech, and any sales-led business where discovery and demo cadence is the core of the pipeline. The integration becomes essential once data entry between the two systems becomes a real cost.

How We Build This

We build this against the Calendly v2 API webhooks and the Salesforce REST API. Salesforce’s strict governor limits inform the architecture: we batch updates and queue webhooks so bursts of bookings never exceed API limits. Round-robin owner mapping, Opportunity creation rules, and intake field mapping are configured per organisation. The Salesforce API Integration page covers the Salesforce capabilities involved, and if you run HubSpot rather than Salesforce the same pattern applies in our Connect Calendly to HubSpot build.

Get Calendly and Salesforce Connected

If Calendly is your booking layer and Salesforce is your pipeline of record, we can build a custom integration that captures every meeting on the right record with full context. Teams that route inbound conversations as well as meetings often pair it with our Connect WhatsApp to Salesforce work so every touchpoint lands on the same record.