Menu

Mattering Automations Cal.com integration

Connect Cal.com to Mattering Automations: live availability lookups, safe slot holds, the full booking lifecycle, event types, schedules with date overrides, connected calendars and busy times, and webhooks as automation triggers, authenticated with one API key.

The Mattering Automations Cal.com integration adds the Cal.com API v2 to your automation canvas: list and manage event types, work the booking lifecycle from listing and lookup through create, cancel, reschedule, confirm, decline, and no-show marking, manage availability schedules with date overrides, look up bookable slots live and hold one with a temporary reservation, read connected calendars and their busy times, manage the webhooks that turn bookings into workflow triggers, and read teams.

The credential is an API key created in the Cal.com web app on the settings page under the Security tab and sent as a Bearer header. Test-mode keys are prefixed cal_ and live-mode keys cal_live_. Setup takes a few minutes, and this guide walks through each step, including the webhook subscription that makes new bookings start workflows, and ends with the full node reference. One thing you never manage here: Cal.com v2 versions its endpoint families independently through a cal-api-version header, and the integration pins the current documented version per family automatically, so every response arrives in the current shape.

The safety modeling is stated on the nodes rather than buried, because scheduling actions reach real inboxes. Of the 34 nodes, 16 read and 18 act, and eight carry a destructive flag: Cal.com: Create Booking, Cal.com: Cancel Booking, Cal.com: Reschedule Booking, Cal.com: Confirm Booking, and Cal.com: Decline Booking each send real email to attendees or hosts that cannot be recalled, and Cal.com: Delete Event Type, Cal.com: Delete Schedule, and Cal.com: Delete Webhook cannot be undone. The slot reservation pair is deliberately the safe counterpart: Cal.com: Reserve Slot holds a time without emailing anyone and expires on its own.

Before you start

  • A Cal.com account. Cal.com has a free individual tier, and API keys are created from the standard settings page, so this integration can be set up and exercised without a paid plan.
  • At least one event type on the account. The slot, reservation, and booking nodes all address an event type by id; Cal.com: List Event Types is how you find those ids.
  • For Cal.com: Get Busy Times, a connected calendar (Google, Outlook, Apple, or another provider) on the Cal.com account. Connecting a calendar is done in the Cal.com app; this integration reads connections but deliberately does not manage them.
  • For Cal.com: List Teams and Cal.com: Get Team, the account must belong to a team; on a personal account both simply return nothing useful.
  • A Mattering workspace with access to the Automations app.

Create a Cal.com API key

Mattering authenticates to Cal.com with an API key sent as a Bearer header on every request. The key acts as the account it belongs to: it sees that account's event types, bookings, schedules, and webhooks, so mint it on the account that owns the scheduling your workflows will run. Cal.com also offers OAuth client credentials through its separate Platform product; this integration uses the standard API key, which works for every regular account.

Sign in to Cal.com, open Settings, and go to the Security tab.
Select API Keys and create a new key.
Copy the key and store it where your automation secrets live. Anyone holding the key can read and change this account's scheduling, including sending real booking emails, so treat it like a password. If a key leaks, revoke it from the same screen and mint a replacement.
Cal.com key prefixes tell you what you are holding: test-mode keys start with cal_ and live-mode keys with cal_live_. If workflows seem connected but touch none of your real bookings, check which mode of key you pasted.

Connect Cal.com to Mattering

In Mattering Automations, open Connectors and click Add Connector.
Choose Cal.com from the list.
Click Create new credential, paste the API key, and save.
The credential is stored encrypted in Google Secret Manager and never appears in workflow logs.
Click Test Connection. Mattering calls Cal.com's authenticated profile endpoint: a success returns the account's id, username, and email, and an error means the key is mistyped or revoked. No version header is involved on this endpoint, so the test isolates the credential itself.
Click Connect. All 34 Cal.com nodes appear in your canvas palette.

Verify it works

