Get Booking: 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
Booking UID bookingUid	string	Required	Booking UID

Sample request

{
  "bookingUid": "{{trigger.bookingUid}}"
}

Returns

{
  "data": {
    "uid": "abc-123",
    "title": "30 Min Meeting",
    "status": "accepted",
    "startTime": "2026-04-15T14:00:00Z"
  },
  "status": "success"
}

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

FAQ

Questions about Get Booking.

What does the Get Booking action do in Cal.com?

Returns a booking by ID with attendee details, custom-question answers, and current status. The standard lookup for follow-up workflows that received a booking ID via webhook.

What inputs does Get Booking require?

Required: Booking UID. Every input accepts a static value or a variable from any upstream node in your workflow.

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 Get Booking support batch operations?

Yes. Run Get Booking 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