> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to Cal.com

The Cal.com connector lets your AI agent act in each user's Cal.com account. Each user connects their own Cal.com access token once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 29 tools.

**Authentication:** Bearer Token
**Categories:** Calendar, Productivity
**Tools:** 29: 12 read, 14 write, 3 destructive
**Users sign in with:** Access token
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=CALCOM)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the Cal.com connection

   In **AgentKit > Connections**, create a Cal.com connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

4. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'calcom'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize Cal.com:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'calcom_bookings_list',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "calcom"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize Cal.com:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="calcom_bookings_list",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user opens the link once and enters their Cal.com credentials there. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'calcom_booking_get',
  toolInput: {
    booking_uid: '<booking_uid>',
  },
  connector: 'calcom',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="calcom_booking_get",
    tool_input={
        "booking_uid": "<booking_uid>",
    },
    connection_name="calcom",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `calcom_booking_get`

Get Booking · Read-only

Get one booking by its uid. For a recurring booking's uid, returns every occurrence.
Returns the booking's title, status, start and end times, event type, hosts, attendees, guests, location, meeting URL, and cancellation or reschedule details.
Use this when you have the uid; use calcom_bookings_list to find it.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `booking_uid` (`string`, required): Unique identifier (uid) of the booking to get. Comes from the uid field returned by calcom_bookings_list or calcom_booking_create. Example: 3sMMoZNJwBMxXT3bm4Mqqm

Example input: `{"booking_uid":"<booking_uid>"}`

### `calcom_bookings_list`

List Bookings · Read-only

List the authenticated user's bookings, filtered by status, attendee, event type, team, or date range.
Returns a page of bookings with uid, title, status, start and end times, event type, hosts, attendees, location, and meeting URL, plus pagination.nextCursor for the next page.
Use this to find bookings or a booking uid; use calcom_booking_get when you already have the uid.
status takes one value; to cover several statuses, call once per status.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `after_created_at` (`string`, optional): Only return bookings created after this date-time (ISO 8601). Example: 2025-01-01T00:00:00Z
- `after_start` (`string`, optional): Only return bookings that start after this date-time (ISO 8601). Example: 2025-01-01T00:00:00Z
- `attendee_email` (`string`, optional): Only return bookings with an attendee who has this email address. Example: john@example.com
- `attendee_name` (`string`, optional): Only return bookings with an attendee who has this name. Example: John Smith
- `before_created_at` (`string`, optional): Only return bookings created before this date-time (ISO 8601). Example: 2025-01-31T23:59:59Z
- `before_end` (`string`, optional): Only return bookings that end before this date-time (ISO 8601). Example: 2025-01-31T23:59:59Z
- `cursor` (`string`, optional): Cursor for the next page: pass the pagination.nextCursor value from the previous response. Leave empty for the first page. Example: eyJpZCI6IjEyMyJ9
- `event_type_ids` (`string`, optional): Comma-separated event type IDs; only bookings of these event types are returned. Get IDs from calcom_event_types_list. Example: 1234567,1234568
- `limit` (`integer`, optional): Maximum number of bookings to return per page, 1 to 100. Cal.com returns 50 when not set. Example: 25
- `sort_created` (`string`, optional): Sort by when the booking was made: asc for oldest first, desc for newest first. Example: desc. One of: `asc`, `desc`.
- `sort_start` (`string`, optional): Sort by booking start time: asc for earliest first, desc for latest first. Example: asc. One of: `asc`, `desc`.
- `status` (`string`, optional): Only return bookings with this one status: upcoming, recurring, past, cancelled, or unconfirmed. Leave empty for all statuses. To cover several statuses, call once per status. Example: upcoming. One of: `upcoming`, `recurring`, `past`, `cancelled`, `unconfirmed`.
- `team_ids` (`string`, optional): Comma-separated IDs of teams the user belongs to; only bookings of these teams' event types are returned. Example: 101,102

Example input: `{}`

### `calcom_calendars_list`

List Connected Calendars · Read-only

List the calendars connected to the authenticated user's Cal.com account, such as Google, Outlook, or Apple calendars.
Returns each connected calendar app with its credential id and calendars, which ones are checked for conflicts, and the destination calendar for new bookings.
Use this to see which calendars Cal.com reads busy times from and writes bookings to.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `calcom_event_type_get`