After connecting, open any automation canvas and check the palette: a Cal.com section should list the query and action nodes. Drop Cal.com: Get My Profile onto the canvas and run a test step. It is the integration's universal probe: it works with any valid API key and returns the account's id, username, email, and timezone without echoing the secret. If this node succeeds, the credential is healthy.

Next, run Cal.com: List Event Types and copy an event type id, because the slot, reservation, and booking-creation nodes all ask for one, then Cal.com: List Schedules to see the account's availability schedules and which is the default. To see availability end to end, give Cal.com: Get Available Slots that event type id and a date range; a map of dates to slot times means the whole read path works, and an empty object is a valid answer that means nothing is free in that window. Everything in this verify path is read-only: it cannot reach the eight destructive nodes and emails no one, so it is safe to re-run whenever you rotate the key.

Node reference

34 nodes, generated from the connector itself so this reference always matches what ships.

Read and query nodes 16

Cal.com: Get Available Slots

calcom_get_available_slots

Look up bookable time slots for an event type between two dates. Returns a map keyed by date, each date holding an array of slot start times (or start plus end when format is range); an empty object means nothing is free. This is a live availability lookup: re-query it rather than caching results.

Cal.com: Get Booking

calcom_get_booking

Fetch one booking by its UID: status, times, hosts, attendees, location, and booking-field responses. For a recurring booking the UID of the whole series returns every recurrence.

Cal.com: Get Booking Attendees

calcom_get_booking_attendees

List every attendee on a booking with name, email, timezone, language, phone number, and absence flag.

Cal.com: Get Busy Times

calcom_get_busy_times

Read busy intervals from a connected calendar between two dates: each row has a start, an end, and a source. This is a live free-busy lookup: re-query it rather than caching results.

Cal.com: Get Default Schedule

calcom_get_default_schedule

Fetch the account's default availability schedule: the one event types use unless they pin another.

Cal.com: Get Event Type

calcom_get_event_type

Fetch one event type by ID: title, slug, duration, locations, booking fields, buffers, limits, schedule, and the public booking URL.

Cal.com: Get My Profile

calcom_get_my_profile

Fetch the authenticated Cal.com account: id, username, email, timezone, week start, locale, and default schedule id. Works with any valid API key, so it doubles as the connection test.

Cal.com: Get Schedule

calcom_get_schedule

Fetch one availability schedule by ID: weekly hours per day, timezone, and date overrides.

Cal.com: Get Team

calcom_get_team

Fetch one team by ID: name, slug, branding, timezone, and whether it is an organization.

Cal.com: Get Webhook

calcom_get_webhook

Fetch one webhook by ID: subscriber URL, trigger events, active flag, secret, and payload template.

Cal.com: List Bookings

calcom_list_bookings

List the account's bookings with attendees, hosts, status, and times. Filter by one status (upcoming, past, cancelled, unconfirmed, recurring), attendee, event type, team, or date range. Cursor-paginated at this API version: pass data.pagination.nextCursor back as cursor until data.pagination.hasMore is false.

Cal.com: List Calendars

calcom_list_calendars

List the account's connected calendars (Google, Outlook, Apple, and others) with each connection's credentialId and the calendars inside it, plus the destination calendar new bookings are written to. Note the payload is an object: connections are at data.data.connectedCalendars[].

Cal.com: List Event Types

calcom_list_event_types

List event types with their titles, slugs, durations, locations, booking fields, and booking URLs. Leave the filters blank to list the authenticated account's event types; pass username to read another user's public event types.

Cal.com: List Schedules

calcom_list_schedules

List the authenticated account's availability schedules with their weekly hours, timezone, date overrides, and which one is the default.

Cal.com: List Teams

calcom_list_teams

List the teams the authenticated account belongs to, with names, slugs, and branding. Team ids feed the bookings lister's team filter.

Cal.com: List Webhooks

calcom_list_webhooks

List the account's webhooks with their subscriber URLs, trigger events, active flags, and payload template.

Action nodes 18

Cal.com: Cancel Booking

calcom_cancel_booking

