> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/integrations/google-calendar.md). # Google Calendar Each host connects their own Google Calendar from **Settings → My Integrations**. A workspace CRM connection does not connect members' calendars. ## Connect your calendar Choose Google Calendar and authorize the Google account you use for meetings. Open the calendar settings afterward and review which calendars Distro checks for conflicts and which calendar is primary for bookings. Set your timezone and [Working hours](/settings/working-hours.md). Check [Time off](/settings/time-off.md) before making your link available to guests. ## Check a booking Open your booking link in a guest session. Choose a suitable slot and complete a controlled booking. Verify the guest confirmation, calendar event and meeting location. Google Meet depends on the event's selected location and usable Google calendar connection. Connecting Google Calendar does not change every event's conferencing choice. ## If times are missing Check busy events, selected calendars, minimum notice, booking window, duration, buffers, time off and required co-hosts. A connected account can still have an expired grant or an unavailable calendar. Reconnect when the integration shows an authorization problem. Avoid treating a missing calendar response as free time; Distro can refuse availability when it cannot check the required calendars. See [Calendars and availability](/scheduling/availability.md). --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.distro.so/integrations/google-calendar.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 `build a script that syncs our docs to a CMS` 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.