Get Event Type · Read-only

Get one event type by its numeric id.
Returns the event type's title, slug, length, description, locations, booking fields, schedule id, buffers, and limits.
Use this when you have the id; use calcom_event_types_list to find it.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `event_type_id` (`integer`, required): Numeric ID of the event type to get. Comes from the id field returned by calcom_event_types_list. Example: 1234567

Example input: `{"event_type_id":1234567}`

### `calcom_event_types_list`

List Event Types · Read-only

List event types (bookable meeting templates), by default the ones owned by the authenticated user, or a given user's public ones by username.
Returns each event type's id, title, slug, length in minutes, locations, booking fields, and scheduling settings.
Use this to find an event type id to book, check slots for, or update; use calcom_event_type_get when you already have the id.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `event_slug` (`string`, optional): Slug of a single event type to return, for example the last part of cal.com/janedoe/30min. Requires username as well, because different users can have event types with the same slug. Example: 30min
- `org_id` (`integer`, optional): Numeric ID of the user's organization, when the user belongs to a Cal.com organization. Use this or org_slug, not both. Example: 42
- `org_slug` (`string`, optional): Slug of the user's organization, when the user belongs to a Cal.com organization. Use this or org_id, not both. Example: acme
- `sort_created_at` (`string`, optional): Order results by creation date: asc for oldest first, desc for newest first. Leave empty for no explicit order. Example: desc. One of: `asc`, `desc`.
- `username` (`string`, optional): Username of the Cal.com user whose event types to return. Leave empty to list the authenticated user's own event types. Example: janedoe
- `usernames` (`string`, optional): Comma-separated usernames to get the dynamic group event type for several users at once. Example: alice,bob

Example input: `{}`

### `calcom_me_get`

Get My Profile · Read-only

Get the profile of the Cal.com user who owns the API key.
Returns the user's id, username, email, name, time zone, week start, time format, default schedule id, and organization id.
Use this to find the account's username, time zone, or default schedule before listing event types, checking slots, or booking; use calcom_me_update to change these settings.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `calcom_schedule_default_get`

Get Default Schedule · Read-only

Get the authenticated user's default availability schedule, used by event types that have no schedule of their own.
Returns the schedule's id, name, time zone, weekly availability, and date overrides.
Use this to see the user's normal working hours; use calcom_schedules_list to see all schedules.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `calcom_schedule_get`

Get Schedule · Read-only

Get one availability schedule by its id.
Returns the schedule's name, time zone, whether it is the default, weekly availability, and date overrides.
Use this when you have the id; use calcom_schedules_list to find it.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `schedule_id` (`integer`, required): Numeric ID of the availability schedule to get. Comes from the id field returned by calcom_schedules_list. Example: 123456

Example input: `{"schedule_id":123456}`

### `calcom_schedules_list`

List Schedules · Read-only

List the authenticated user's availability schedules.
Returns each schedule's id, name, time zone, whether it is the default, weekly availability, and date overrides.
Use this to find a schedule id; use calcom_schedule_default_get for the default schedule only, or calcom_schedule_get for one schedule by id.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `calcom_slots_list`

Get Available Slots · Read-only

Get the free start times for an event type between two dates, or when two or more users are all free.
Returns available slots grouped by date, as start times or start and end ranges.
Use this before calcom_booking_create or calcom_booking_reschedule to pick a time.
Identify the event type by event_type_id, or by event_type_slug plus username (user event) or team_slug (team event), or pass usernames for a group of users.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `end` (`string`, required): End of the range to check, in UTC (ISO 8601). A date alone means the end of that day. Example: 2025-03-14
- `start` (`string`, required): Start of the range to check, in UTC (ISO 8601). A date alone means the start of that day. Example: 2025-03-10
- `booking_uid_to_reschedule` (`string`, optional): Uid of a booking being rescheduled, so that its current time is also shown as available. Example: 3sMMoZNJwBMxXT3bm4Mqqm
- `duration` (`integer`, optional): Slot length in minutes, for event types with several lengths or for group meetings (default 30). Example: 60
- `event_type_id` (`integer`, optional): Numeric ID of the event type to check, from calcom_event_types_list. For a managed team event, use a child event type's ID. Example: 1234567
- `event_type_slug` (`string`, optional): Slug of the event type to check, used instead of event_type_id together with username or team_slug. Example: 30min
- `format` (`string`, optional): Format of each slot: time returns only start times, range returns start and end times. Example: range. One of: `time`, `range`.
- `organization_slug` (`string`, optional): Slug of the organization the user or team belongs to, when they are in an organization. Example: acme
- `team_slug` (`string`, optional): Slug of the team that owns the event type, used with event_type_slug for team events. Example: sales
- `time_zone` (`string`, optional): IANA time zone for the returned slot times. Defaults to UTC. Example: America/New_York
- `username` (`string`, optional): Username of the event type owner, used with event_type_slug. Example: janedoe
- `usernames` (`string`, optional): Comma-separated usernames (at least 2) to find times when all of them are free, for a dynamic group meeting. Example: alice,bob

