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

# Calendar

Connect a Cal.com calendar to your AI agent. This allows the agent to check available times and make bookings directly for your callers.

{% hint style="info" %}
Currently, the integration supports retrieving available appointments as well as direct booking. Additional features 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 %}

#### Sign in at [app.cal.com](https://app.cal.com/) in

{% 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="warning" %}
By default, API keys are valid for 30 days. In the Cal.com settings, you can adjust the validity or create a key with unlimited validity.
{% endhint %}

## Set up calendar integration in sipgate

{% stepper %}
{% step %}

### **Open your AI agent**

and navigate to the **Calendar**
{% endstep %}

{% step %}

### **Click "Add"**

to open the setup dialog
{% endstep %}

{% step %}

### **Enter your API key**

and click **Continue**
{% endstep %}

{% step %}

### **Select the appropriate mode, API region, and, if needed, additional IDs**

See table
{% endstep %}

{% step %}

### **Click Save**

{% endstep %}

{% step %}

### Make sure no playbook is configured for appointment requests

A playbook for appointment requests can lead to unexpected behavior when Cal.com integration is active.
{% endstep %}
{% endstepper %}

## 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 "Organization" mode                     | The ID of your Cal.com organization                          |
| **Team ID**         | Only in "Team" mode, optional in "Organization" | The ID of your Cal.com team                                  |

## Choose mode

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

{% hint style="info" %}
You can find the team ID and organization ID in the URL when you open the respective team or organization in Cal.com.
{% endhint %}

## API region

| Region          | URL           | Use                                                    |
| --------------- | ------------- | ------------------------------------------------------ |
| **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 not sure which region is correct, check the URL in your browser when you're logged in to Cal.com. If you use `cal.eu`, choose the EU region.
{% endhint %}

## Edit configuration

After setup, you can adjust the **Mode**, the **API region** and the **API token** separately at any time using the edit buttons.

### Good to know

* When Cal.com integration is active, **no** playbook for appointment requests should be configured.
* Do not enter any appointment or booking items in the customer questions. This can disrupt the booking process because the agent may then treat the request as a knowledge question instead of using the calendar integration.
* Your API key is stored encrypted.
* The AI agent checks availability in your Cal.com calendar for every call.
* Changes to the configuration take effect immediately.
* If you delete the integration, the agent can no longer check or book appointments.

{% hint style="info" %}
With the **Enterprise plan** more complex appointment and process logic can also be mapped. [Learn more.](/documentation/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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.sipgate.com/documentation/en/connections-and-integrations/kalender.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.