DESTRUCTIVE: cancel a booking. This SENDS REAL CANCELLATION EMAILS to the attendees and host, which cannot be recalled, so this node must never run in a blind test matrix. The booking's status becomes cancelled and its calendar events are removed.

Cal.com: Confirm Booking

calcom_confirm_booking

DESTRUCTIVE: accept a booking that is pending host confirmation. This SENDS THE REAL CONFIRMATION EMAIL to the booker, which cannot be recalled, so this node must never run in a blind test matrix. The booking's status becomes accepted and calendar events are created.

Cal.com: Create Booking

calcom_create_booking

DESTRUCTIVE: book a real meeting on the event owner's calendar. This SENDS REAL CONFIRMATION EMAILS to the attendee and the host, which cannot be recalled, so this node must never run in a blind test matrix; verify the attendee address upstream. The slot must be available (check with Cal.com: Get Available Slots). Cancelling afterwards emails everyone again.

Cal.com: Create Event Type

calcom_create_event_type

Create an event type on the authenticated account: title, slug, and duration are required; locations default to Cal Video when omitted. The response includes the new id and public booking URL. Reversible with Cal.com: Delete Event Type.

Cal.com: Create Schedule

calcom_create_schedule

Create an availability schedule. Without an availability array Cal.com applies its documented default of Monday to Friday, 09:00 to 17:00. Reversible with Cal.com: Delete Schedule.

Cal.com: Create Webhook

calcom_create_webhook

Subscribe a URL to the account's booking events: created, rescheduled, cancelled, no-show, and more. Cal.com POSTs the event payload to the URL as things happen; this is the standard way to trigger an automation from Cal.com. Reversible with Cal.com: Delete Webhook.

Cal.com: Decline Booking

calcom_decline_booking

DESTRUCTIVE: reject a booking that is pending host confirmation. This SENDS A REAL REJECTION EMAIL to the booker, which cannot be recalled, so this node must never run in a blind test matrix. The booking's status becomes rejected.

Cal.com: Delete Event Type

calcom_delete_event_type

DESTRUCTIVE: delete an event type. Its booking page stops working immediately and the configuration cannot be restored; existing bookings made through it are not cancelled.

Cal.com: Delete Schedule

calcom_delete_schedule

DESTRUCTIVE: delete an availability schedule. Its weekly hours and overrides cannot be restored, and event types pinned to it fall back to other availability.

Cal.com: Delete Slot Reservation

calcom_delete_slot_reservation

Release a temporary slot hold early, making the slot bookable again. Holds are ephemeral and expire on their own, so nothing permanent is lost; re-reserving recreates the hold.

Cal.com: Delete Webhook

calcom_delete_webhook

DESTRUCTIVE: delete a webhook. Event deliveries to its URL stop immediately and the subscription (including its secret and template) cannot be restored; pause with Cal.com: Update Webhook (active false) if the stop should be temporary.

Cal.com: Mark Booking Absence

calcom_mark_booking_absent

Record a no-show on a past booking: mark the host or specific attendees absent. Reversible by calling again with absent false. Note no-show marks can fire the account's webhooks and workflows.

Cal.com: Reschedule Booking

calcom_reschedule_booking

DESTRUCTIVE: move a booking to a new start time. This SENDS REAL RESCHEDULE EMAILS to the attendees and host, which cannot be recalled, so this node must never run in a blind test matrix. A new booking is created and the old one is marked rescheduled; the response is the NEW booking with its new uid.

Cal.com: Reserve Slot

calcom_reserve_slot

Place a temporary hold on a slot so nobody else can book it while a flow completes. The hold expires on its own after reservationDuration minutes (default 5) and emails no one. Release early with Cal.com: Delete Slot Reservation using the returned reservationUid.

Cal.com: Update Event Type

calcom_update_event_type

Update an event type. Only fields you fill are sent, so existing settings are untouched; note bookingFields and locations REPLACE the whole existing array when sent. Reversible by writing the previous values back (read them first with Cal.com: Get Event Type).

Cal.com: Update My Profile

calcom_update_my_profile