Example input: `{"end":"<end>","start":"<start>"}`

### `calcom_webhook_get`

Get Webhook · Read-only

Get one of the authenticated user's webhooks by its id.
Returns the webhook's subscriber URL, triggers, active flag, and payload template.
Use this when you have the id; use calcom_webhooks_list to find it.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `webhook_id` (`string`, required): ID of the webhook to get. Comes from the id field returned by calcom_webhooks_list or calcom_webhook_create. Example: 2fa2bb45-5d4c-4cd2-a5a5-4d4cbd0c6d3b

Example input: `{"webhook_id":"<webhook_id>"}`

### `calcom_webhooks_list`

List Webhooks · Read-only

List the authenticated user's webhooks.
Returns each webhook's id, subscriber URL, triggers, active flag, and payload template.
Use this to find a webhook id; use calcom_webhook_get when you already have it.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `skip` (`integer`, optional): Number of webhooks to skip, for paging through results together with take. Example: 50
- `take` (`integer`, optional): Maximum number of webhooks to return, 1 to 250. Cal.com returns 250 when not set. Example: 50

Example input: `{}`

### `calcom_booking_cancel`

Cancel Booking · Write

Cancel a booking and notify its attendees. For a recurring booking's uid, cancels every occurrence; for a seated booking, a seat_uid cancels only that seat.
Returns the cancelled booking with its status and cancellation reason.
Use this to call off a meeting; use calcom_booking_reschedule to move it, or calcom_booking_decline to reject a booking that awaits confirmation.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `booking_uid` (`string`, required): Unique identifier (uid) of the booking to cancel. Comes from the uid field returned by calcom_bookings_list or calcom_booking_create. Example: 3sMMoZNJwBMxXT3bm4Mqqm
- `cancel_subsequent_bookings` (`boolean`, optional): Only for one occurrence of a recurring, non-seated booking: true also cancels every later occurrence. Example: true
- `cancellation_reason` (`string`, optional): Reason for cancelling, shown in the cancellation emails. Example: Client asked to postpone
- `seat_uid` (`string`, optional): For a seated event, the uid of the one seat to cancel; leave empty to cancel the whole booking. Example: 5b7f6c1e-3a2d-4d1e-9a7b-1c2d3e4f5a6b

Example input: `{"booking_uid":"<booking_uid>"}`

### `calcom_booking_confirm`

Confirm Booking · Write

Confirm a booking that is waiting for the host's approval, on an event type that requires confirmation.
Returns the booking with its status set to accepted.
Use calcom_bookings_list with status unconfirmed to find bookings waiting for approval; use calcom_booking_decline to reject one instead.
The API key must belong to the booking's host.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `booking_uid` (`string`, required): Unique identifier (uid) of the booking to confirm. Comes from the uid field returned by calcom_bookings_list or calcom_booking_create. Example: 3sMMoZNJwBMxXT3bm4Mqqm

Example input: `{"booking_uid":"<booking_uid>"}`

### `calcom_booking_create`

Create Booking · Write

