> 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/chrome-extension/google-calendar.md).

# Google Calendar

Open a Distro meeting in Google Calendar to access **View in Distro** and the available no-show controls. The buttons appear on meetings Distro can match to a booking.

Use **View in Distro** when you need the full booking details. Mark a meeting as a no-show only when the prospect didn't attend; use the undo action if it was marked by mistake.

To show or hide these controls, open the extension's **Settings → Browser integrations → Calendar event buttons**.

You can also type `di/` into an event description to insert a meeting link. That is controlled separately under **Keyword detection → Google Calendar**.

If the buttons are missing, check that you're signed in, the event belongs to a Distro booking, and **Calendar event buttons** is enabled. Refresh the Calendar page after installing or updating the extension.


---

# 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/chrome-extension/google-calendar.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.