Cal.com
Read and manage Cal.com bookings, event types and schedules — the open-source scheduling platform.
About
Cal.com ships in the w6w first-party pack. It declares 8 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.cal- Version
- 0.1.3
- Author
- w6w
- Licence
- MIT
- Categories
- Calendar & Scheduling
Overview
Cal.com is an open-source scheduling platform, and this app puts its bookings, event types and schedules into a workflow: list, fetch, create, cancel and reschedule bookings by their own id, and read the event types and schedules configured on the account.
Cal.com’s newer API versions each endpoint group independently rather than the whole API at once, so a workflow calling through this app is automatically talking to the version each action was built and verified against — one less thing to track when Cal.com ships a change underneath. Creating a booking takes a structured location object — an attendee address, a video integration, and so on — rather than a bare string, matching what the vendor’s API actually expects.
Build with Cal.com
Three routes to the same 8 actions. The Workflow tab is generated from Cal.com's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
List Bookings
booking-get-many List bookings, optionally filtered by status, attendee, event type or date range.
Reschedule Booking
booking-reschedule Move a booking to a new start time (POST /bookings/{uid}/reschedule).
List Event Types
event-type-get-many List event types, optionally scoped to a username or organization.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Cal.com's real ids.
{
"manifestVersion": "2",
"name": "cal-example",
"steps": [
{
"id": "booking-create",
"uses": {
"app": "io.w6w.cal",
"action": "booking-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"eventTypeId": "<eventTypeId>",
"start": "<start>",
"attendeeName": "<attendeeName>"
}
}
]
}Here are some of the things you can do
-
Create Booking
performbooking-create -
Get Booking
readbooking-get -
List Bookings
readbooking-get-many -
Reschedule Booking
performbooking-reschedule -
Get Event Type
readevent-type-get
+3 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Cal.com, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Cal.com. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "booking-create",
payload: {
eventTypeId: "<value>",
start: "<value>",
attendeeName: "<value>",
attendeeTimeZone: "<value>",
// attendeeEmail: "<value>",
// attendeePhoneNumber: "<value>",
// attendeeLanguage: "<value>",
// guests: "<value>",
// location: "<value>",
// lengthInMinutes: "<value>",
// metadata: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action booking-create --payload '{"eventTypeId":"<value>","start":"<value>","attendeeName":"<value>","attendeeTimeZone":"<value>"}'Give an AI agent Cal.com — without giving it Cal.com's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.cal#booking-create",
"input": {
"eventTypeId": "<eventTypeId>",
"start": "<start>",
"attendeeName": "<attendeeName>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Cal.com connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Cal.com's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Cal.com itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Cal.com declares its own checks, so its health is a property of the app rather than something the host guesses at.
Cal.com platform status
status.cal.com summary API, with per-component detail. Unauthenticated and unsigned.