Book a meeting on a Cal.com event type for an attendee at a given start time. A recurring event type creates a recurring booking.
Returns the created booking with its uid, status, start and end times, hosts, attendees, location, and meeting URL.
Use calcom_slots_list first to pick a free start time; use calcom_booking_reschedule to move an existing booking.
Identify the event type by event_type_id, or by event_type_slug plus username (user event) or team_slug (team event).

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `attendee_name` (`string`, required): Full name of the person booking the meeting. Example: John Smith
- `attendee_time_zone` (`string`, required): IANA time zone of the attendee, used in confirmation emails. Example: Europe/London
- `start` (`string`, required): Start time of the meeting in UTC, ISO 8601. Take it from a slot returned by calcom_slots_list. Example: 2025-03-10T14:00:00Z
- `attendee_email` (`string`, optional): Email address of the attendee. Cal.com sends the confirmation and calendar invite to it. Example: john@example.com
- `attendee_language` (`string`, optional): Language code for the attendee's confirmation emails. Example: en. One of: `ar`, `ca`, `de`, `es`, `eu`, `he`, `id`, `ja`, `lv`, `pl`, `ro`, `sr`, `th`, `vi`, `az`, `cs`, `el`, `es-419`, `fi`, `hr`, `it`, `km`, `nl`, `pt`, `ru`, `sv`, `tr`, `zh-CN`, `bg`, `da`, `en`, `et`, `fr`, `hu`, `iw`, `ko`, `no`, `pt-BR`, `sk`, `ta`, `uk`, `zh-TW`, `bn`.
- `attendee_phone_number` (`string`, optional): Phone number of the attendee in international format. Needed when the event type asks for a phone number or uses SMS reminders. Example: +14155550123
- `booking_fields_responses` (`object`, optional): Answers to the event type's custom booking questions, keyed by each booking field's slug. Example: {"company": "Acme", "notes": "Discuss pricing"}
- `event_type_id` (`integer`, optional): Numeric ID of the event type to book, from calcom_event_types_list. Required unless event_type_slug with username or team_slug is given. Example: 1234567
- `event_type_slug` (`string`, optional): Slug of the event type to book, used instead of event_type_id together with username (user event) or team_slug (team event). Example: 30min
- `guests` (`array`, optional): Extra guest email addresses to invite to the meeting. Example: ["anna@example.com"]
- `length_in_minutes` (`integer`, optional): Meeting length in minutes, only for event types that offer several lengths. Defaults to the event type's length. Example: 60
- `location` (`object`, optional): Where the meeting happens, chosen from the event type's locations. An object with a type and the value it needs: {"type": "integration", "integration": "cal-video"} for a video app, {"type": "attendeePhone", "phone": "+14155550123"} for the attendee's phone, {"type": "attendeeAddress", "address": "..."} or {"type": "attendeeDefined", "location": "..."}; address, link, phone and organizersDefaultApp need only the type. Leave empty to use the event type's default. Example: {"type": "integration", "integration": "cal-video"}
- `metadata` (`object`, optional): Your own key-value data to store on the booking: up to 50 keys of up to 40 characters, string values up to 500 characters. Example: {"crm_id": "0061234"}
- `organization_slug` (`string`, optional): Slug of the organization the user or team belongs to, used with event_type_slug when they are in an organization. Example: acme
- `team_slug` (`string`, optional): Slug of the team that owns the event type, used with event_type_slug for team events. Example: sales
- `username` (`string`, optional): Username of the event type owner, used with event_type_slug. Example: janedoe

Example input: `{"attendee_name":"<attendee_name>","attendee_time_zone":"<attendee_time_zone>","start":"<start>"}`

### `calcom_booking_decline`

Decline Booking · Write

Decline a booking that is waiting for the host's approval, on an event type that requires confirmation. The attendee is notified.
Returns the booking with its status set to rejected.
Use this to reject an unconfirmed booking; use calcom_booking_confirm to accept it, or calcom_booking_cancel for a booking that is already confirmed.
The API key must belong to the booking's host.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `booking_uid` (`string`, required): Unique identifier (uid) of the booking to decline. Comes from the uid field returned by calcom_bookings_list or calcom_booking_create. Example: 3sMMoZNJwBMxXT3bm4Mqqm
- `reason` (`string`, optional): Reason for declining, sent to the attendee. Example: Not available that day

Example input: `{"booking_uid":"<booking_uid>"}`

### `calcom_booking_guests_add`

Add Booking Guests · Write

