Webhook recipe · Calendly

Calendly → Chromoly: bookings with a memory.

A Calendly booking is a strong signal - someone wants to talk - and by default it lands only in your calendar. This recipe gives every booking a consequence: the lead updates, prep tasks appear, and no-shows get a follow-up instead of a shrug.

What people build with it

The recipe

In Chromoly, add a webhook trigger: "when a booking arrives, find the lead by email and log the meeting". Copy the trigger URL.

In Calendly, create a webhook subscription pointing at that URL for invitee.created and invitee.canceled - via Calendly’s API or their integrations admin, per their docs.

Book a test meeting. Chromoly shows the payload - map invitee name, email, event type, and time to your fields once.

Describe the consequences: match-or-create the lead, add the prep task, handle cancellations. Preview, deploy.

Webhook triggers and their signing secrets are covered in the integrations documentation. Every received request - including rejected ones - appears in the workflow's run history, so the connection is debuggable from day one.

Questions

Does Calendly support webhooks on my plan?

Webhook subscriptions are a paid-plan Calendly feature (Standard and up), created via their API or admin integrations. On the free plan, an email-forward bridge can substitute until you upgrade.

What events does Calendly send?

The useful two: invitee.created and invitee.canceled - enough to create records, schedule prep, and clean up when meetings vanish.

Can this update an existing lead instead of creating duplicates?

Yes - the workflow matches on the invitee's email first, attaches the booking as activity when found, and creates a record only when there's no match.

Build the system this feeds

Describe it in plain language - the webhook trigger is part of the description. Preview free before anything deploys.

Start free