Email and calendar
Calendly for AI agents.
Managed auth, ready-made tools.
Find open times, share booking links, and book, review or cancel meetings in Calendly on behalf of each of your users.
About Calendly
With the Calendly connector, your agent handles scheduling in each user’s own Calendly account. It can find open times, send a one-time booking link, book or cancel a meeting, and check who is coming, using only the tools your project allows.
Calendly is a scheduling platform that lets people book time from shared availability.
Tools
What your agent can do in Calendly.
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 Calendly connection.
-
List event types
Readcalendly_list_event_typesList the kinds of meetings the user offers.
-
Get available times
Readcalendly_get_available_timesList the open times for an event type in a date range.
-
Create a booking link
Writecalendly_create_scheduling_linkCreate a single-use link for one person to book a meeting.
-
Book a meeting
Writecalendly_book_meetingBook an open time on an event type for an invitee.
-
List scheduled events
Readcalendly_list_eventsList upcoming or past meetings in a date range.
-
List invitees
Readcalendly_list_inviteesList who booked a meeting, with their answers.
-
Cancel a meeting
Writecalendly_cancel_eventCancel a scheduled meeting with a reason.
-
Mark a no-show
Writecalendly_mark_no_showMark an invitee as a no-show.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Calendly, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Allow booking links and reading, and switch off
calendly_cancel_eventif the agent should never cancel a meeting. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use, for example scheduled events but not event types. A call outside them is refused.
Get started
Connect Calendly
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 Calendly
Each end user authorizes their own Calendly 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 Calendly account, once. const connection = await agent200 .user("user_123") .connect("calendly"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the Calendly tools
Name the user, the model and the tools. The model decides which Calendly 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: "Send Jordan a one-time link for a 30 minute intro call", tools: ["calendly"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Who signs in
Each of your users, once, on Calendly's own sign-in page. You never see or store their Calendly password.
-
What access is requested
The Calendly scopes the connection needs, such as reading event types or managing scheduled events. Calendly lets the user decline a scope during sign-in, and a tool that needs it then stops working.
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 Calendly connector and how to use it.
Connector: Calendly, through Agent200. In code: "calendly". What it does: Find open times, share booking links, and book, review or cancel meetings in Calendly on behalf of each of your users. Page: https://www.agent200.com/tools/calendly/ 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 Calendly's own page, through the authorization link Agent200 returns. Never ask a user for a Calendly 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: calendly_list_event_types, calendly_get_available_times, calendly_list_events, calendly_list_invitees. Write tools: calendly_create_scheduling_link, calendly_book_meeting, calendly_cancel_event, calendly_mark_no_show. Name "calendly" 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/tools/calendly/framework/claude/ https://www.agent200.com/tools/calendly/framework/chatgpt/ https://www.agent200.com/tools/calendly/framework/claude-code/ https://www.agent200.com/tools/calendly/framework/muse/ https://www.agent200.com/tools/calendly/framework/grok-bot/ https://www.agent200.com/tools/calendly/framework/openai-dots/ https://www.agent200.com/tools/calendly/framework/claude-duet/ https://www.agent200.com/tools/calendly/framework/hermes-agent/ https://www.agent200.com/tools/calendly/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: /tools/calendly.md
Guides
Use Calendly with the AI you build on.
Step-by-step setup for Calendly with a specific model, assistant or agent framework.
-
Calendly + Claude
How to connect Calendly to Claude
-
Calendly + ChatGPT
How to connect Calendly to ChatGPT
-
Calendly + Claude Code
How to connect Calendly to Claude Code
-
Calendly + Muse
How to connect Calendly to Muse
-
Calendly + Grok Bot
How to connect Calendly to Grok Bot
-
Calendly + OpenAI Dots
How to connect Calendly to OpenAI Dots
-
Calendly + Claude Duet
How to connect Calendly to Claude Duet
-
Calendly + Hermes Agent
How to connect Calendly to Hermes Agent
-
Calendly + OpenClaw
How to connect Calendly to OpenClaw
FAQ
Calendly and Agent200, answered.
Who handles the Calendly 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 Calendly.
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 Calendly connection, never another user's. It cannot reach anything the user or Calendly has not authorized.
Can I limit what my agent can do in Calendly?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.