Add guests to an existing booking and send them the calendar invite. Up to 10 guests per call and 30 per booking; limited to 5 calls per minute.
Returns the updated booking with its attendees and guests.
Use this to invite more people to a booked meeting; use calcom_booking_create to book a new one.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `booking_uid` (`string`, required): Unique identifier (uid) of the booking to add guests to. Comes from the uid field returned by calcom_bookings_list or calcom_booking_create. Example: 3sMMoZNJwBMxXT3bm4Mqqm
- `guests` (`array`, required): Guests to add, up to 10. Each needs an email and can also have a name, an IANA time zone, a phone number in international format, and a language code for their emails. Example: [{"email": "anna@example.com", "name": "Anna Lee", "timeZone": "Europe/Paris"}]

Example input: `{"booking_uid":"<booking_uid>","guests":[{"email":"anna@example.com","name":"Anna Lee","timeZone":"Europe/Paris"}]}`

### `calcom_booking_mark_absent`

Mark Booking No-Show · Write

Record who did not show up to a past booking: the host, one or more attendees, or both.
Returns the booking with its updated no-show flags.
Use this after a meeting to track no-shows; set absent to false to undo a mark. The API key must belong to the booking's host.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `booking_uid` (`string`, required): Unique identifier (uid) of the booking to mark. Comes from the uid field returned by calcom_bookings_list or calcom_booking_create. Example: 3sMMoZNJwBMxXT3bm4Mqqm
- `attendees` (`array`, optional): Attendees to mark, each with the attendee's email and absent set to true (did not attend) or false (attended). Example: [{"email": "john@example.com", "absent": true}]
- `host` (`boolean`, optional): Set to true if the host did not attend, false to clear the mark. Example: false

Example input: `{"booking_uid":"<booking_uid>"}`

### `calcom_booking_reschedule`

Reschedule Booking · Write

Move an existing booking to a new start time. Cal.com cancels the original and creates a new booking with a new uid.
Returns the new booking with its uid, status, and start and end times.
Use calcom_slots_list with booking_uid_to_reschedule first to find a free time; use calcom_booking_cancel to cancel without a new time.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `booking_uid` (`string`, required): Unique identifier (uid) of the booking to reschedule. Comes from the uid field returned by calcom_bookings_list or calcom_booking_create. Example: 3sMMoZNJwBMxXT3bm4Mqqm
- `start` (`string`, required): New start time of the meeting in UTC, ISO 8601. Example: 2025-03-12T15:00:00Z
- `length_in_minutes` (`integer`, optional): New meeting length in minutes, only for event types that offer several lengths and only when not moving a single seat. Example: 60
- `rescheduled_by` (`string`, optional): Email of the person rescheduling. Only matters for event types that need confirmation: the event type owner's email confirms the new booking automatically, otherwise the owner must confirm it. Example: jane@example.com
- `rescheduling_reason` (`string`, optional): Reason for the change, shown in the reschedule emails. Example: Conflict with another meeting
- `seat_uid` (`string`, optional): For a seated event, the uid of the one seat to move; leave empty to move the whole booking. Example: 5b7f6c1e-3a2d-4d1e-9a7b-1c2d3e4f5a6b

Example input: `{"booking_uid":"<booking_uid>","start":"<start>"}`

### `calcom_event_type_create`

Create Event Type · Write

Create a new event type (a bookable meeting template) for the authenticated user.
Returns the created event type with its id, slug, length, and settings.
Use this to add a new kind of meeting; use calcom_event_type_update to change an existing one.
The slug must be unique among the user's event types.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `length_in_minutes` (`integer`, required): Default length of the meeting in minutes. Example: 30
- `slug` (`string`, required): URL slug of the event type, the last part of its booking link (cal.com/<username>/<slug>). Lowercase letters, numbers and hyphens. Example: 30min
- `title` (`string`, required): Name of the event type shown on the booking page. Example: 30 Minute Meeting
- `after_event_buffer` (`integer`, optional): Minutes blocked on the calendar after each meeting. Example: 10
- `before_event_buffer` (`integer`, optional): Minutes blocked on the calendar before each meeting. Example: 10
- `description` (`string`, optional): Description shown to bookers on the booking page. Example: A quick intro call to discuss your needs.
- `hidden` (`boolean`, optional): Set to true to hide the event type from the user's public booking page; it can still be booked by direct link. Example: false
- `locations` (`array`, optional): Where the meeting takes place, as a list of location objects. Each object has a type plus the value that type needs: integration with an integration name (cal-video, google-meet, zoom or office365-video, the app must already be installed), address with an address, link with a link, or phone with a phone number; address, link and phone also take public (true to show it before booking). attendeeAddress, attendeePhone and attendeeDefined ask the booker for it. If not set, Cal Video is used. Example: [{"type": "integration", "integration": "google-meet"}]
- `minimum_booking_notice` (`integer`, optional): Minimum number of minutes between now and the meeting start for a booking to be allowed. Example: 120
- `schedule_id` (`integer`, optional): ID of an availability schedule to use for this event type instead of the user's default schedule. Get it from calcom_schedules_list. Example: 123456
- `slot_interval` (`integer`, optional): Spacing in minutes between the start times offered to bookers. Defaults to the event length; for example 15 with a 30-minute event offers 9:00, 9:15, 9:30. Example: 15
- `success_redirect_url` (`string`, optional): URL the booker is sent to after a successful booking. Example: https://example.com/thanks

