# 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.

- Page: https://www.agent200.com/tools/calendly/
- Category: Email and calendar
- Authentication: Managed OAuth
- Identifier in code: `calendly`
- Create an API key: https://agent200.com/platform/apikeys/
- Updated: 2026-11-15

## Instructions for AI agents

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/

## About

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.

## Calendly tools

- **List event types** (`calendly_list_event_types`, read): List the kinds of meetings the user offers.
- **Get available times** (`calendly_get_available_times`, read): List the open times for an event type in a date range.
- **Create a booking link** (`calendly_create_scheduling_link`, write): Create a single-use link for one person to book a meeting.
- **Book a meeting** (`calendly_book_meeting`, write): Book an open time on an event type for an invitee.
- **List scheduled events** (`calendly_list_events`, read): List upcoming or past meetings in a date range.
- **List invitees** (`calendly_list_invitees`, read): List who booked a meeting, with their answers.
- **Cancel a meeting** (`calendly_cancel_event`, write): Cancel a scheduled meeting with a reason.
- **Mark a no-show** (`calendly_mark_no_show`, write): Mark an invitee as a no-show.

## Limits you can set

**Turn single tools on or off.** Allow booking links and reading, and switch off `calendly_cancel_event` if 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

### Step 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.

File `agent.js`:

```js
// One Agent200 API key covers every connector enabled for the project.
const agent200 = new Agent200({
  apiKey: process.env.AGENT200_API_KEY,
});
```

(Conceptual example of the Agent200 SDK.)

### Step 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.

File `connect.js`:

```js
// 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);
}
```

(Conceptual example of the Agent200 SDK.)

### Step 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.

File `run.js`:

```js
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);
```

(Conceptual example of the Agent200 SDK.)

## 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.

## Example requests

- "Send Jordan a one-time link for a 30 minute intro call"
- "What meetings are booked with me tomorrow?"
- "Book Maria into my next open demo slot on Thursday"
- "Cancel my 2pm and tell the invitee I'm sick"

## Guides: Calendly with your AI framework

- [Calendly + Claude](https://www.agent200.com/tools/calendly/framework/claude.md): Connect Calendly to Claude through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Calendly + ChatGPT](https://www.agent200.com/tools/calendly/framework/chatgpt.md): ChatGPT cannot send an API key to a custom MCP server, so this guide builds Calendly into your own agent with OpenAI's models and the Agent200 SDK.
- [Calendly + Claude Code](https://www.agent200.com/tools/calendly/framework/claude-code.md): Have Claude Code build a Calendly agent with the Agent200 SDK: managed OAuth, ready-made tools and one API key.
- [Calendly + Muse](https://www.agent200.com/tools/calendly/framework/muse.md): Connect Calendly to Muse through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Calendly + Grok Bot](https://www.agent200.com/tools/calendly/framework/grok-bot.md): Connect Calendly to Grok Bot through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Calendly + OpenAI Dots](https://www.agent200.com/tools/calendly/framework/openai-dots.md): Dots cannot send an API key to a custom MCP server, so this guide builds an always-on Calendly agent with OpenAI's models and the Agent200 SDK.
- [Calendly + Claude Duet](https://www.agent200.com/tools/calendly/framework/claude-duet.md): Connect Calendly to Claude Duet through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Calendly + Hermes Agent](https://www.agent200.com/tools/calendly/framework/hermes-agent.md): Connect Calendly to Hermes Agent through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Calendly + OpenClaw](https://www.agent200.com/tools/calendly/framework/openclaw.md): Connect Calendly to OpenClaw through Agent200's MCP server: managed OAuth, ready-made tools and one API key.

## FAQ

### 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.

## Related connectors

- [Gmail](https://www.agent200.com/tools/gmail.md): Read, search, draft and send email from each user's own Gmail account.
- [Outlook](https://www.agent200.com/tools/outlook.md): Work with mail and calendar in each user's Microsoft Outlook account.
- [Google Calendar](https://www.agent200.com/tools/google-calendar.md): Check availability and create, update or cancel events in your users' calendars.
- [iCloud](https://www.agent200.com/tools/icloud.md): Search and send iCloud Mail, read and add calendar events, and look up contacts on behalf of each of your users.

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
