Create a record in Airtable when someone cancels a meeting in Calendly

What each client fills in

Airtable: Base ID

From the base’s URL: airtable.com/appXXXX/…

Airtable: Table

For example Leads

The accounts it needs

Each is the client’s own, stored encrypted and never copied between clients. Until one is added the client’s checklist shows it, and nothing runs.

• Calendly

  In the client’s Calendly: Integrations & apps → API and webhooks → Personal access tokens → Generate new token, with the scopes scheduling_links:write (booking links) and, for the triggers, users:read, webhooks:read and webhooks:write. A token made before Calendly introduced scopes keeps full access.

• Airtable

  airtable.com/create/tokens → Create token → scopes data.records:write and data.records:read (lookups and the triggers) → add the client’s base → copy the token.

After you install it

It lands switched off. The client’s checklist holds exactly this:

1. Connect the client’s Calendly, for “Someone cancels a meeting”
2. Connect the client’s Airtable, for “Create a record”
3. Fill in Airtable: Base ID (From the base’s URL: airtable.com/appXXXX/…)
4. Fill in Airtable: Table (For example Leads)
5. Confirm with the client: The client’s Calendly is on a paid plan (Standard, Teams or Enterprise): Calendly sends webhook events only on those.
6. Match Airtable’s fields to the client’s own: Their name, Their email, Their phone for text reminders, Rescheduled true or false