Example input: `{"length_in_minutes":30,"slug":"<slug>","title":"<title>"}`

### `calcom_event_type_update`

Update Event Type · Write

Update an existing event type owned by the authenticated user, such as its title, length, locations, or schedule.
Returns the updated event type.
Use this to change an event type; use calcom_event_type_create to add a new one. Only the fields you set are changed; locations replaces the whole list.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `event_type_id` (`integer`, required): Numeric ID of the event type to update. Comes from the id field returned by calcom_event_types_list. Example: 1234567
- `after_event_buffer` (`integer`, optional): Minutes blocked on the calendar after each meeting. Example: 10
- `before_event_buffer` (`integer`, optional): Minutes blocked on the calendar before each meeting. Example: 10
- `description` (`string`, optional): Description shown to bookers on the booking page. Example: A quick intro call to discuss your needs.
- `hidden` (`boolean`, optional): Set to true to hide the event type from the user's public booking page; it can still be booked by direct link. Example: false
- `length_in_minutes` (`integer`, optional): Default length of the meeting in minutes. Example: 30
- `locations` (`array`, optional): Where the meeting takes place, as a list of location objects. Each object has a type plus the value that type needs: integration with an integration name (cal-video, google-meet, zoom or office365-video, the app must already be installed), address with an address, link with a link, or phone with a phone number; address, link and phone also take public (true to show it before booking). attendeeAddress, attendeePhone and attendeeDefined ask the booker for it. If not set, Cal Video is used. Example: [{"type": "integration", "integration": "google-meet"}]
- `minimum_booking_notice` (`integer`, optional): Minimum number of minutes between now and the meeting start for a booking to be allowed. Example: 120
- `schedule_id` (`integer`, optional): ID of an availability schedule to use for this event type instead of the user's default schedule. Get it from calcom_schedules_list. Example: 123456
- `slot_interval` (`integer`, optional): Spacing in minutes between the start times offered to bookers. Defaults to the event length; for example 15 with a 30-minute event offers 9:00, 9:15, 9:30. Example: 15
- `slug` (`string`, optional): URL slug of the event type, the last part of its booking link (cal.com/<username>/<slug>). Lowercase letters, numbers and hyphens. Example: 30min
- `success_redirect_url` (`string`, optional): URL the booker is sent to after a successful booking. Example: https://example.com/thanks
- `title` (`string`, optional): Name of the event type shown on the booking page. Example: 30 Minute Meeting

Example input: `{"event_type_id":1234567}`

### `calcom_me_update`

Update My Profile · Write

