> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/connector-configuration/calcom.md).

# Cal.com

Create a Cal.com API key and connect the Appmixer Cal.com connector.

The Appmixer Cal.com connector uses **API key** authentication with the Cal.com API v2. You do not need to register an OAuth app. Each user creates an API key in their own Cal.com account and enters it when they connect Cal.com in Appmixer.

The connector works with Cal.com Cloud (`https://api.cal.com`). Self-hosted Cal.com instances are not supported, because the API address is fixed in the connector.

***

## 1. Create an API key

1. Log in to [Cal.com](https://app.cal.com).
2. Open **Settings** and go to **Security** → **API Keys**.
3. Create a new API key, give it a name (for example `Appmixer`) and choose when it expires.
4. Copy the key. Keys start with `cal_` (test mode) or `cal_live_` (live mode).

An API key acts as the Cal.com user who created it, with all of that user's privileges. Cal.com API keys have no scopes, so there is nothing else to select. Keep the key secret. If the key expires or is deleted, the Cal.com components fail until the account is reconnected in Appmixer with a new key.

***

## 2. Connect in Appmixer

When you add a Cal.com component to a flow, Appmixer asks you to connect an account. Paste the key into the **API Key** field.

Appmixer sends the key as a Bearer token (`Authorization: Bearer <key>`) to `https://api.cal.com`. To check the key, it calls `GET /v2/me`. The connection is named after the email address of the Cal.com user.

**Make API Call** accepts a path relative to `https://api.cal.com` (for example `/v2/schedules`), or a full URL on that host only. Any other host is rejected so that the key is never sent elsewhere. Add the `cal-api-version` header that the endpoint documents in the [Cal.com API reference](https://cal.com/docs/api-reference/v2/introduction).

***

## 3. Triggers

You do not need to set up webhooks in Cal.com yourself. When a flow with a Cal.com trigger starts, Appmixer uses the API key to register a webhook in Cal.com (`POST /v2/webhooks`) for one trigger event, pointing at the flow's webhook URL. When the flow stops, Appmixer deletes that webhook.

| Trigger                 | Cal.com event         |
| ----------------------- | --------------------- |
| **Booking Created**     | `BOOKING_CREATED`     |
| **Booking Cancelled**   | `BOOKING_CANCELLED`   |
| **Booking Rescheduled** | `BOOKING_RESCHEDULED` |
| **Meeting Ended**       | `MEETING_ENDED`       |

* Your Appmixer API must be reachable from the public internet so that Cal.com can deliver webhook calls.
* Each webhook is registered with a random secret. Appmixer checks the `x-cal-signature-256` header of every call and rejects calls with a missing or invalid signature.
* The webhooks are account-wide: they fire for every booking of the connected Cal.com user, not only for bookings made from Appmixer.

***

## Rate limits

Cal.com allows 120 requests per minute for an API key. Cal.com support can raise the limit on request. The connector queues requests to stay at 120 requests per minute per Appmixer user.

***

## Backoffice configuration

Configuration ID: `appmixer:calcom`. For how to set connector configuration values, see [Connector Configuration](https://docs.appmixer.com/getting-started/services).

You do not need any Backoffice configuration to authenticate, because every user enters their own API key. There are two optional keys:

* `listCacheTTL`: optional. How long, in milliseconds, the list of event types shown in the inspector dropdowns (**Create Booking**, **Update Event Type**, **Delete Event Type**, **Find Available Slots**, **Find Bookings**) is cached. The default is `120000` (2 minutes).
* `outputFilePrefix`: optional. A prefix for the names of CSV files created when **Find Bookings**, **Find Available Slots** or **List Event Types** runs with the **Store to CSV file** output type. Files are named `<prefix>-<component label in the flow>.csv`. The default is `calcom-objects-export`.

```bash
appmixer service-config set appmixer:calcom -u -d '{
  "listCacheTTL": 120000,
  "outputFilePrefix": "calcom-objects-export"
}'
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appmixer.com/connector-configuration/calcom.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
