Calendly logoScheduling connector

Calendly in Claude, ChatGPT and any MCP client. For your whole team.

Events, invitees, event types, available slots, routing forms. One token in Loopthink, one login per person, roles per tool and an audit entry for every call.

Free for 2 connectors, no card · Pro €19 · EU-hosted · 15 read tools, 2 write tools off by default

Your AI clientCalendly

“Which demo calls are booked for the organization next week, with host and event type?”

Used list_scheduled_events from Calendly

Three demo calls are booked for next week:

Invitee companyHostEvent typeWhen
Nordwind HandelS. KellerProduct demo 45 minMon 26 Oct 10:00
Alpen LogistikM. BergerProduct demo 45 minTue 27 Oct 14:30
Kraus & PartnerS. KellerTechnical deep diveThu 29 Oct 11:00
  • read-only
  • masked
An example answer in an AI client: the question “Which demo calls are booked for the organization next week, with host and event type?” is answered from Calendly through the tool list_scheduled_events, and the call was read-only, masked.
In the product

One token in, the tools come out.

The Calendly connection form in Loopthink: the token
1. Connect. Paste the token, nothing else. The token stays in Loopthink; nobody on your team sees it.
The Tools tab of the Calendly server in Loopthink: each tool with its own switch
2. Choose the tools. Reads are on from the start; tools that change data stay off until you switch them on. Masking rules per tool keep personal fields out of the answer.

Calendly is where meetings get booked: event types such as the 30-minute intro call, the scheduled events that came out of them, the invitees with their answers to the booking questions, routing forms that qualify a lead before the slot is offered. The questions are small, "what demos are booked this week", "when does Jonas have a free slot on Thursday", but today they mean switching to Calendly, picking the right member and scrolling the list.

With the Calendly connector, Sales, Customer Success and Office Management ask in Claude or ChatGPT and get the answer from the live organization. Loopthink holds one personal access token, every person signs in with their own identity, and every call is logged under their name. The token never reaches the AI client.

Fifteen read tools cover the token owner, scheduled events and their invitees, event types and their open slots, busy times and availability schedules, organization members, routing forms with submissions and contacts. The two write tools, cancelling an event and creating a single-use scheduling link, stay off until you switch them on for a role.

What your team asks
  • Sales

    “Which demo calls are booked for the organization next week, with host and event type?”

    Answered by list_scheduled_events

  • Sales

    “When is the next free slot for the '30 min intro call' between Monday and Wednesday, in Berlin time?”

    Answered by list_event_type_available_times

  • Customer Success

    “What did the invitees of yesterday's 14:00 onboarding call answer to the question about their current tool?”

    Answered by list_event_invitees

  • Office Management

    “Is Jonas Weber busy tomorrow between 09:00 and 12:00?”

    Answered by list_user_busy_times

  • Marketing

    “How many submissions did the 'Enterprise inquiry' routing form get in October, and how many booked a meeting?”

    Answered by list_routing_form_submissions

  • Sales

    “Create a one-time booking link for the 'Technical deep dive' event type that I can send to Müller & Söhne.”

    Answered by create_single_use_scheduling_link

Tools

What the Calendly connector can do.

ToolWhat it doesAccessDefault
get_current_userReturns the token owner's profile. Call this first: resource.uri is the user URI and resource.current_organization is the organization URI that most other tools need as 'user' o…ReadOn
list_scheduled_eventsLists booked meetings (scheduled events). Pass either 'user' (user URI) or 'organization' (org URI, needs admin) from get_current_user.ReadOn
get_scheduled_eventGets one scheduled event (time, event type, location, hosts, cancellation). uuid is the last path segment of the event URI from list_scheduled_events.ReadOn
list_event_inviteesLists invitees (attendees) of one scheduled event, including their answers to booking questions. Contains personal data.ReadOn
get_event_inviteeGets one invitee of a scheduled event (name, email, status, answers, reschedule/cancel info).ReadOn
list_event_typesLists bookable event types (meeting templates such as '30 min intro call'). Either user or organization is required (URIs from get_current_user).ReadOn
get_event_typeGets one event type (duration, scheduling_url, location settings, custom questions).ReadOn
list_event_type_available_timesReturns open bookable slots of one event type. Use to answer 'when is there a free slot'.ReadOn
list_user_busy_timesReturns busy blocks of a user (Calendly events plus external calendar events where conflict checking is on). Range max 7 days, start not in the past.ReadOn
list_user_availability_schedulesLists the working-hours schedules (weekly rules, date overrides, timezone) of a user.ReadOn
list_organization_membershipsLists members of the organization with role. Use to find a colleague's user URI by email.ReadOn
list_routing_formsLists routing forms (qualification forms before booking) of the organization. Paid team plans only.ReadOn
list_routing_form_submissionsLists submissions of one routing form (answers, routing result, whether a meeting was booked). Contains personal data.ReadOn
get_routing_form_submissionGets one routing form submission with all answers.ReadOn
list_contactsLists Calendly contacts (people you met with). Filters: email/phone_number/timezone/country/state exact match, name/company/job_title/city partial match; each accepts a comma-se…ReadOn
cancel_eventWRITE: Cancels a scheduled event. Calendly notifies the invitees.WriteOff
create_single_use_scheduling_linkWRITE: Creates a one-time booking link for an event type (usable for exactly one booking). Returns resource.booking_url to send to a contact.WriteOff