Update profile settings of the Cal.com user who owns the API key, such as name, time zone, or default schedule.
Returns the updated profile.
Use this to change account settings; use calcom_me_get to read them first. Only the fields you set are changed.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `avatar_url` (`string`, optional): Public URL of an image to use as the user's avatar. Example: https://example.com/avatar.png
- `bio` (`string`, optional): Short bio shown on the user's public booking page. Example: Product designer based in Lisbon.
- `default_schedule_id` (`integer`, optional): ID of the availability schedule to use by default for event types that have no schedule of their own. Get it from calcom_schedules_list. Example: 123456
- `email` (`string`, optional): New primary email address of the user. Cal.com may require the new email to be verified. Example: jane@example.com
- `locale` (`string`, optional): Language code for the user's Cal.com interface and emails. Example: en. One of: `ar`, `ca`, `de`, `es`, `eu`, `he`, `id`, `ja`, `lv`, `pl`, `ro`, `sr`, `th`, `vi`, `az`, `cs`, `el`, `es-419`, `fi`, `hr`, `it`, `km`, `nl`, `pt`, `ru`, `sv`, `tr`, `zh-CN`, `bg`, `da`, `en`, `et`, `fr`, `hu`, `iw`, `ko`, `no`, `pt-BR`, `sk`, `ta`, `uk`, `zh-TW`, `bn`.
- `name` (`string`, optional): New display name of the user. Example: Jane Doe
- `time_format` (`integer`, optional): Clock format used in Cal.com: 12 for a 12-hour clock (AM/PM) or 24 for a 24-hour clock. Example: 24. One of: `12`, `24`.
- `time_zone` (`string`, optional): IANA time zone used to show the user's availability and bookings. Example: America/New_York
- `week_start` (`string`, optional): Day the user's calendar week starts on. One of Monday to Sunday. Example: Monday. One of: `Monday`, `Tuesday`, `Wednesday`, `Thursday`, `Friday`, `Saturday`, `Sunday`.

Example input: `{}`

### `calcom_schedule_create`

Create Schedule · Write

Create an availability schedule (named weekly working hours with optional date overrides) for the authenticated user.
Returns the created schedule with its id, name, time zone, availability, and overrides.
Use this to add a new set of hours, then attach it to an event type with calcom_event_type_update; use calcom_schedule_update to change an existing schedule.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `is_default` (`boolean`, required): Set to true to make this the user's default schedule, used by event types without a schedule of their own. Example: false
- `name` (`string`, required): Name of the schedule. Example: Working Hours
- `time_zone` (`string`, required): IANA time zone the availability hours are in. Example: Europe/Berlin
- `availability` (`array`, optional): Weekly hours when the user can be booked, as a list of blocks. Each block has the days it applies to (Monday to Sunday) and a start and end time in HH:MM, 24-hour. When creating a schedule without it, Cal.com uses Monday to Friday 09:00 to 17:00. Example: [{"days": ["Monday", "Tuesday"], "startTime": "09:00", "endTime": "17:00"}]
- `overrides` (`array`, optional): Different hours for specific dates, as a list of blocks. Each block has a date (YYYY-MM-DD) and a start and end time in HH:MM, 24-hour. Example: [{"date": "2025-12-24", "startTime": "09:00", "endTime": "12:00"}]

Example input: `{"is_default":true,"name":"<name>","time_zone":"<time_zone>"}`

### `calcom_schedule_update`

Update Schedule · Write

Update an availability schedule's name, time zone, weekly hours, or date overrides, or make it the default.
Returns the updated schedule.
Use this to change working hours; use calcom_schedule_create to add a new schedule. Only the fields you set are changed; availability and overrides replace the whole list.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `schedule_id` (`integer`, required): Numeric ID of the availability schedule to update. Comes from the id field returned by calcom_schedules_list. Example: 123456
- `availability` (`array`, optional): Weekly hours when the user can be booked, as a list of blocks. Each block has the days it applies to (Monday to Sunday) and a start and end time in HH:MM, 24-hour. When creating a schedule without it, Cal.com uses Monday to Friday 09:00 to 17:00. Example: [{"days": ["Monday", "Tuesday"], "startTime": "09:00", "endTime": "17:00"}]
- `is_default` (`boolean`, optional): Set to true to make this the user's default schedule, used by event types without a schedule of their own. Example: false
- `name` (`string`, optional): Name of the schedule. Example: Working Hours
- `overrides` (`array`, optional): Different hours for specific dates, as a list of blocks. Each block has a date (YYYY-MM-DD) and a start and end time in HH:MM, 24-hour. Example: [{"date": "2025-12-24", "startTime": "09:00", "endTime": "12:00"}]
- `time_zone` (`string`, optional): IANA time zone the availability hours are in. Example: Europe/Berlin

Example input: `{"schedule_id":123456}`

### `calcom_webhook_create`

Create Webhook · Write

