Menu
Mattering Automations connector

A Calendly MCP that knows a canceled event is a canceled meeting

Connect one Personal Access Token and your Calendly account becomes workflow steps: scheduled events with filters, invitees, event types and their available times, busy times, no-show markers, and single-use scheduling links. The one node that cancels a real meeting and emails real invitees is flagged accordingly.

22 ready-made nodes One credential to connect Works with Claude, ChatGPT, and Matter

What the Calendly MCP connector does

The Calendly connector for Mattering Automations is 22 nodes across API v2: the current user, event types (list, get, and their actual available times), scheduled events (list with time and status filters, get, cancel), invitees (list, get), invitee no-show markers (mark, get, unmark), single-use scheduling links, availability schedules and busy times, organization memberships, and webhook subscription management.

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An assistant can answer what is on the calendar this week, who booked, who showed up, and what slots are actually open, without anyone opening Calendly.

Because Mattering is a work platform rather than middleware, bookings land somewhere useful by default: a scheduled sweep over new events can open a prep task per meeting in Mattering Productivity, no-shows can drive follow-up sequences, and a single-use scheduling link can be minted inside any workflow that needs one specific person to book one specific slot.

Calendly's API has one quirk this connector absorbs for you: everything is identified by full URI rather than bare id, and the list endpoints require a user or organization URI to scope them. Calendly: Get Current User is the first node to run; it returns your user URI and organization URI, every node's help text says which one it wants, and the nodes accept either full URIs or bare UUIDs. The one genuinely consequential action is Calendly: Cancel Event, which cancels a real meeting and notifies real invitees, and is flagged destructive for exactly that reason.

One connection, three surfaces

  • Visual automations. Drag Calendly nodes onto the canvas and wire them to triggers, conditions, and other apps.
  • AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
  • The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.

Every Calendly node, ready to drop on the canvas

22 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.

Read and query nodes 16

Calendly: Get Current User

Fetch the account that owns the access token. This is the entry point for every Calendly flow: the response carries your user URI (data.resource.uri) and organization URI (data.resource.current_organization), which the list nodes require as inputs. Zero config, zero cost - also the credential health check.

Calendly: Get Event Invitee

Fetch one invitee on a scheduled event, including form answers, payment record, no-show marker, and reschedule/cancel links.

Calendly: Get Event Type

Fetch one event type: name, duration, scheduling URL, custom questions, locations. Pipe in an event type URI from List Event Types or a scheduled event's data.resource.event_type.

Calendly: Get Invitee No-Show

Fetch a no-show marker by its identifier (returned when the marker was created, or on the invitee's no_show field).

Calendly: Get Scheduled Event

Fetch one booked meeting: times, status, location, host memberships, guests, and the linked calendar event. Pipe in an event URI from List Scheduled Events or a webhook payload.

Calendly: Get User

Fetch a specific user's profile: name, email, timezone, scheduling URL. Pipe in a user URI from the memberships or scheduled-events nodes to resolve who a URI belongs to.

Calendly: Get User Availability Schedule

Fetch one availability schedule by identifier: name, timezone, and its day/date rules.

Calendly: Get Webhook Subscription

Fetch one webhook subscription: callback URL, subscribed events, scope, and state (active or disabled).

Calendly: List Event Invitees

List the people booked on a scheduled event, with their emails, form answers, UTM tracking, and reschedule/cancel links. The bridge from a meeting to CRM contact data.

Calendly: List Event Type Available Times

List the open, bookable time slots for an event type in a date range (max 31 days). Each slot carries a direct scheduling_url that books that exact time - useful for offering concrete times in an outreach message. No pagination on this endpoint.

Calendly: List Event Types

List the meeting types (15 Minute Meeting, Discovery Call, ...) defined for a user or across the whole organization. Provide EITHER the user field OR the organization field - Calendly requires one of them. Each result's data URI is what the availability and scheduling-link nodes take as their event_type input.

Calendly: List Organization Memberships

List an organization's members (with each member's embedded user profile and role), or look up a user's membership. Provide EITHER the organization field OR the user field. The way to resolve teammates' user URIs for the other nodes.

