Create booking

calcom.createBooking creates a regular, recurring, seated, or instant Cal.com booking.

automations/create-booking.automation.ts

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

export default automation("Create booking", () => {
  markSignificant(
    calcom.createBooking({
      eventTypeId: 23,
      start: "2026-09-10T17:00:00.000Z",
      attendee: {
        name: "Ada Lovelace",
        email: "ada@example.com",
        timeZone: "Europe/London",
      },
    }),
  )
})

Input

Pass these fields:

Field	Type	Required	Description
`start`	`string (date-time)`	Yes	The start time of the booking in ISO 8601 format in UTC timezone.
`attendee`	`JSON value`	Yes	The attendee’s details.
`bookingFieldsResponses`	`object`	No	Booking field responses consisting of an object with booking field slug as keys and user response as values for custom booking fields added by you.
`eventTypeId`	`number`	No	The ID of the event type that is booked. Required unless eventTypeSlug and username are provided as an alternative to identifying the event type.
`eventTypeSlug`	`string`	No	The slug of the event type. Required along with username / teamSlug and optionally organizationSlug if eventTypeId is not provided.
`username`	`string`	No	The username of the event owner. Required along with eventTypeSlug and optionally organizationSlug if eventTypeId is not provided.
`teamSlug`	`string`	No	Team slug for team that owns event type for which slots are fetched. Required along with eventTypeSlug and optionally organizationSlug if the team is part of organization
`organizationSlug`	`string`	No	The organization slug. Optional, only used when booking with eventTypeSlug + username or eventTypeSlug + teamSlug.
`guests`	`string[]`	No	An optional list of guest emails attending the event.
`meetingUrl`	`string (uri)`	No	Deprecated - use ‘location’ instead. Meeting URL just for this booking. Displayed in email and calendar event. If not provided then cal video link will be generated.
`location`	`object`	No	One of the event type locations. If instead of passing one of the location objects as required by schema you are still passing a string please use an object.
`metadata`	`object`	No	You can store any additional data you want here. Metadata must have at most 50 keys, each key up to 40 characters, and string values up to 500 characters.
`lengthInMinutes`	`number`	No	If it is an event type that has multiple possible lengths that attendee can pick from, you can pass the desired booking length here. If not provided then event type default length will be used for the booking. Minimum: 1.
`routing`	`JSON value`	No	Routing information from routing forms that determined the booking assignment. Both responseId and teamMemberIds are required if provided.
`emailVerificationCode`	`string`	No	Email verification code required when event type has email verification enabled.
`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.

Regular bookings use the fields above. Instant bookings add required instant: true. Recurring bookings can add recurrenceCount. In every variant, identify the event by eventTypeId or by eventTypeSlug with the applicable username, team, or organization slug.

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 with `id`, `uid`, `title`, `status`, `start`, `end`, organizer, attendees, guests, location, and meeting URL fields.
Recurring booking	An array of recurring booking objects.
Seated booking	One seated booking object; seated-only fields such as `seatUid` are present only on this branch.
Recurring seated booking	An array of recurring seated booking objects.

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