Create a webhook that sends the authenticated user's booking and meeting events to a URL.
Returns the created webhook with its id, subscriber URL, triggers, and active flag.
Use this to subscribe a URL to events; use calcom_webhook_update to change an existing webhook.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `subscriber_url` (`string`, required): HTTPS URL that Cal.com sends the webhook POST requests to. Example: https://example.com/webhooks/calcom
- `triggers` (`array`, required): Events that fire the webhook, for example BOOKING_CREATED, BOOKING_RESCHEDULED, BOOKING_CANCELLED, MEETING_ENDED. Example: ["BOOKING_CREATED", "BOOKING_CANCELLED"]
- `active` (`boolean`, optional): Whether the webhook is enabled. Defaults to true. Example: true. Default: `true`.
- `payload_template` (`string`, optional): Custom payload template using Cal.com webhook variables. Leave empty to send the default payload. Example: {"title": "{{title}}", "start": "{{startTime}}"}
- `secret` (`string`, optional): Secret Cal.com uses to sign each payload, so your endpoint can verify it came from Cal.com. Example: whsec_3f9a2b

Example input: `{"subscriber_url":"<subscriber_url>","triggers":["BOOKING_CREATED","BOOKING_CANCELLED"]}`

### `calcom_webhook_update`

Update Webhook · Write

Update a webhook's subscriber URL, triggers, secret, or payload template, or pause and resume it.
Returns the updated webhook.
Use this to change a webhook; use calcom_webhook_create to add one. Only the fields you set are changed; triggers replaces the whole list.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `webhook_id` (`string`, required): ID of the webhook to update. Comes from the id field returned by calcom_webhooks_list or calcom_webhook_create. Example: 2fa2bb45-5d4c-4cd2-a5a5-4d4cbd0c6d3b
- `active` (`boolean`, optional): Set to false to pause the webhook or true to turn it back on. Example: false
- `payload_template` (`string`, optional): Custom payload template using Cal.com webhook variables. Leave empty to send the default payload. Example: {"title": "{{title}}", "start": "{{startTime}}"}
- `secret` (`string`, optional): Secret Cal.com uses to sign each payload, so your endpoint can verify it came from Cal.com. Example: whsec_3f9a2b
- `subscriber_url` (`string`, optional): HTTPS URL that Cal.com sends the webhook POST requests to. Example: https://example.com/webhooks/calcom
- `triggers` (`array`, optional): Events that fire the webhook, for example BOOKING_CREATED, BOOKING_RESCHEDULED, BOOKING_CANCELLED, MEETING_ENDED. Example: ["BOOKING_CREATED", "BOOKING_CANCELLED"]

Example input: `{"webhook_id":"<webhook_id>"}`

### `calcom_event_type_delete`

Delete Event Type · Destructive

Permanently delete an event type owned by the authenticated user.
Returns the deleted event type's id, title, slug, and length.
Use this only to remove an event type for good; to stop it showing on the profile, use calcom_event_type_update with hidden set to true.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `event_type_id` (`integer`, required): Numeric ID of the event type to delete. Comes from the id field returned by calcom_event_types_list. Example: 1234567

Example input: `{"event_type_id":1234567}`

### `calcom_schedule_delete`

Delete Schedule · Destructive

Permanently delete an availability schedule.
Returns a success status.
Use this only to remove a schedule for good; use calcom_schedule_update to change its hours instead.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `schedule_id` (`integer`, required): Numeric ID of the availability schedule to delete. Comes from the id field returned by calcom_schedules_list. Example: 123456

Example input: `{"schedule_id":123456}`

### `calcom_webhook_delete`

Delete Webhook · Destructive

Permanently delete a webhook so Cal.com stops sending events to its URL.
Returns the deleted webhook.
Use this to remove a webhook for good; use calcom_webhook_update with active set to false to pause it instead.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `webhook_id` (`string`, required): ID of the webhook to delete. Comes from the id field returned by calcom_webhooks_list or calcom_webhook_create. Example: 2fa2bb45-5d4c-4cd2-a5a5-4d4cbd0c6d3b

Example input: `{"webhook_id":"<webhook_id>"}`

## Related

Other Calendar connectors ([all 25](/agentkit/connectors/?category=calendar)):

- [Google Calendar](/agentkit/connectors/googlecalendar/): Scalekit connector, OAuth, 30 tools
- [Zoom](/agentkit/connectors/zoom/): Scalekit connector, OAuth, 58 tools
- [Calendly](/agentkit/connectors/calendly/): Scalekit connector, OAuth, 64 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