Calendly: List Scheduled Events

List booked meetings, filterable by time window, status, and invitee email. Provide the user field, the organization field (admin/owner token), or a group field - Calendly requires one of them. The classic daily-digest and meeting-sync node.

Calendly: List User Availability Schedules

List a user's availability schedules (Working Hours and any alternates): timezone plus the weekly-day and specific-date rules with their time intervals.

Calendly: List User Busy Times

List a user's busy blocks in a date range (max 7 days): Calendly meetings plus external calendar conflicts (external events appear only for calendars with 'check for conflicts' enabled). No pagination on this endpoint.

Calendly: List Webhook Subscriptions

List the webhook subscriptions registered for an organization, user, or group. Both organization and scope are always required; add the user or group field when scope is user or group.

Action nodes 6

Calendly: Cancel Event

DESTRUCTIVE: cancels a real booked meeting. Calendly notifies the invitees, and the cancellation cannot be undone from the API - the invitee would have to book again. Use only in flows where cancellation is the explicit intent (e.g. an approval step rejected the booking).

Calendly: Create Single-Use Scheduling Link

Create a one-time booking link for an event type: the link dies after a single booking. The workhorse for outreach automations - generate a fresh link per prospect and drop data.resource.booking_url into an email or SMS node.

Calendly: Create Webhook Subscription

Register a callback URL for Calendly events (invitee.created, invitee.canceled, invitee_no_show.created/deleted, event_type.created/updated/deleted, routing_form_submission.created, and more). Management only: this node registers the subscription; it is not an inbound trigger by itself. Point the URL at a Mattering Automations webhook trigger to receive the events in a flow.

Calendly: Delete Webhook Subscription

DESTRUCTIVE: permanently removes a webhook subscription. Whatever integration relied on it silently stops receiving events, and deliveries missed before it is recreated are gone. Recreating requires knowing the original URL, events, and signing key.

Calendly: Mark Invitee No-Show

Mark an invitee as a no-show after a missed meeting. Reversible: the Unmark Invitee No-Show node removes the marker. Feeds follow-up flows (no-show re-engagement emails, CRM flags).

Calendly: Unmark Invitee No-Show

Remove a no-show marker (undo of Mark Invitee No-Show). Classed as a reversible write, not destructive: the marker can be recreated at any time with the create node and nothing else is lost.

Connecting Calendly takes one credential

Calendly issues Personal Access Tokens from Integrations, then API and webhooks, in your Calendly account. The token authenticates as you and is sent as a bearer credential on every request. Rate limits are per minute and scale with plan; the read nodes sit comfortably inside them.

1

In Calendly, open Integrations, then API and webhooks, and generate a Personal Access Token.

2

In Mattering Automations, open Connectors, click Add Connector, choose Calendly, and create a credential with that token.

3

Click Test Connection. Mattering calls Calendly's current-user endpoint and confirms the token authenticates.

4

All 22 Calendly nodes appear in the canvas palette. Run Calendly: Get Current User first: it returns the user URI and organization URI that the list nodes require.

Common uses for the Calendly MCP

A meeting prep pipeline

Calendly: List Scheduled Events on a schedule, filtered to upcoming active events, opens a prep task per meeting in Mattering Productivity, and Calendly: List Event Invitees attaches who booked and the answers they gave to the booking questions. The meeting arrives with context instead of just a calendar block.

No-shows that trigger follow-up

After a meeting window passes, Calendly: List Event Invitees shows who was expected, Calendly: Mark Invitee No-Show records who did not appear, and the marker can drive a re-booking email or a task. Calendly: Unmark Invitee No-Show reverses a mistaken marker, so this loop is safe to automate.

Real availability, not guesses

Calendly: List Event Type Available Times returns the actual open slots for an event type over a date range, the same slots a booker would see. An assistant can answer when someone can meet, and a workflow can propose concrete times, straight from the calendar truth.

One link, one booking

