Email and calendar
Cal.com for AI agents.
Managed auth, ready-made tools.
List event types and open slots, book, reschedule and cancel Cal.com bookings on behalf of each of your users.
About Cal.com
With the Cal.com connector, your agent manages scheduling in each user’s own Cal.com account. It can list event types and open slots, book a meeting, reschedule or cancel a booking and list what is coming up, using only the tools your project allows.
Cal.com is a scheduling platform for booking meetings through shareable links.
Tools
What your agent can do in Cal.com.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Cal.com connection.
-
List event types
Readcal_com_list_event_typesList the user's event types.
-
Get available slots
Readcal_com_get_slotsGet the open time slots for an event type.
-
List bookings
Readcal_com_list_bookingsList upcoming and past bookings.
-
Create a booking
Writecal_com_create_bookingBook a meeting in an open slot.
-
Reschedule a booking
Writecal_com_reschedule_bookingMove a booking to a new time.
-
Cancel a booking
Writecal_com_cancel_bookingCancel a booking.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Cal.com, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent read bookings and book new ones, and switch off
cal_com_cancel_bookingso it can never cancel one. -
Restrict what the agent reaches
Choose the endpoints a project may use, for example slots and bookings but not event types. A call outside them is refused.
Get started
Connect Cal.com
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect Cal.com
Each end user authorizes their own Cal.com account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Cal.com account, once. const connection = await agent200 .user("user_123") .connect("cal_com"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the Cal.com tools
Name the user, the model and the tools. The model decides which Cal.com tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "What slots do I have open for a 30 minute call next Tuesday", tools: ["cal_com"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Who signs in
Each of your users, once, on Cal.com's own sign-in page. You never see or store their Cal.com password.
-
What access is requested
The access the connection needs, such as reading or managing bookings and event types, listed on Cal.com's authorization screen. Users can remove the app later from their Cal.com account settings.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Cal.com connector and how to use it.
Connector: Cal.com, through Agent200. In code: "cal_com". What it does: List event types and open slots, book, reschedule and cancel Cal.com bookings on behalf of each of your users. Page: https://www.agent200.com/connectors/cal-com/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on Cal.com's own page, through the authorization link Agent200 returns. Never ask a user for a Cal.com password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: cal_com_list_event_types, cal_com_get_slots, cal_com_list_bookings. Write tools: cal_com_create_booking, cal_com_reschedule_booking, cal_com_cancel_booking. Name "cal_com" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/connectors/cal-com/framework/claude/ https://www.agent200.com/connectors/cal-com/framework/chatgpt/ https://www.agent200.com/connectors/cal-com/framework/claude-code/ https://www.agent200.com/connectors/cal-com/framework/muse/ https://www.agent200.com/connectors/cal-com/framework/grok-bot/ https://www.agent200.com/connectors/cal-com/framework/openai-dots/ https://www.agent200.com/connectors/cal-com/framework/claude-duet/ https://www.agent200.com/connectors/cal-com/framework/hermes-agent/ https://www.agent200.com/connectors/cal-com/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /connectors/cal-com.md
Guides
Use Cal.com with the AI you build on.
Step-by-step setup for Cal.com with a specific model, assistant or agent framework.
-
Cal.com + Claude
How to connect Cal.com to Claude
-
Cal.com + ChatGPT
How to connect Cal.com to ChatGPT
-
Cal.com + Claude Code
How to connect Cal.com to Claude Code
-
Cal.com + Muse
How to connect Cal.com to Muse
-
Cal.com + Grok Bot
How to connect Cal.com to Grok Bot
-
Cal.com + OpenAI Dots
How to connect Cal.com to OpenAI Dots
-
Cal.com + Claude Duet
How to connect Cal.com to Claude Duet
-
Cal.com + Hermes Agent
How to connect Cal.com to Hermes Agent
-
Cal.com + OpenClaw
How to connect Cal.com to OpenClaw
FAQ
Cal.com and Agent200, answered.
Who handles the Cal.com OAuth flow and the tokens?
Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Cal.com.
Does my agent act as the end user?
Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Cal.com connection, never another user's. It cannot reach anything the user or Cal.com has not authorized.
Can I limit what my agent can do in Cal.com?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.