Reschedule 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
New Start Time start	datetime	Required	New Start Time. (date/time)
Reason reschedulingReason	string	Optional	Reason

Sample request

{
  "bookingUid": "{{trigger.bookingUid}}",
  "start": "{{trigger.start}}",
  "reschedulingReason": "{{trigger.reschedulingReason}}"
}

Returns

{
  "data": {
    "uid": "abc-123",
    "status": "accepted",
    "startTime": "2026-04-16T14:00:00Z"
  },
  "status": "success"
}

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

FAQ

Questions about Reschedule Booking.

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

Moves a booking to a new time slot. Cal.com sends the standard reschedule email. Useful for "host emergency → auto-move tomorrow's bookings to next week" bulk operations.

What inputs does Reschedule Booking require?

Required: Booking UID, New Start Time. 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 Reschedule Booking support batch operations?

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