Create a customer in Stripe when someone books a meeting in Calendly

What each client fills in

Nothing to fill in. It needs the accounts it connects to, set up as its checklist says.

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.

• 

  In the client’s Stripe dashboard: Developers → API keys → Create restricted key. Give it only what the steps need: Customers write, Payment Links write, Prices read, Invoices write, and Webhook Endpoints write for the triggers. Leave “IP access” empty: Thrum has no fixed addresses, so a key locked to IPs fails every call.

After you install it

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

1. Connect the client’s Calendly, for “Someone books a meeting”
2. Connect the client’s Stripe, for “Create a customer”
3. Confirm with the client: The client’s Calendly is on a paid plan (Standard, Teams or Enterprise): Calendly sends webhook events only on those.