Update the authenticated account's profile: name, email, timezone, week start, time format, default schedule, locale, bio, or avatar. Only fields you fill are sent; reversible by writing the previous values back (read them first with Cal.com: Get My Profile).

Cal.com: Update Schedule

calcom_update_schedule

Update an availability schedule: rename it, change its timezone, replace its weekly hours or overrides, or make it the default. Only fields you fill are sent; reversible by writing the previous values back (read them first with Cal.com: Get Schedule).

Cal.com: Update Webhook

calcom_update_webhook

Update a webhook: change its URL, trigger events, payload template, or pause it with active false. Only fields you fill are sent; reversible by writing the previous values back (read them first with Cal.com: Get Webhook).

Using the integration

On the automation canvas

Cal.com nodes chain with every other node: a webhook subscribed with Cal.com: Create Webhook fires a workflow the moment someone books, Cal.com: Get Booking fetches the full detail, and the workflow writes the attendee into a Mattering database and opens a prep task in Mattering Productivity. Two ids do most of the addressing work: the event type id from Cal.com: List Event Types feeds the slot and booking nodes, and the booking uid from Cal.com: List Bookings feeds everything that acts on one booking.

From AI assistants over MCP

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and Matter can drive the same surface. An agent can read availability with Cal.com: Get Available Slots, hold a time with Cal.com: Reserve Slot while it confirms details, and book with Cal.com: Create Booking once a person has verified the attendee's address. The read nodes are the safest surface to hand an agent; keep the five email-sending booking nodes behind conditions or approval steps.

Webhooks as the trigger surface

Cal.com: Create Webhook subscribes a URL to the account's booking events: created, rescheduled, cancelled, no-show, and more, and Cal.com POSTs the event payload to that URL as things happen, which is the standard way to start an automation from Cal.com. Cal.com: Update Webhook changes the URL or trigger events, and pausing is a first-class move: set active to false rather than deleting, because Cal.com: Delete Webhook is destructive and takes the subscription's secret and template with it. One replacement rule to know: the triggers array on an update replaces the existing array entirely, so send the full list you want, not just the additions.

The booking lifecycle, with the emails stated plainly

Five nodes send real email that cannot be recalled: Cal.com: Create Booking confirms to the attendee and host, Cal.com: Cancel Booking sends cancellations, Cal.com: Reschedule Booking sends reschedule notices, and Cal.com: Confirm Booking and Cal.com: Decline Booking answer a booker who is waiting on host confirmation. All five are flagged destructive so workflows gate them; the honest pattern puts an approval task or a verified condition in front of each. Two mechanics worth knowing: a reschedule creates a new booking and returns it with a new uid, so downstream steps must use the returned uid rather than the old one, and Cal.com: Mark Booking Absence is the reversible member of the family, flipping back with absent false.

Slot holds: the safe middle step

Cal.com: Reserve Slot places a temporary hold on a slot so nobody else can book it while a flow completes, and it emails no one. The hold expires on its own after the reservation duration, five minutes by default, and Cal.com: Delete Slot Reservation releases it early using the reservationUid the reserve node returned; that uid exists nowhere else, so carry it through the workflow. The designed-for sequence is look, hold, verify, book: Cal.com: Get Available Slots finds the time, the hold protects it, a person or an upstream check verifies the attendee, and only the final step sends mail. Availability answers are live, so re-query rather than cache them.

Reading the responses: the data.data shape

Cal.com wraps every response in its own envelope, and the connector's envelope carries that body as data, so downstream paths are double-nested: a list's first id is at data.data[0].id and a booking's uid at data.data.uid. Three shapes to know beyond that. Cal.com: List Bookings is cursor-paginated: pass data.pagination.nextCursor back as the cursor input until data.pagination.hasMore is false. Cal.com: Get Available Slots returns a date-keyed map, not an array, and an empty object means nothing is free. Cal.com: List Calendars returns an object whose connections live at data.data.connectedCalendars, with the destination calendar for new bookings beside them.

Troubleshooting

