A Calendly connection lets the Calendly triggers start a run when someone books, cancels or submits a routing form, and lets the Calendly steps find events, read an invitee, cancel an event and make a one-time booking link. It connects with a personal access token you make in Calendly.

Who can do this

  • In Bizomate: workspace Admins and Editors, on every plan — Calendly is not a premium connection. Viewers see the connection but cannot add or change it.
  • In Calendly: any user can make their own token. To hear about bookings for everyone in your Calendly organisation, or about routing forms, the token must belong to an organisation owner or admin.
  • Calendly's plan: the triggers need a paid Calendly plan — Calendly offers webhooks only there. On a free plan the triggers show Not listening with Calendly's reason; they do not check instead. The steps work on every Calendly plan.

Steps

In Calendly, make the token:

  1. Sign in to Calendly.
  2. Open Integrations & apps, then API and webhooks.
  3. Under Personal access tokens, select Generate new token, and name it — Bizomate.
  4. Copy the token. Calendly shows it only once.

In Bizomate, add the connection:

  1. Select Connections in the bar at the top, then + Add connection.
  2. Under Productivity, select Calendly. It reads "Stored credential".
  3. In Connection name, type a name — for example Consulace Calendly.
  4. Paste the token in Personal access token. It is hidden as you type.
  5. Optional: choose an end date in This token expires on · optional.
  6. Leave Test the connection before saving ticked.
  7. Select Save connection. It reads Testing while Calendly is asked whose token it is.

The toast "Connection added" says "“Consulace Calendly” is ready. Every workflow in this workspace can use it."

What happens next

  • The connection appears under Productivity. Its panel shows the masked token's ending, never the token.
  • Test answers with the Calendly user and their booking page — Reached Rohan Mehta · calendly.com/consulace.
  • The Calendly triggers and steps list it under Connection, and load your event types and routing forms from it.

Good to know

  • The token acts as one Calendly user. Events the steps cancel are cancelled as that user, and Find scheduled events finds that user's events. If they leave your Calendly organisation, the connection stops working — replace the token with another user's.
  • Revoking the token in Calendly ends it at once. Open the connection's panel, select Replace token, paste a new one and select Replace token.
  • Signing in with Calendly, instead of a token, is planned for later. The token stays as a way to connect.

If something goes wrong

What you see Why What to do
Calendly refused it — "Calendly refused: The access token is invalid. Check the connection's details on Connections. Nothing was saved." (Calendly's own reason after "refused:") The token was mistyped or revoked. Make a new token and paste it.
"Could not reach Calendly: …" or "Calendly did not answer within 30 seconds." Calendly could not be reached. Try again in a few minutes.
"Enter the credential." The token box is empty. Paste the token.