> For the complete documentation index, see [llms.txt](https://help.sipgate.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sipgate.de/ai-agents/en/connections-and-integrations/kalender.md).

# Calendar

Connect a Cal.com calendar with your agent. This allows your agent to check available appointments and book directly for your callers.

{% hint style="info" %}
**Note:** Currently, the integration supports retrieving available appointments as well as direct booking. More functions will be added step by step.
{% endhint %}

### Requirements

* a Cal.com account, free or paid
* at least one configured event type in Cal.com
* an API key from your Cal.com account

### Create Cal.com API key

{% stepper %}
{% step %}
Log in at [app.cal.com](https://app.cal.com/) .
{% endstep %}

{% step %}
Go to Settings **→** Security **→** API Keys.
{% endstep %}

{% step %}
Create a new API key.
{% endstep %}

{% step %}
Store the key securely.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**Note:** API keys are valid for 30 days by default. In the Cal.com settings, adjust the validity or create an unlimited key.
{% endhint %}

### Set up calendar integration

{% stepper %}
{% step %}
Open your agent and navigate to the **Calendar.**
{% endstep %}

{% step %}
Click **Add** to open the setup dialog.
{% endstep %}

{% step %}
Enter your API key and click **Next.**
{% endstep %}

{% step %}
Choose the appropriate mode, API region, and, if needed, additional IDs.
{% endstep %}

{% step %}
Click Save.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
**Important:** Make sure that no playbook for appointment requests is active, neither your own nor one from the library. Otherwise your agent may handle the request via the playbook and will not start an appointment booking.
{% endhint %}

### Configuration fields

| Field               | Required                                        | Description                                                  |
| ------------------- | ----------------------------------------------- | ------------------------------------------------------------ |
| **API token**       | Yes                                             | Your Cal.com API key (starts with `cal_` or `cal_live_`)     |
| **Mode**            | Yes                                             | Determines which calendar is accessed (see below)            |
| **API region**      | Yes                                             | US or EU — depending on where your Cal.com account is hosted |
| **Organization ID** | Only in mode "Organization"                     | The ID of your Cal.com organization                          |
| **Team ID**         | Only in mode "Team", optional in "Organization" | The ID of your Cal.com team                                  |

### Choose mode

You can find the team ID and organization ID in the URL when you open the respective team or organization in Cal.com.

| Mode             | Description                                                                  |
| ---------------- | ---------------------------------------------------------------------------- |
| **Personal**     | Access to your personal Cal.com calendar                                     |
| **Team**         | Access to a team calendar — requires a team ID                               |
| **Organization** | Organization-level access — requires an organization ID, team ID is optional |

## API region

| Region          | URL           | Usage                                                  |
| --------------- | ------------- | ------------------------------------------------------ |
| **US (Global)** | `api.cal.com` | Default for Cal.com accounts                           |
| **EU**          | `api.cal.eu`  | For Cal.com accounts hosted in the EU (GDPR-compliant) |

{% hint style="info" %}
If you're unsure which region is the right one: look at your browser's address bar while logged in to Cal.com. If the address is `app.cal.eu`, select the EU region. If it is `app.cal.com`, select US (Global).
{% endhint %}

## Edit configuration

After setup, you can adjust the **Mode**, the **API region** and the **API token** separately via the edit buttons. Changes take effect immediately.

### Good to know

* Do not include any entries about appointments or appointment bookings in the customer questions. Otherwise your agent may treat the request as a knowledge question instead of using the calendar integration.
* Your API key is stored encrypted.
* Your agent checks availability in your Cal.com calendar on every call.
* If you delete the integration, your agent can no longer check or book appointments.

{% hint style="info" %}
In the **Enterprise plan** you can also implement more complex appointment and process logic. [Learn more.](https://help.sipgate.de/ai-agents/en/plans-and-costs/enterprise-tarif-leistungen-und-einfuhrungsprozess.md)
{% endhint %}


---

# 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://help.sipgate.de/ai-agents/en/connections-and-integrations/kalender.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.
