A Cal.com connection lets the Cal.com triggers start a run when a booking is made, cancelled, rescheduled or ends, and lets the Cal.com steps find bookings, find free slots, book and cancel. It connects with an API key from Cal.com, on cal.com or on a Cal.com you run yourself.

Who can do this

  • In Bizomate: workspace Admins and Editors, on every plan — Cal.com is not a premium connection. Viewers see the connection but cannot add or change it.
  • In Cal.com: any user can make their own key. The connection sees that user's event types and bookings, and its steps act as that user.

Steps

In Cal.com, make the key:

  1. Sign in to Cal.com.
  2. Open Settings, then Developer, then API keys (path to check on the day of moving).
  3. Select New, name it — Bizomate — and choose when it expires, or Never expires.
  4. Copy the key. Cal.com 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 Cal.com. It reads "Stored credential".
  3. In Connection name, type a name — for example Consulace Cal.com.
  4. In Address, choose where your Cal.com is:
    • Cal.com — cal.com, the usual one. It is chosen to begin with.
    • Your own address — a Cal.com you run yourself. Then type, in Your own address, the https address its API v2 answers on, without /v2 — for example https://api.cal.consulace.com. Leave Your own address empty when Address is Cal.com.
  5. Paste the key in API key. It is hidden as you type.
  6. Optional: if the key expires, choose that date in This key expires on · optional. The workspace's admins are reminded 30, 7 and 1 days before.
  7. Leave Test the connection before saving ticked.
  8. Select Save connection. It reads Testing while Cal.com is asked whose key it is.

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

What happens next

  • The connection appears under Productivity. Its panel shows the address and the masked key's ending, never the key.
  • Test answers with the Cal.com username and where it is — Reached rohan-mehta · cal.com, or your own address's host: Reached rohan-mehta · api.cal.consulace.com.
  • The Cal.com triggers and steps list it under Connection, and load your event types from it.

Good to know

  • Cal.com EU (cal.eu) is not offered yet: Cal.com's documentation does not yet say which API address it uses. It will be added as a third Address choice once it does.
  • Your own Cal.com must be reachable on the public internet over https. One on a private network, such as 10.0.0.5 or localhost, is refused.
  • A key works only where it was made. A key from your own Cal.com is refused on Cal.com, and the other way round.
  • A key that expires stops the connection on that day. Make a new one in Cal.com, then Replace key on the connection's panel.

If something goes wrong

What you see Why What to do
Cal.com refused it — "Cal.com refused: … Check the connection's details on Connections. Nothing was saved." The key was mistyped, deleted or expired, or Address is the wrong Cal.com. Check Address, then make a new key and paste it.
"… is not on the public internet, so workflows cannot reach it." Your own address is a private one. Use your Cal.com's public address.
"Cal.com address “…” is not an https address." Your own address starts with http://. Use its https address.
"Your own address is empty. Give your Cal.com's API address — https://api.cal.consulace.com, say." Address is Your own address, but the address is not filled in. Type it, or choose Cal.com.
"Could not reach Cal.com: …" or "Cal.com did not answer within 30 seconds." The address is wrong, or Cal.com did not answer. Check Address, then try again.
"Enter the credential." API key is empty. Paste the key.