Connect Calendly

Connect your Calendly account in minutes – no API keys, no webhooks to wire by hand. Authorize once, then map booking events like meetings booked, cancellations and no-shows straight onto your conversions.

Connecting Calendly turns scheduling events – meetings booked, cancellations, no-shows – into LeadJourney conversions, automatically attributed to the campaign, ad set and ad that earned them. You authorize Calendly once (no keys to copy, no webhook URLs to paste by hand), then map each Calendly event onto one of your conversion types. Mapped events flow through the same postback pipeline as your offline conversions, so they automatically pick up every ad postback you've already configured.

Before you start

Have these ready so the connection works end to end:

An active LeadJourney workspace and a Calendly account you can sign in to.
A paid Calendly plan – Calendly's free plan doesn't support webhooks, so connecting requires a paid account.
Tracking is live – clicks have to be recorded first so bookings can be matched back to a campaign. See Install the tracking script.
At least one conversion type to map onto (e.g. BookedCall). Set these up first in the Events Manager.

Where to find it

Open Settings → Apps, or go to app.leadjourney.io/settings?slug=apps. Click the Calendly card to open the integration. While you're not connected you'll see a “Connect your Calendly account” card; once connected, the same screen shows your account, scope and triggers.

Step by step

Authorize LeadJourney from Calendly

On the Connect your Calendly account card, click Connect with Calendly. You'll be redirected to Calendly to sign in and approve LeadJourney's access.

The grant gives read access to your scheduled events and organization, plus write access for webhook subscriptions (so LeadJourney can subscribe to your bookings) – there are no keys to copy and no webhook URLs to paste. After you approve, Calendly sends you back and you'll see a “Calendly connected” confirmation.

Webhooks need a paid Calendly plan

Calendly only exposes webhooks on its paid plans. If the connection fails, confirm your Calendly account is on a plan that supports webhook subscriptions.

Check the connection details

Once connected, the header shows everything at a glance: a Live pill (or Needs reconnect if something breaks), your connected account, whether the grant is at User scope or Organization scope, how many triggers are active, and the date you connected. A Disconnect button lives in the same header for later.

Add a trigger

In the Triggers panel – “Each trigger maps a Calendly event to one of your conversions.” – click Add trigger. In the New Calendly trigger dialog:

App – Calendly (already selected).
LeadJourney Event – pick the conversion type this Calendly event should record, e.g. BookedCall. (No options? Create one under Settings → Events first.)
Trigger – choose the Calendly event that should fire it, such as a booking, a cancellation or a no-show.

Click Continue.

Receive data and confirm the mapping

The dialog opens a three-tab flow:

Receive Data – click Check for Data to pull recent records for the event you picked. If nothing appears, create a test booking in Calendly and check again, then select a record to map against.
Configure Mapping – map the Calendly record onto LeadJourney columns – Email, Name, Phone, click_id, Revenue and Currency – using Add custom field for anything extra. Mapping click_id is recommended but optional (see the callout below).
Filtering (optional) – add conditions so the trigger only fires for matching events.

Click Activate to finish.

Why bookings link to the right campaign automatically

Calendly carries the visitor's click ID through scheduling links in its tracking.salesforce_uuid field, and LeadJourney's tracking script populates it. So when someone books, LeadJourney already knows which click – and therefore which campaign, ad set and ad – earned it, without you mapping click_id by hand. Just make sure your scheduling links are opened through LeadJourney-tracked landing pages.

Managing your triggers

Each trigger appears as a row – Calendly event → conversion type – with an Active / Paused pill and a summary of how many fields and filters it uses.

Pause / Resume – temporarily stop a trigger without deleting it.
Edit – change the mapping, filters or target conversion.
Delete – remove a single trigger; others keep running.
Add another – use Add trigger again to map more Calendly events (bookings, cancellations, no-shows) onto different conversions.

Reconnecting

If Calendly revokes the app, the webhook subscription goes missing, or Calendly is unreachable, the header flips to Needs reconnect and shows a banner explaining why. Click Reconnect to re-run the authorization – your triggers stay in place.

Disconnecting

To remove Calendly, click Disconnect in the header and type disconnect to confirm. This is deliberate because it's destructive:

Disconnect deletes your triggers

Disconnecting permanently removes the Calendly connection, deletes every trigger and revokes the webhook subscription. Calendly events stop flowing into your conversions immediately. You can reconnect later, but your trigger configuration won't be restored – you'll set them up again.

Troubleshooting

No records when you click “Check for Data”?

Nothing has happened in Calendly for that event type yet. Create a fresh booking – or cancel one to test a cancellation – then click Check for Data again. The matching record should appear so you can finish the mapping.

Bookings come in but aren't attributed to a campaign?

LeadJourney needs to know which click the booking belongs to. Check that (1) the tracking script is installed and recording clicks, (2) visitors reach Calendly through LeadJourney-tracked pages (so tracking.salesforce_uuid carries the click ID), and (3) the trigger is Active. As a fallback you can map click_id, email or phone explicitly on the Configure Mapping tab.

Header shows “Needs reconnect”?

Calendly has revoked the grant, the webhook is gone, or the API is unreachable. Click Reconnect in the banner to re-authorize. Your triggers are preserved.