Test Connection fails with an authentication error
The profile endpoint accepts any valid API key, so a failure here is about the key itself. Check for leading or trailing whitespace from the copy, and confirm the key still exists in Cal.com under Settings, Security, API Keys: a revoked key fails exactly like a wrong one. If the key was minted on a different Cal.com account than the one whose scheduling you expected, the test can even pass while every later node reads the wrong account's data, so confirm the returned username matches the account you meant.
A downstream step finds nothing at data[0] even though the node succeeded
Cal.com wraps responses in its own envelope and the connector carries that whole body as data, so results are one level deeper than you might expect: data.data[0].id for a list, data.data.uid for a single booking. Repoint the downstream path at data.data and it resolves. The calendars node adds one more level of shape: connections are at data.data.connectedCalendars, an object rather than an array.
Cal.com: Get Available Slots returns an empty object
An empty object is a valid answer meaning nothing is bookable in that window, not an error. Check the obvious causes in order: the date range is in the past or too narrow, the event type's schedule has no working hours on those days, a date override blocks them, or existing bookings and buffers have consumed the window. The lookup is live, so if bookings changed since the last run, the answer legitimately changed too. Confirm the schedule with Cal.com: Get Schedule and widen the range before suspecting the credential.
Cal.com: Create Booking fails because the slot is no longer available
Someone took the slot between the lookup and the booking, which is a race the API design expects you to close with a hold: run Cal.com: Reserve Slot immediately after picking a time, and the slot stays yours for the reservation duration, five minutes by default, while the workflow confirms details. If the booking still fails with a hold in place, re-run Cal.com: Get Available Slots rather than retrying blind; availability answers are live and the workflow should re-pick from current truth.
Cal.com: List Bookings returns fewer bookings than exist
The bookings list is cursor-paginated. One call returns one page plus data.pagination.nextCursor and data.pagination.hasMore beside the results; pass nextCursor back as the cursor input and loop until hasMore is false. Filters also narrow silently: the status filter takes one status at a time, so a list filtered to upcoming will never show cancelled or past bookings no matter how many pages you read.
Cal.com: Confirm Booking or Cal.com: Decline Booking fails on a booking
Both nodes only apply to bookings that are pending host confirmation, which exist only for event types that require confirmation. A booking that was auto-accepted at creation has nothing to confirm, and a booking already confirmed or declined cannot be answered twice. Read the booking first with Cal.com: Get Booking and check its status; if the workflow is a confirmation queue, drive it from Cal.com: List Bookings filtered to unconfirmed so it only ever sees bookings these nodes can act on.
A webhook stops delivering events
Check the webhook with Cal.com: Get Webhook first: if active is false, it was paused, and Cal.com: Update Webhook with active true resumes it. If the trigger list looks shorter than you remember, a previous update replaced the whole triggers array rather than adding to it, so send the complete list you want. If the webhook is gone entirely, it was deleted; deletion is destructive and unrecoverable, so re-create it with Cal.com: Create Webhook and update the workflow with the new subscription.
Cal.com: Get Busy Times fails or needs ids you cannot find
The node addresses a calendar by a credentialId and externalId pair, and both come from Cal.com: List Calendars: each connection at data.data.connectedCalendars carries its credentialId, and each calendar inside a connection carries its externalId. Copy the pair from the same connection, because a credentialId from one connection with an externalId from another matches nothing. If the calendars list itself is empty, no calendar is connected to the Cal.com account yet, and connecting one is done in the Cal.com app rather than through this integration.
Nodes start failing with rate-limit errors during a sweep
Cal.com documents a default limit of 120 requests per minute for API-key authentication. A workflow paging through a long booking history or fanning out per-booking lookups can reach it. The nodes report the rate-limit response on their output rather than silently retrying, so add a wait step between pages, spread scheduled sweeps apart, and prefer one filtered Cal.com: List Bookings call over many Cal.com: Get Booking calls. Cal.com notes the limit can be increased by contacting them if a legitimate workload needs more.

Cal.com 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.

Start Free Explore our Products