> ## Documentation Index
> Fetch the complete documentation index at: https://docs.atako.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Google Calendar

> Connect Google Calendar to your Atako agents — 5 read and 4 write actions.

Let your agents read your calendars, and create or update events on your behalf.

## Connection

* **Authentication**: OAuth 2.0 — you authorize Atako via Google Calendar's consent screen; no key to copy.
* **Scopes requested**:
  * `https://www.googleapis.com/auth/calendar`

See [Google Calendar's documentation](https://developers.google.com/workspace/calendar/api/v3/reference).

## Read actions (5)

| Action            | Description                                                   |
| ----------------- | ------------------------------------------------------------- |
| `get_calendar`    | Fetch a calendar by id (use "primary" for the main calendar). |
| `get_event`       | Fetch a single event.                                         |
| `list_calendars`  | List the calendars on the connected account.                  |
| `list_events`     | List events of a calendar, optionally within a time window.   |
| `query_free_busy` | Query free/busy intervals across calendars for a time window. |

## Write actions (4)

| Action            | Description                                                       |
| ----------------- | ----------------------------------------------------------------- |
| `create_event`    | Create an event (start/end use RFC3339 dateTime or all-day date). |
| `delete_event`    | Delete an event.                                                  |
| `quick_add_event` | Create an event from a natural-language sentence.                 |
| `update_event`    | Update fields of an existing event.                               |

## Permissions

Every action above must be explicitly granted to an agent before it can be used. See [Permissions](/integrations/permissions) for the grant model and [Security](/integrations/security) for how credentials are protected.