- Home
- Resources
- Integrations
- Calendly
Claude Calendly connectorWhat Claude can do in your Calendly account.
The Claude Calendly connector exposes 36 tools. 25 read your events, availability and organization, 11 change something in your account, and 0 lack a description, since Calendly documents every one. Below: what Claude books, what it cancels and what stays manual.
Verified Trustpilot reviews · AI, automation & growth agency
What Claude does once it can reach your Calendly
Scheduling usually means juggling tabs: your calendar, the Calendly dashboard, an email thread with the person you are trying to meet. With the connector, you tell Claude what you need in one sentence and it checks your open slots, books, cancels or produces a link, then reports back in the same conversation.
Find a slot without opening Calendly. Ask for free times next week for your coaching session: Claude reads them from the event type's open times and lists them for you.
Book or cancel from the chat. One tool places a booking for a named guest, another calls off a meeting you no longer need. Both touch real calendars, so read what Claude proposes before you confirm.
Adjust how people book you. Claude can set up a new event type, change an existing one, edit its availability schedule, or produce a single-use link that expires after one booking.
What it cannot do: Calendly hosts the connector itself, so there is nothing to install or run elsewhere, and booking through Claude needs a paid Calendly subscription according to the publisher. Routing forms are only readable, and only on Calendly's Teams tier or higher. Nothing fires on its own either: Claude calls these tools while you talk to it. For a workflow that reacts every time someone books, the Calendly n8n integration page covers that different job.
Five words to know first
The terms that come up around this connector, each explained once.
- Connector
- A link you set up once between Claude and an account you already use, so Claude can act on it while it answers you.
- Tool
- One named action a connector opens to Claude. Claude decides which ones to call, and the directory lists them all by name.
- Authorization
- Calendly's consent screen, where you press Connect to Calendly and hand Claude the access it will use. Once per person, revocable.
- Approval
- The confirmation Claude waits for before doing something that changes your account, shown in the conversation when it counts.
- MCP
- The open standard connectors run on: the shared language that lets an assistant like Claude talk to a service such as Calendly.
Connect Calendly to Claude in three steps
- 01
Find Calendly in Claude
In Claude's settings, open Customize, then Connectors, and look for Calendly. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it for the organization before members can sign in.
- 02
Log in to Calendly
Click Connect on its row. Calendly opens a browser window where you sign in to your own Calendly account. If the link breaks later, Disconnect and connect again.
- 03
Approve Calendly's consent screen
Read the screen before you press the button to connect. It belongs to Calendly, not to Claude, and it sets what the access covers. You can take that access back later from the Calendly side as well.
The 36 tools, split into reading and changing
Calendly gives Claude 36 tools: 25 that read your account, 11 that change something in it.
Calendly publishes a line for each tool, so everything falls into two groups. Names stay exactly as Claude shows them.
- 25 read
- 11 write
Tools index
- users-get_current_user
- users-get_user
- event_types-list_event_types
- event_types-get_event_type
- event_types-list_event_type_available_times
- event_types-list_event_type_availability_schedules
- locations-list_user_meeting_locations
- meetings-list_events
- meetings-get_event
- meetings-list_event_invitees
- meetings-get_event_invitee
- availability-list_user_availability_schedules
- availability-get_user_availability_schedule
- availability-list_user_busy_times
- meetings-get_invitee_no_show
- organizations-get_organization
- organizations-list_organization_memberships
- organizations-get_organization_membership
- organizations-list_organization_invitations
- routing_forms-list_routing_forms
- routing_forms-get_routing_form
- routing_forms-list_routing_form_submissions
- routing_forms-get_routing_form_submission
- list_calendly_skills
- load_calendly_skill
- event_types-create_event_type
- event_types-update_event_type
- event_types-update_event_type_availability_schedule
- meetings-cancel_event
- meetings-create_invitee
- scheduling_links-create_single_use_scheduling_link
- meetings-create_invitee_no_show
- meetings-delete_invitee_no_show
- organizations-create_organization_invitation
- organizations-revoke_organization_invitation
- shares-create_share
What Claude reads (25)
25 toolsYour profile, event types, bookings, availability, organization and routing forms, looked at and left alone.
users-get_current_user
Returns the Calendly user who is connected, so Claude knows whose calendar and whose event types it is working with before it answers anything else.
users-get_user
Fetches the profile of a specific Calendly user from its unique identifier, which Claude may need when a meeting or a membership points to someone else in your organization.
event_types-list_event_types
Lists the kinds of meetings a user or an organization offers: a short intro, a 30-minute demo, a paid consultation. Claude reads this catalogue before talking about any booking.
event_types-get_event_type
Opens a single event type in detail, with its duration, location and settings, so Claude answers precisely rather than from the name alone.
event_types-list_event_type_available_times
Looks up the free slots of an event type over a period. Claude can then tell you, or a prospect, exactly when you are bookable next week.
event_types-list_event_type_availability_schedules
Returns the availability schedules attached to an event type, meaning the weekly rules that decide when that meeting can be booked at all.
locations-list_user_meeting_locations
Lists the meeting locations a user has configured, such as a video platform, a phone number or a physical address. Claude uses it to say where a meeting will actually happen.
meetings-list_events
Lists the meetings already booked in your calendar. Claude can summarise your week, spot a crowded day or find the session you are thinking of.
meetings-get_event
Pulls the full details of one booked meeting: time, event type, location and status. Claude reads it when you point to a specific appointment.
meetings-list_event_invitees
Lists the people who booked a given meeting, which matters for group sessions, webinars or workshops where several guests share one slot and you need the full attendee list.
meetings-get_event_invitee
Returns what Calendly holds on one guest of one meeting, as Calendly exposes them for that booking. Claude can brief you on that person before the call.
availability-list_user_availability_schedules
Lists all the availability schedules a user has, for example a standard week and a summer week, so Claude can compare them side by side and tell you which one is active.
availability-get_user_availability_schedule
Opens one availability schedule in detail, with its daily hours and exceptions. Claude reads it to explain precisely when, and on which days, people can book you.
availability-list_user_busy_times
Returns the periods when a user is already occupied within a date range, as Calendly sees them. It helps Claude reason about your real load, not just your published hours.
meetings-get_invitee_no_show
Reads the record that marks a guest as absent from a meeting, so Claude can confirm that a no-show was logged, for which meeting, and when it was recorded.
organizations-get_organization
Retrieves the details of the Calendly organization you belong to. Claude uses it as context when your question concerns the whole team rather than your own calendar.
organizations-list_organization_memberships
Returns every member of your Calendly organization. Claude can answer who is on the account, as your own role lets you see it, and help you find the right colleague for a meeting.
organizations-get_organization_membership
Returns the details of one person's membership in the organization, such as their role. Useful when Claude has to tell an admin from a regular member.
organizations-list_organization_invitations
Lists the invitations to join your organization that nobody has accepted yet. Claude can remind you who is still waiting.
routing_forms-list_routing_forms
Lists the routing forms of your organization, those short questionnaires that route each visitor to the right person or event type.
routing_forms-get_routing_form
Opens one routing form in detail, with its questions and the rules that decide where each answer leads. Claude can explain the logic in plain words.
routing_forms-list_routing_form_submissions
Lists the answers people submitted through a routing form. Claude can count them, group them or spot a pattern in who is asking for what.
routing_forms-get_routing_form_submission
Retrieves a single submission of a routing form, with every answer the visitor gave. Claude reads it when you want the story behind one lead.
list_calendly_skills
Lists the skills Calendly makes available through the connector. Calendly documents the tool this way and does not detail what a skill contains, so Claude consults the list and nothing more is promised here.
load_calendly_skill
Retrieves one specific Calendly skill so Claude can use its content. The publisher describes it in one line, without detailing what each skill holds, so this page does not go further.
What Claude changes (11)
11 toolsTools that book, cancel, configure or invite. No source spells out their confirmation, so the general rule below applies.
event_types-create_event_type
Approval: see the ruleCreates a new kind of meeting in your account, with a name and duration, described by Calendly simply as a new event type in your account.
event_types-update_event_type
Approval: see the ruleUpdates the details of an existing event type, such as its name, duration or description. Calendly's documentation describes it as an update of the event type's details.
event_types-update_event_type_availability_schedule
Approval: see the ruleChanges the availability schedule of an event type, for instance removing a weekday from the hours people can pick.
meetings-cancel_event
Approval: see the ruleCancels a meeting that is already booked, on a real calendar with a real guest. It acts on someone else's agenda as well as yours.
meetings-create_invitee
Approval: see the rulePlaces a new booking on one of your event types for a named guest with an email address, at a time you choose.
scheduling_links-create_single_use_scheduling_link
Approval: see the ruleGenerates a booking link from an existing event type that works once and then expires, without any customisation.
meetings-create_invitee_no_show
Approval: see the ruleFlags a guest as absent from a meeting, which keeps your records honest and can feed your follow-up.
meetings-delete_invitee_no_show
Approval: see the ruleDeletes the no-show mark from a guest, for when someone was flagged absent by mistake or turned up late after all.
organizations-create_organization_invitation
Approval: see the ruleSends an invitation to join your Calendly organization to a given email address, from the conversation.
organizations-revoke_organization_invitation
Approval: see the ruleWithdraws a pending invitation to your organization before the person accepts it.
shares-create_share
Approval: see the ruleCreates a single-use booking link from an existing event type, but with customisations applied, unlike the plain single-use link above.
What Claude checks with you before acting
By default, Claude stops and asks before each action it carries out on an account for someone, right in the conversation.
On Team and Enterprise workspaces, owners decide whether members may let some actions through without a prompt each time. They can also restrict a connector across the organization, for example keeping availability lookups open while blocking bookings and cancellations, and nobody reverses that from a personal account. Claude acts with the rights of the person who connected: Calendly says the connector carries the same scopes and permissions as its public API. The official per-tool label lives only in a signed-in account's settings.
Which Claude plans include it
None of the 819 sheets in the official directory states plan availability. That answer is published nowhere, connector by connector.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner opens the connector for the organization before members connect. Calendly's own tiers are a separate matter, covered in the limits below. To see the live state for your account, open the connector's sheet in the official directory.
Where the Claude Calendly connector stops
A connector is not an automation. Claude calls these tools while answering you, so nothing happens by itself when someone books or cancels.
The tool list is an observed floor rather than a promise: an administrator can open actions that no public sheet lists. The partner badge is not a security audit, and Anthropic states on every sheet that it neither picks a publisher's tools nor vouches for their behaviour. Everything on this page comes from the directory sheet and Calendly's developer documentation; no Claude help article covers this connector. If you want an example of official sources that openly contradict each other, see the Claude gmail connector page.
Need help connecting Calendly to Claude?
A person reads every message.



