AI agents with Cal.com webhooks

Receive Cal.com webhooks on Trigger.dev and use them to start, resume or message your AI agents.

Get started now

What you can do with Cal.com webhooks

Start an agent

Cal.com events can start a new agent run. For example, an agent that preps for every new Cal.com booking.

Resume an agent

An agent can pause until the Cal.com event it needs arrives, for up to 90 days, and costs nothing while it waits.

Message an agent

Cal.com events can land in a running agent's conversation, so it acts on them with full context.

Events you can receive from Cal.com

Cal.com sends events like BOOKING_CREATED, BOOKING_CANCELLED, BOOKING_RESCHEDULED and MEETING_ENDED, and your agent can filter on any of them.

Example

An agent that preps for every new Cal.com booking

import { webhook, webhooks } from "@trigger.dev/sdk";
export const calCom = webhooks.endpoint.define({
id: "cal-com",
source: webhooks.calCom(),
});
export const calComEvents = webhook({
id: "cal-com-events",
endpoint: calCom,
filter: "event.triggerEvent == 'BOOKING_CREATED'",
onEvent: async ({ event }) => {
// Start, resume or message your agent with the event
console.log(event);
},
});

Handled for you

Verified for you

webhooks.calCom() checks the X-Cal-Signature-256 header on every request. Bad requests are rejected before anything runs.

Filter before anything runs

Only the Cal.com events you care about start a run. Filtered webhooks use no compute.

See every delivery

Every webhook is recorded with its payload, headers and the agents it reached, so you can debug it and replay it.

Get started

  1. 1

    Set up the agent

    Copy the starter prompt into your coding agent, like Claude Code, Cursor or Codex. It creates a Trigger.dev project and adds the webhook endpoint. Prefer to write it yourself? Start from the example above.

  2. 2

    Add the webhook in Cal.com

    Deploy your project, or run trigger dev, and the endpoint appears on the Webhooks page of the Trigger.dev dashboard with its URL. Add that URL in Cal.com's webhook settings and pick the events you need. The endpoint's Copy setup prompt button gives your coding agent the exact steps.

  3. 3

    Add a signing secret

    On the endpoint's page in the Trigger.dev dashboard, choose Generate secret. Then paste it into Cal.com's webhook settings, so Trigger.dev can check every request really came from Cal.com.

  4. 4

    Try it

    Send a test event from Cal.com, or use the endpoint's Test tab. It appears on the endpoint's Deliveries tab, with the agents it reached.

Related integrations

Ready to build with Cal.com webhooks?

Declare an endpoint, deploy, and paste the URL into your provider.

Get started for free