List Bookings: Cal.com action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Status status	options	Optional	Status. Options: All, Upcoming, Past, Cancelled, Recurring
Limit take	string	Optional	Limit. e.g. "10"

Sample request

{
  "status": "{{trigger.status}}",
  "take": "10"
}

Returns

{
  "data": [
    {
      "id": 123,
      "uid": "abc-123",
      "title": "30 Minute Meeting",
      "status": "accepted",
      "endTime": "2026-04-15T14:30:00Z",
      "attendees": [
        {
          "name": "John",
          "email": "john@example.com"
        }
      ],
      "startTime": "2026-04-15T14:00:00Z"
    }
  ],
  "status": "success"
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about List Bookings.

What does the List Bookings action do in Cal.com?

Paginated bookings filterable by status, time range, host, event type. The base query for daily-summary workflows ("here's today's schedule") and for booking-volume reporting.

What inputs does List Bookings require?

List Bookings has no required inputs. Sensible defaults are applied if you leave fields blank.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Cal.com returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Bookings support batch operations?

Yes. Run List Bookings inside a Loop node to process arrays. Tiny Command handles Cal.com's rate limits automatically so you don't have to throttle manually.

More actions