> ## 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 Drive

> Connect Google Drive to your Atako agents — 11 read and 15 write actions.

Let your agents search, organize and share your Google Drive files — folders, metadata, permissions, comments and export links.

## Connection

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

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

## Read actions (11)

| Action             | Description                                                                          |
| ------------------ | ------------------------------------------------------------------------------------ |
| `get_about`        | Fetch account info — user identity, storage quota and import formats.                |
| `get_drive`        | Fetch a shared drive — name, restrictions and capabilities.                          |
| `get_export_links` | Get the web view, download and per-format export links of a file.                    |
| `get_file`         | Fetch file metadata — name, mimeType, parents, owners, size, links.                  |
| `get_permission`   | Fetch a single permission by id.                                                     |
| `list_comments`    | List comments on a file, newest first.                                               |
| `list_drives`      | List the shared drives the connected account can access.                             |
| `list_files`       | List files, optionally inside a folder (trashed items excluded by default).          |
| `list_permissions` | List who has access to a file or shared drive.                                       |
| `list_revisions`   | List the revision history of a file.                                                 |
| `search_files`     | Search files with a Drive query (e.g. "name contains 'report' and trashed = false"). |

## Write actions (15)

| Action                 | Description                                                             |
| ---------------------- | ----------------------------------------------------------------------- |
| `copy_file`            | Copy a file, optionally with a new name or destination folder.          |
| `create_comment`       | Add a comment to a file.                                                |
| `create_folder`        | Create a folder, optionally inside a parent folder.                     |
| `create_permission`    | Share a file with a user, group, domain or anyone, at a given role.     |
| `create_shortcut`      | Create a shortcut pointing at another Drive file or folder.             |
| `delete_file`          | Permanently delete a file, bypassing the trash (irreversible).          |
| `delete_permission`    | Revoke a permission, removing that user, group or link access.          |
| `empty_trash`          | Permanently delete all files in the trash (irreversible).               |
| `move_file`            | Move a file to another folder (add the new parent, remove the old one). |
| `rename_file`          | Rename a file or folder.                                                |
| `reply_to_comment`     | Reply to an existing comment on a file.                                 |
| `restore_file`         | Restore a trashed file back to its original location.                   |
| `trash_file`           | Move a file to the trash (recoverable until the trash is emptied).      |
| `update_file_metadata` | Update file metadata — description, starred flag or folder color.       |
| `update_permission`    | Change the role of an existing permission (e.g. reader to writer).      |

## 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.