Calendly

Through Zapier / Pabbly · 15 min

Every new Calendly booking becomes a lead in the project

Before you start

A paid Calendly plan (Standard or higher) and a Zapier plan that includes Webhooks by Zapier.
Steps use Zapier. Make and Pabbly Connect have the same Calendly trigger and an HTTP / webhook step and work the same way. Calendly's own webhooks need its API, so a plain paste-the-URL setup is not possible.

Your Calendly lead URL

Your lead URL appears here when you open this page from the LeedsApp app: open the project, then Lead integrations and Calendly.

Set it up in Calendly

1
Ask for the phone number in CalendlyIn Calendly, go to Scheduling and open your event type. Click More options at the bottom, open Invitee form and click + Add new question. Type Mobile number, tick Required, set Answer type to Phone number and click Save changes.
2
Create a ZapIn Zapier, click Create › Zaps. For the trigger choose Calendly and the event Invitee Created. Connect your Calendly account.
3
Add the POST stepFor the action choose Webhooks by Zapier and the event POST. Paste your LeedsApp lead URL in URL and set Payload Type to JSON.
4
Map the fieldsUnder Data, add rows: name = Invitee Name, email = Invitee Email, phone = the answer to your phone question, booking_id = Invitee URI.
5
Test and publishClick Test step. Zapier sends a sample booking; it should show a success reply. Click Publish.

What LeedsApp saves

Calendly sendsSaved on the lead asnameNamephoneMobile numberemailEmailbooking_idNotesOther rows you addCustom field
Lead source: Calendly. The same booking sent twice is saved once. Cancelled bookings are not sent.

If leads don't arrive

  • Calendly does not fire for bookings made before the Zap was turned on. Book a new test slot.
  • No phone on the lead (or the lead is refused): add a required Phone number question in the event type's Invitee form and map its answer to phone.
  • Zapier's Zap history shows each run and the reply from LeedsApp.

Need help? Write to support@leedsapp.com