Mattering Automations Calendly integration
Connect Calendly to Mattering Automations: scheduled events, invitees, event types with available times, no-show markers, scheduling links, and webhook management as workflow steps, authenticated with a Calendly Personal Access Token.
The Mattering Automations Calendly integration adds Calendly to your automation canvas: list and read scheduled events with their invitees, browse event types and their real available times, mark and unmark no-shows, mint single-use scheduling links, read availability schedules and busy times, and manage webhook subscriptions.
Setup takes a couple of minutes: generate a Personal Access Token in Calendly, attach it as a credential in Mattering, and test the connection. This guide walks through each step and ends with the full node reference.
Two things define this API. First, Calendly identifies everything by full URI rather than bare id, and list endpoints need a user or organization URI to scope them: Calendly: Get Current User returns both, so it is always the first node to run. Second, Calendly: Cancel Event cancels a real meeting and Calendly notifies the real invitees, so it is flagged destructive and belongs behind a condition or approval.
Before you start
- A Calendly account. The read surface works on the free plan; webhook subscriptions require a paid Calendly plan.
- Permission to generate a Personal Access Token under Integrations, then API and webhooks.
- A Mattering workspace with access to the Automations app.
Create a Calendly Personal Access Token
Mattering authenticates to Calendly with a Personal Access Token, sent as a bearer credential on every request. The token acts as you: it sees the events, event types, and organization your Calendly user can see.
Connect Calendly to Mattering
Verify it works
After connecting, open any automation canvas and check the palette: a Calendly section should list the query and action nodes. Drop Calendly: Get Current User onto the canvas and run a test step. It takes no configuration and returns your profile, including the two values everything else needs: your user URI and your organization URI.
Then run Calendly: List Event Types with your user URI, and Calendly: List Scheduled Events with either URI, to confirm the scoped list surface end to end. Everything in this path is read-only; nothing here can touch a real meeting.
Node reference
22 nodes, generated from the connector itself so this reference always matches what ships.
Read and query nodes 16
Calendly: Get Current User
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
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
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
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
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
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
calendly_get_user_availability_schedule
Fetch one availability schedule by identifier: name, timezone, and its day/date rules.
Calendly: Get Webhook Subscription
calendly_get_webhook_subscription
Fetch one webhook subscription: callback URL, subscribed events, scope, and state (active or disabled).
Calendly: List Event Invitees
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
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
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
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
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
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
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
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
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
calendly_create_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
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
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
calendly_create_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
calendly_delete_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.
Using the integration
On the automation canvas
Calendly nodes chain with every other node: a scheduled Calendly: List Scheduled Events sweep can open a prep task per new booking in Mattering Productivity, Calendly: List Event Invitees attaches who booked and their answers, and attendance history can accumulate in a Mattering database for follow-up and reporting.
From AI assistants over MCP
Every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and Matter can answer what is booked, who attended, and which slots are genuinely open through the same nodes your workflows use. The read surface is 16 of the 22 nodes, which makes this a naturally agent-safe connector.
The URI model, in practice
Run Calendly: Get Current User once and reuse its outputs: list nodes scope by user URI or organization URI (each node's help text says which), and detail nodes accept the full URIs that list responses carry, or bare UUIDs, interchangeably. When a node complains about a missing scope parameter, the fix is piping in one of those two URIs.
No-shows as a reversible loop
Calendly: Mark Invitee No-Show records a miss, Calendly: Get Invitee No-Show reads the marker, and Calendly: Unmark Invitee No-Show reverses it, so attendance automation is safe to run and correct later. Pair with Calendly: List Event Invitees after each meeting window to drive follow-up sequences.
Cancellation is the one sharp edge
Calendly: Cancel Event cancels an actual meeting and Calendly emails the invitees; there is no undo, and rebooking means a new link. Keep it behind a condition, an approval step, or a manual run. For the inverse need, getting someone booked, use Calendly: Create Single-Use Scheduling Link: one link, one booking, sent by the workflow to exactly one person.
Webhooks managed, not received
Calendly: List Webhook Subscriptions, Calendly: Get Webhook Subscription, Calendly: Create Webhook Subscription, and Calendly: Delete Webhook Subscription manage org- or user-scoped subscriptions for invitee and event lifecycle events. There is no inbound Calendly trigger in this integration; subscriptions can point at any URL you operate, and scheduled event sweeps cover polling. Webhook subscriptions require a paid Calendly plan.
Troubleshooting
Test Connection fails with a 401
A list node fails asking for user or organization
A node rejects an id that looks correct
Create Webhook Subscription is refused
Cancel Event fails on a past or already-canceled event
Available times look wrong or empty
Calls fail with a 429 rate limit
Related
The Calendly MCP
What connecting Calendly unlocks for AI agents and automations, with common uses and FAQs.
More guides
All Automations documentation
Every integration guide, plus how connectors, credentials, and workflows fit together.
Calendly is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.