Connector · Scheduling
Calendly, in every client’s workflows.
Make a one-time booking link, or start when someone books a meeting, with the client’s own Calendly account.
- Triggers
- 2start a workflow
- Actions
- 1steps in a workflow
Start a workflow when something happens in CalendlyBeta
By webhook where Calendly sends one, by checking where it does not. A webhook is checked once a day to see it is still on, and if Calendly turns it off the alert carries a Reconnect button.
- Someone books a meetingWebhookA new booking on the account’s Calendly, within seconds.
- Someone cancels a meetingWebhookA booking canceled on the account’s Calendly, within seconds. A reschedule is a cancel and a new booking; skip those with the toggle.
Do it in Calendly
A step with its own fields: values from the run go in by name, and what Calendly answers is there for the next step.
- Make a one-time booking linkA link that books one event, to send to a lead: the output’s booking_url.
Connect the client’s Calendly
On the client’s page in Thrum: Add credential, type Calendly personal access token.
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.
The key is stored encrypted and bound to that client: another client’s workflow cannot use it, and no template or pack copies it.
Watched like everything else
When Calendly stops answering or refuses the client’s key, you hear about it, and your client does not.
- A failing request
- Tried 3 times, 5 seconds apart and doubling, only for errors a retry can fix
- A service that asks for a pause
- Given it, up to an hour
- Requests at once, per account
- 2, per worker; the rest wait their turn
- Timeout
- 15 seconds, unless the step sets its own
- Private and internal addresses
- Refused, on every redirect too
- The client’s key
- Encrypted, bound to the client, and kept out of every run record
- A step that keeps failing
- Marks the workflow Degraded and alerts you, not the client
Calendly and its logo are trademarks of their owner, used here only to say what Thrum works with; no endorsement is implied.
Thrum is cooking.
Get early access and you’ll be among the first in. Early members get a launch perk.