CRM, sales & support · wired today
Cal.com, wired into your agent workforce
Pipeline truth lives here, and agents are only as honest as their source. The Cal.com connector is one of 205 executable connectors and gives agents 3 read-only tools, with the credential held in the vault and every call receipted.
Connecting Cal.com takes one credential
You provide API key from your Cal.com account; Quox sends it as a bearer token. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Where to get it: Cal.com's own API documentation ↗ covers creating and scoping the credential.
What agents can run against Cal.com
get_meGet the Cal.com profile this API key belongs to (username, email, timezone, organization)
list_event_typesList Cal.com event types, optionally filtered to one username or event slug
list_bookingsList Cal.com bookings, optionally filtered by status or attendee email (cursor paginated)
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
How proven is this?
This connector was blind shape-proven against the real Cal.com API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.
Cal.com integration FAQ
What can Quox agents do with Cal.com?
Agents can run 3 read-only tools against Cal.com: get me, list event types, list bookings. Every call is receipted in the evidence trail.
What does the Cal.com integration need?
You provide API key from your Cal.com account; Quox sends it as a bearer token. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Do agents see my Cal.com credentials?
No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.
How proven is the Cal.com connector?
This connector was blind shape-proven against the real Cal.com API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.