CONNECT APP
Build with Cal.com
Business Management
- API key
MCP
Give your agent Cal.com tools
Every Cal.com action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Cal.com account for each tool call — you store no tokens.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "cal_com",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Cancel Booking:
const result = await mcp.callTool({
name: "cal_com-delete-booking",
arguments: {
bookingId: "Booking ID",
cancellationReason: "Cancellation Reason",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", # any stable ID for this user in your system
"x-pd-app-slug": "cal_com",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Cancel Booking:
result = await session.call_tool("cal_com-delete-booking", {
"bookingId": "Booking ID",
"cancellationReason": "Cancellation Reason",
})API PROXY
Call the Cal.com API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Cal.com API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://api.example.com/v1/me",
})
// Any allowed Cal.com endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://api.example.com/v1/me
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkuZXhhbXBsZS5jb20vdjEvbWU?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Cal.com actions from your backend
Connect a user's Cal.com account once, then run Cancel Booking on their behalf from your own code — TypeScript, Python, or plain HTTP.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "cal_com-delete-booking",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
cal_com: { authProvisionId: "apn_xxxxxxx" },
bookingId: "Booking ID",
cancellationReason: "Cancellation Reason",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="cal_com-delete-booking",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"cal_com": {"authProvisionId": "apn_xxxxxxx"},
"bookingId": "Booking ID",
"cancellationReason": "Cancellation Reason",
},
)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "cal_com-delete-booking",
"configured_props": {
"cal_com": { "authProvisionId": "apn_xxxxxxx" },
"bookingId": "Booking ID",
"cancellationReason": "Cancellation Reason"
}
}'TOOLS
Cal.com actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Cancel Booking
actionCancel an existing booking by its UID. Note: Cal.com v2 replaces the v1 delete endpoint with a cancellation flow; the booking is marked cancelled rather than removed. See the documentationWritev0.1.1 -
Create Booking
actionCreate a new booking. See the documentationWritev1.0.1 -
Create Booking (V2)
actionCreate a booking using Cal.com API v2 (Option 1). See documentationWritev0.0.1 -
Get All Bookings
actionRetrieve all bookings from Cal.com. See the documentationRead-onlyv1.0.0 -
Get Bookable Slots
actionRetrieve available bookable slots between a datetime range. See the documentationRead-onlyv1.0.1 -
Get Booking
actionRetrieve a booking by its UID. See the documentationRead-onlyv1.0.0 -
List Event Type ID Options
actionRetrieves available options for the Event Type ID field.Read-onlyv0.0.1
EVENTS
Cal.com triggers
Event sources your backend can deploy for users and receive through a webhook.
-
Booking Cancelled
triggerEmit new event when a booking is cancelled.Instantv1.0.0 -
Booking Ended
triggerEmit new event when a booking ends.Instantv1.0.0 -
Booking Rescheduled
triggerEmit new event when a booking is rescheduled.Instantv1.0.0 -
New Booking Created
triggerEmit new event when a new booking is created.Instantv1.0.0
MULTI-APP
Use Cal.com with other popular apps
Most products don't stop at one integration. Pair Cal.com with the other apps your users rely on, and ship use cases that span both.
- App slug
- cal_com
- Authentication
- API key
- Categories
- Business Management
- Actions
- 7
- Triggers
- 4
- API proxy
- Available