Reschedule booking

calcom.rescheduleBooking reschedules an existing booking or one seat in a seated booking.

automations/reschedule-booking.automation.ts

import { automation, markSignificant } from "automate.ax"
import { calcom } from "automate.ax/calcom"

export default automation("Reschedule booking", () => {
  markSignificant(
    calcom.rescheduleBooking({
      bookingUid: "booking-uid",
      start: "2026-09-11T17:00:00.000Z",
    }),
  )
})

Input

Pass these fields:

Field	Type	Required	Description
`bookingUid`	`string`	Yes	—
`start`	`string (date-time)`	Yes	Start time in ISO 8601 format for the new booking
`rescheduledBy`	`string`	No	Email of the person who is rescheduling the booking - only needed when rescheduling a booking that requires a confirmation. If event type owner email is provided then rescheduled booking will be automatically confirmed. If attendee email or no email is passed then the event type owner will have to confirm the rescheduled booking.
`reschedulingReason`	`string`	No	Reason for rescheduling the booking
`emailVerificationCode`	`string`	No	Email verification code required when event type has email verification enabled.
`rescheduleWithSameHost`	`boolean`	No	Only for round robin event types that let the person rescheduling choose the host. True keeps the original host, false lets round robin pick from the whole team. Ignored for every other event type.
`allowConflicts`	`boolean`	No	When true and the authenticated user is a host of the event type, availability conflict checks are bypassed. If the user is not a host or is unauthenticated, this parameter is silently ignored.
`allowBookingOutOfBounds`	`boolean`	No	When true and the authenticated user is a host of the event type, booking time out-of-bounds checks are bypassed allowing bookings outside the normally permitted scheduling window. If the user is not a host or is unauthenticated, this parameter is silently ignored. Only supported on the 2026-02-25 API version.
`skipBookingLimits`	`boolean`	No	When true and the authenticated user is a host of the event type, booking limit checks (event type, team, and per-host limits such as bookings per day/week/month/year, as well as duration limits) are bypassed, allowing the booking to be created even when a host has reached their limit. If the user is not a host or is unauthenticated, this parameter is silently ignored. Only supported on the 2026-02-25 API version.

For a seated booking, start and seatUid are required. Regular bookings require start and can use rescheduleWithSameHost and reschedulingReason. Both variants accept the bounds, conflict, verification, actor, and limit-bypass fields listed above.

Output

The action removes the outer Cal.com status envelope. Its result is one of these data variants:

Variant	Result
Regular booking	One booking object.
Recurring booking	One recurring booking object.
Seated booking	One seated booking object.
Recurring seated booking	One recurring seated booking object.

Cal.com enforces account role, plan, and availability requirements. Provider rejections surface as structured action failures with the HTTP status and any Retry-After delay.

Built-in triggers

Built-in actions

Runtime utilities

Integrations

Input

Output

​Input

​Output

Input

Output