# Cal.com integrations: bookings and event types

> Create a booking, create an event type and create a schedule in Cal.com, and start a workflow when Cal.com sends “Booking created”.

**Canonical page:** https://tray.ai/connectors/cal-com-integrations/
**Categories:** Operations
**Connects through:** HTTP Connector

## Overview

Cal.com is an open-source scheduling platform where people publish booking pages, manage availability, and route meetings across individuals and teams. Tray.ai connects to Cal.com through the HTTP Connector, so your workflows can call the Cal.com API alongside the rest of your stack.

## Use cases

### Bookings

Read, create, update, delete, and manage bookings in Cal.com from any Tray.ai workflow. The Cal.com API covers calls such as list bookings and create a booking.

- List bookings
- Create a booking
- Reschedule a booking

### Event types

Read, create, update, and delete event types in Cal.com from any Tray.ai workflow. The Cal.com API covers calls such as list event types and create an event type.

- List event types
- Create an event type
- Update an event type

### Schedules

Read, create, update, and delete schedules in Cal.com from any Tray.ai workflow. The Cal.com API covers calls such as list schedules and create a schedule.

- List schedules
- Create a schedule
- Update a schedule

### Slots

Read, delete, and manage slots in Cal.com from any Tray.ai workflow. The Cal.com API covers calls such as get available time slots and reserve a slot.

- Get available time slots
- Reserve a slot
- Delete a reserved slot

### Webhooks

Read, create, update, and delete webhooks in Cal.com from any Tray.ai workflow. The Cal.com API covers calls such as list webhooks and create a webhook.

- List webhooks
- Create a webhook
- Update a webhook

### Cal.com events

Start a Tray.ai workflow the moment something happens in Cal.com. Cal.com sends events such as booking created and booking cancelled to a Tray.ai webhook trigger.

- Booking created
- Booking cancelled
- Booking rescheduled

## Challenges Tray.ai solves

### Keeping Cal.com credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Cal.com credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Cal.com API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Cal.com API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Cal.com?

Yes. Tray.ai connects to Cal.com through the HTTP Connector, which calls the Cal.com API directly. Any call the Cal.com API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Cal.com?

The Cal.com API uses a bearer token and OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Cal.com connector?

Cal.com runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Cal.com connector from the Cal.com API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/