Skip to main content

Connect Calendly (Automatic Booked Calls)

Send every Calendly booking to us automatically as a booked call - one token, no Zapier. Includes the exact permissions your token needs and how to choose which meetings count.

Written by Chris Ross

If you take bookings through Calendly, you can send them to us automatically. Every new booking is recorded as a booked call against that lead, which lets the ad platforms find more people who actually book with you.

It's a one-time setup, it takes about two minutes, and there's no Zapier and no field mapping. You paste one token and we build the connection for you.

⚠️ Calendly only allows this on a paid Calendly plan (Standard or above). On the free plan Calendly will refuse the connection.

Step 1 — Create a Calendly token

In Calendly, go to Integrations & apps → API & webhooks → Personal access tokens and create a token.

When Calendly asks which permissions the token should have, tick exactly these five:

  • users:read — lets us see which Calendly account the token belongs to.

  • webhooks:read — lets us check for an existing connection, so reconnecting later can't create a duplicate.

  • webhooks:write — lets us create the connection (and remove it if you disconnect).

  • scheduled_events:read — Calendly insists on this before it will send us bookings, even though we only read what it sends us.

  • event_types:read — lets us list your meeting types so you can choose which ones count.

⚠️ Tick all five before you create the token. Calendly doesn't let you change a token's permissions afterwards — if you miss one, create a new token and use that instead.

Copy the token when Calendly shows it to you. This is the only time it's displayed.

Step 2 — Paste it into your portal

In your portal, go to Account → Webhooks and find the Calendly card. Paste the token and click Connect Calendly.

The Calendly card in the portal before connecting, with a box to paste your token

We use the token once to create the connection, and then discard it — we never store it. If you'd rather revoke it in Calendly afterwards, the connection keeps working.

Once it's connected the card confirms it, and there's nothing else to set up.

The Calendly card showing Connected, and which meetings count as booked calls

Step 3 — Choose which meetings count

Calendly sends us every booking you take — on their side a connection can't be limited to a single meeting type. So if you also use Calendly for vendor calls, interviews or internal meetings, tell us which ones actually count.

On the Calendly card, tick the meetings that mean a real prospect booked with you, then click Save meeting types. Everything else is ignored — the booking still reaches us, we just don't record it or report it to the ad platforms.

The meeting-type picker showing Calendly meeting types with checkboxes

Leave everything unticked and every booking counts. That's the default, and it's the right choice if you only use Calendly for prospects. Once you've saved a choice the list collapses to show just what you picked — click Change which meetings count to edit it.

Don't see one of your meetings listed? Type its name into the box exactly as it's spelled in Calendly, then save.

What happens after that

  • Every booking of a meeting you've chosen is recorded as a booked call against that lead.

  • We match the booking to a lead by the email address the person used in Calendly. If they book with a different address than they registered with, we won't find them — nothing breaks, we just can't attribute it.

  • Cancellations and reschedules are ignored, so nothing breaks when somebody moves a meeting.

  • You can see everything that reached us under Account → Webhooks in the Recent activity list.

⚠️ Don't turn on “Require a signature” while Calendly is connected. Calendly signs its bookings with its own key rather than your secret, so switching that on makes us reject every Calendly booking. The portal will warn you if both are on.

If something isn't working

  • “missing required scope” — the token is missing one of the five permissions above. They can't be added to a token after it's made, so create a new one with all five ticked and paste that.

  • “Calendly already has a webhook for this address” — an earlier attempt left a connection behind. Create a fresh token that includes webhooks:read and connect again; we'll clear the old one out for you.

  • Calendly refuses the connection — usually a free Calendly plan (this needs Standard or above), or a token that was copied incompletely.

  • Your meeting types didn't appear — the token was created without event_types:read. Either reconnect with a new token that has it, or just type your meeting names into the box by hand.

  • Bookings happen but nothing is recorded — check the meeting-type list. If that meeting isn't ticked, we're ignoring it on purpose.

Disconnecting

Click Disconnect Calendly on the card. To also delete the webhook inside your Calendly account, paste a token first — otherwise we stop recording bookings on our side but the webhook stays in Calendly until you remove it there.

Sending us more than bookings

Calendly can only tell us who booked. If you also want to tell us who became a client, who attended a seminar, or how good a lead was, see Sending Us Your Conversion Data (Booked Calls, Clients, Attendance) — you can upload a spreadsheet or connect your CRM.

Stuck at any point? Use Chat with us in the portal and we'll sort it out.

Did this answer your question?