Calendly: Create Single-Use Scheduling Link mints a link that works exactly once. Minted inside a workflow, it lets one specific contact book one slot, with no risk of the link circulating.

Attendance data where the records live

Scheduled events, invitees, and no-show markers can flow into a Mattering database on a schedule, building an attendance history per contact that feeds scoring, follow-up cadence, or simple reporting, without anyone exporting CSVs.

Webhook subscriptions managed from the canvas

Calendly: List Webhook Subscriptions, Calendly: Create Webhook Subscription, and the get and delete nodes manage org- or user-scoped subscriptions for invitee and event lifecycle events. Management only, and the connector says so: there is no inbound Calendly trigger, but the subscriptions can point at any URL you operate.

Example: Every booking becomes a prepped meeting, every no-show a follow-up

Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.

1

Trigger: a schedule runs every hour.

2

Calendly: Get Current User supplies the organization URI (run once; the value is reused).

3

Calendly: List Scheduled Events pulls events booked since the last run.

4

Calendly: List Event Invitees attaches each booker and their answers to the booking questions.

5

A task is created in Mattering Productivity per new meeting, carrying invitee context.

6

A second scheduled pass after each meeting window marks recorded no-shows with Calendly: Mark Invitee No-Show and opens a follow-up task for each.

Calendly MCP questions, answered

What Calendly operations are supported?

22 nodes: current user and user lookup, event types with their real available times, scheduled events (list with filters, get, cancel), invitees, no-show markers (mark, get, unmark), single-use scheduling links, availability schedules, busy times, organization memberships, and webhook subscription management. Deliberately not shipped: booking meetings on an invitee's behalf, event type creation and editing, organization invitations and member removal, and Calendly's permanent data-deletion endpoints, which never belong on an automation canvas.

Does this work with Claude, ChatGPT, or other AI assistants?

Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.

What are these URIs the nodes keep asking for?

Calendly's API identifies everything by full URI (like https://api.calendly.com/users/XXXX) rather than bare ids, and list endpoints require a user or organization URI to scope the query. Run Calendly: Get Current User once: it returns your user URI and your organization URI, and each node's help text says which one it wants. The nodes also accept bare UUIDs and expand them, so either form works.

Can this cancel real meetings?

Yes, and it is the one node to be careful with. Calendly: Cancel Event cancels an actual scheduled meeting, Calendly notifies the invitees, and there is no undo; rebooking means sending a new link. It is flagged destructive so it can be gated behind a condition, an approval step, or a manual run. Everything else in the connector is a read or a reversible marker.

Can a new booking trigger a workflow?

Not as a trigger node in this connector. The webhook nodes manage subscriptions rather than receiving events, so there is no inbound Calendly trigger. The honest pattern today is polling: run Calendly: List Scheduled Events on a schedule and act on events created since the last run. The subscriptions you manage can still point Calendly's invitee and event webhooks at any URL you operate.

Can this book a meeting for someone?

Not directly, by design: Calendly's API for booking on an invitee's behalf carries heavy restrictions and consent implications, so it is deliberately out of scope. The supported pattern is Calendly: Create Single-Use Scheduling Link, which mints a one-time link a workflow can send to exactly one person; they book themselves, and consent stays with the invitee.

How do the no-show nodes behave?

As a reversible marker, not a judgment. Calendly: Mark Invitee No-Show records that an invitee missed an event, Calendly: Get Invitee No-Show reads the marker, and Calendly: Unmark Invitee No-Show removes it if it was wrong. Because the marker is fully reversible, it is safe to automate against attendance data and correct later.

What do the availability nodes actually return?

Three different truths. Calendly: List Event Type Available Times returns the bookable slots for one event type over a date range, exactly as a booker would see them. Calendly: List User Busy Times returns the busy intervals on the user's connected calendars. Calendly: List User Availability Schedules returns the configured working-hours rules. Use available times for proposing slots; use busy times and schedules for understanding why a slot is not offered.

22 nodes waiting on the canvas

Put Calendly to work inside your workspace

Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.

All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Calendly is a product of its respective owner; Mattering is an independent platform.

Start Free Explore our Products