Write tools are off for every role until you switch them on, one tool for one role. The names are what the model sees; it also gets the full parameter description of each tool.

Setup

Getting the Calendly token.

Five minutes, once. Nobody on your team ever sees it.

  1. 1

    Log in to Calendly and open Integrations, then the 'API & Webhooks' tile.

  2. 2

    Under Personal Access Tokens click 'Get a token now' (or 'Generate new token').

  3. 3

    Enter a name (e.g. 'Loopthink'), select the scopes below, click 'Create Token'.

  4. 4

    Copy the token immediately. Calendly does not show it again.

  5. 5

    In Loopthink, add Calendly from the catalog and paste the token. Your team sees the tools a minute later.

The token acts as the user who created it. Organization-wide reads (organization filter, memberships, routing forms) need an org admin or owner. New PATs have no API access until scopes are selected.

Masking

What we suggest masking in Calendly.

Every booking is a person: the invitee's name and email, the text reminder number, the answers to booking questions, who cancelled and why, the phone numbers, emails and LinkedIn profile on a contact. The suggested fields mask those and keep event times, event types, hosts, statuses and slot availability, which is what a scheduling question needs. Office Management sees that Thursday 10:00 is taken without seeing the customer's mobile number.

  • email
  • name
  • first_name
  • last_name
  • text_reminder_number
  • questions_and_answers
  • cancellation.reason
  • cancellation.canceled_by
  • phone_numbers
  • emails
  • linkedin
  • invitee_email
Questions

Calendly and Loopthink

Which scopes does the token need?
users:read, scheduled_events:read, event_types:read, availability:read, organizations:read, routing_forms:read and contacts:read for the read tools. Add scheduled_events:write only if a role should use cancel_event, and scheduling_links:write only for create_single_use_scheduling_link. A new token has no API access at all until scopes are selected.
Why do we only see one person's meetings?
The token acts as the user who created it. Organization-wide reads, the organization filter, memberships and routing forms, need a token from an org admin or owner. Create it with a dedicated admin user so the view covers the team.
Can the AI cancel a meeting?
Only if you switch cancel_event on for a role. Calendly then notifies the invitees and the cancellation cannot be undone, which is why the tool asks for confirmation first and why most teams leave it off.
Does every team member need their own Calendly account?
No. Loopthink holds one key or token for Calendly. Your people sign in to Loopthink with their own identity, and every call to Calendly is logged under their name. Seats in Calendly stay where they are today.
Where does the Calendly key live?
In Loopthink, encrypted, in the EU. It never reaches the AI client and never reaches the people using the connector. Rotate it in Calendly whenever you like and paste the new one once.
Can somebody write to Calendly from the chat?
Not unless you switch it on. Write actions are a separate row in the permission matrix and are off for every role by default. If a role needs one write tool, you grant that one tool to that one role.
What does the model see?
The result of the tool call, after masking. Fields you mark as personal, such as emails, names or card details, are masked before the answer travels to the AI client. The model gets the numbers, not the people.
What does it cost?
Free for one person and two connectors, no card. Pro is €19 a month for up to five people and every connector on the site, with roles, field masking and a 30-day audit. Team is €49 for ten people and adds your own REST APIs and SQL databases, your own domain and your own identity provider. No call needed.

Stuck, or a tool you need is missing? A person who knows this connector answers within one working day.

Works in Claude, ChatGPT, Langdock and any other MCP client.