Cancel 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. Example: abc-123-def-456
Reason cancellationReason	string	Optional	Reason

Sample request

{
  "bookingUid": "e.g. abc-123-def-456",
  "cancellationReason": "{{trigger.cancellationReason}}"
}

Returns

{
  "data": {
    "uid": "abc-123",
    "status": "cancelled"
  },
  "status": "success"
}

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

FAQ

Questions about Cancel Booking.

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

Programmatically cancels a booking. Cal.com sends the configured cancellation email. Useful for "host out sick → bulk-cancel today's bookings with the right reason" workflows.

What inputs does Cancel 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 Cancel Booking support batch operations?

Yes. Run Cancel 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