> For the complete documentation index, see [llms.txt](https://help.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.distro.so/integrations/calendars.md).
# Calendars
Connect the calendar you use for meetings so Distro can check busy times and add new bookings.
In the Distro app, open **Settings → My Integrations** and connect your calendar provider. Complete the provider's sign-in flow, then return to **Settings → Calendars**.
Choose your **Primary calendar** and click **Save**. This is where Distro creates new events. Review your calendar connection and availability before sharing a booking link.
If a calendar needs reconnecting, restore the connection before relying on that host's availability. A saved calendar row can remain visible even when its provider needs reconnecting.
The event details visible while scheduling can be limited to the primary calendar or hidden by privacy settings. Choose from the available times Distro offers; the absence of a visible event does not prove that a time is free.
Open **Settings → Conferencing** to review how online meeting details are provided. Calendar connection and conferencing are separate parts of setup: check both before sharing your first link.
## Check the booking experience
Open one of your booking links and preview the available dates. If the times don't look right, check your [weekly hours](/settings/personal-settings/my-availability.md), timezone, and the link's [event type](/event-types/create-an-event-type.md).
If your calendar connection needs attention, use **Manage integrations** from the Calendars page to return to the connection settings. Reconnect the intended account and check the primary calendar again.
Changing the primary calendar controls where new bookings are created. It is not a way to move existing meetings between calendars.
---
# 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.distro.so/integrations/calendars.md?ask=&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.
