> For the complete documentation index, see [llms.txt](https://docs.eesel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eesel.ai/integrations/knowledge/google-drive.md).

# Google Drive

Connect Google Drive to your AI agent. It answers from the Docs, Sheets, PDFs and files you pick, in your helpdesk, Slack and chat, with the file linked.

Your agent answers from the Google Drive files and folders you pick, links the file it used, and never changes anything in your Drive.

<figure><img src="https://3732419023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2xXO0947TYoPIhGoBgSE%2Fuploads%2Fgit-blob-2c0bac1432b49f77f81766f2d8113388167fa112%2Fgoogle-drive-hero.png?alt=media" alt="A Google Drive knowledge source card listing synced files, feeding an agent that answers a question in Slack and links the file it read"><figcaption><p>The Drive files you pick become knowledge your agent answers from.</p></figcaption></figure>

{% hint style="info" %}
**Using Claude Code, Codex or Cursor?** Ask it to help connect Google Drive with [eesel CLI](https://docs.eesel.ai/apis-and-developer-resources/cli). Point it to the [setup guide](https://docs.eesel.ai/getting-started/set-up-from-a-coding-agent).

**Using Claude.ai or ChatGPT?** Use the eesel connector (MCP). See [Claude and other assistants](https://docs.eesel.ai/apis-and-developer-resources/use-eesel-from-claude-and-other-assistants.md) or [ChatGPT](https://docs.eesel.ai/apis-and-developer-resources/use-eesel-from-chatgpt.md). If the eesel connector is already linked to the correct workspace, keep using it. For steps it cannot complete, use the dashboard.

**CLI details for your coding tool:** You still need to sign in and choose files in the dashboard picker below; the CLI cannot replace it. Select the right workspace, complete those steps, then check `eesel status` and use `eesel chat` to test a question from a selected document.
{% endhint %}

## What your agent sees

Google Drive is a knowledge source. Your agent reads copies of the files you pick, indexed ahead of time and searched when a question comes in.

* **Only what you pick.** The files and folders you tick in the picker, from My Drive, Shared with me and Shared Drives. Nothing else in your Drive is read.
* **Whole folders, including subfolders.** A picked folder brings in every supported file inside it, up to 20 folder levels deep.
* **The text of each file.** Google Docs and Slides as text, every tab of a Google Sheet, modern Word, Excel and PowerPoint files (`.docx`, `.xlsx`, `.pptx`), PDFs, and text files such as `.txt`, `.md`, `.csv`, `.html`, JSON and XML.
* **A link to each file.** Answers link the Drive file. Someone clicking it still needs access to the file in Drive.
* **Not there:** images, video, audio, Google Forms, Maps, Sites, shortcuts, files in the trash, files over 50 MB, and legacy `.doc`, `.xls` and `.ppt` files. Comments and version history are not read either.
* **A snapshot, not a live view.** Files are copied when they sync. Edits in Drive show up after the next re-sync.

### Sources

On the integration page your files are grouped into three rows, each with its own count and toggle:

| Source            | Description                                           | Requires                                               |
| ----------------- | ----------------------------------------------------- | ------------------------------------------------------ |
| **Google Docs**   | Google Docs and Google Slides, as text                | The file, or a folder holding it, picked in the picker |
| **Google Sheets** | Spreadsheet data, across every tab in the sheet       | As above                                               |
| **Other Files**   | Word, Excel and PowerPoint files, PDFs and text files | As above                                               |

Every other integration on the agent is also a source, so a Drive answer can draw on Confluence, Notion, your helpdesk and your website at once. See [Integrations](https://docs.eesel.ai/integrations/overview.md).

## What it can do

### Triggers

Google Drive has no triggers. Nothing that happens in Drive starts your agent.

### Actions

Google Drive has no actions, so your agent can't change anything in your Drive.

## Set up eesel in Google Drive

{% stepper %}
{% step %}

### Ask your agent to connect Google Drive

Open the chat in your dashboard and ask it to connect Google Drive. The sign-in has to happen in the dashboard. Your agent links the Integrations page and tells you to click Google Drive there. Prefer to click? That page has the same **Connect Google Drive** option.

<figure><img src="https://3732419023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2xXO0947TYoPIhGoBgSE%2Fuploads%2Fgit-blob-d619f0d5d9539d94a1a9965807438e07eb1d0ca0%2Fgoogle-drive-connect-chat.png?alt=media" alt="The dashboard chat where the user asks to connect Google Drive and the agent links the Integrations page and explains the approval"><figcaption><p>The agent hands you the link and says what happens after you approve.</p></figcaption></figure>
{% endstep %}

{% step %}

### Sign in and grant read access

Clicking Google Drive opens a short notice. The connection is brokered by Pipedream, our integration provider, so Pipedream is named here and on Google's own screen. Click **Continue**.

<figure><img src="https://3732419023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2xXO0947TYoPIhGoBgSE%2Fuploads%2Fgit-blob-c1e6e361473b7da4618bc04599bbc8abdeea46d9%2Fgoogle-drive-pipedream.png?alt=media" alt="A dashboard modal saying eesel AI uses Pipedream to connect your account, with a Continue button"><figcaption><p>The notice that names Pipedream as the integration provider.</p></figcaption></figure>

Google's sign-in and consent screen comes next. It names Pipedream and lists one Drive permission whose wording covers more than reading. eesel uses it only to read the files you pick in the next step. Pick the account whose files you want read, then click **Continue**. Your agent never sees more than that Google account can see.

A person approves this in the browser.
{% endstep %}

{% step %}

### Pick your files and folders

Back in the dashboard, the **Add files from Google Drive** picker opens. Search, or tick items under **My Drive** and **Shared with me**, including files in Shared Drives. Picking a folder brings in every supported file inside it, walking subfolders up to 20 levels deep. Click **Add files** when you are done.

<figure><img src="https://3732419023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2xXO0947TYoPIhGoBgSE%2Fuploads%2Fgit-blob-c036a8eec4a509434a53ffc30d20220acef9c333%2Fgoogle-drive-file-picker.png?alt=media" alt="The connected Google Drive integration page with the file picker open, showing a search box and folder checkboxes under My Drive and Shared with me"><figcaption><p>The picker, with folders listed under My Drive and Shared with me.</p></figcaption></figure>

{% hint style="warning" %}
**New files arrive on the next re-sync, not on their own.** Drop a file into a folder you picked, then ask your agent to re-sync Google Drive, and the file is indexed. A file outside your picked folders still needs picking. A folder picked before 3 November 2026 is only re-checked once you pick it again.
{% endhint %}
{% endstep %}

{% step %}

### Confirm the connection and check what it can read

**Integrations > Google Drive** shows the connection as **Connected**, with **Start a chat** buttons and a **Sources** list of what the agent can read. Each source row has its own document count and its own toggle, and **Add** re-opens the picker.

<figure><img src="https://3732419023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2xXO0947TYoPIhGoBgSE%2Fuploads%2Fgit-blob-6a572f3cb406bd45efd27d55a5bb1b434de39bce%2Fgoogle-drive-integration-page.png?alt=media" alt="The Google Drive integration page showing a Connected badge, Start a chat buttons, and Sources rows for Google Docs, Google Sheets and Other Files with document counts and toggles"><figcaption><p>Each source row has its own document count and its own toggle.</p></figcaption></figure>

**Check it worked.** Each source row shows its document count once its sync is done. From a terminal, `eesel status` lists the integration as connected with its source counts.
{% endstep %}

{% step %}

### Ask it something

Ask a question that only a Drive file can answer. Your agent answers and links the file it used in its answer, with follow-up suggestions.

<figure><img src="https://3732419023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2xXO0947TYoPIhGoBgSE%2Fuploads%2Fgit-blob-76947d6fc99867784a90d7217609db6abdc3125b%2Fgoogle-drive-test-chat.png?alt=media" alt="The dashboard chat answering a question from a Drive document, with a table in the answer and a link to the document"><figcaption><p>An answer built from a Drive document, with the source file linked.</p></figcaption></figure>
{% endstep %}

{% step %}

### Tell it how to answer

Tell your agent a standing rule in plain language. It shows you the exact wording it wants to save and asks you to confirm before it writes anything.

<figure><img src="https://3732419023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2xXO0947TYoPIhGoBgSE%2Fuploads%2Fgit-blob-daffda26e3c642e4fb026e0603930eff45f9ef6b%2Fgoogle-drive-instruction-chat.png?alt=media" alt="The dashboard chat where the user gives a standing rule, the agent shows the exact wording it will save, and confirms it saved"><figcaption><p>The agent shows the wording it will save, then asks you to confirm.</p></figcaption></figure>

The saved rule lives on the **Instructions** page, where you can read it and edit it by hand.

<figure><img src="https://3732419023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2xXO0947TYoPIhGoBgSE%2Fuploads%2Fgit-blob-4ab70d55dc81e8c1662fae7db1e3102bdc554fd8%2Fgoogle-drive-instruction-saved.png?alt=media" alt="The Instructions page open beside the chat, showing the saved rule as editable text"><figcaption><p>The rule on the Instructions page, ready to edit.</p></figcaption></figure>
{% endstep %}

{% step %}

### Use it where your team works

A teammate can mention your agent in Slack and get the answer in the thread. The source file is linked, and any rule you saved is applied.

<figure><img src="https://3732419023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2xXO0947TYoPIhGoBgSE%2Fuploads%2Fgit-blob-f2ce001033b47bd2e28eeddc6f70b2b2a3e41f59%2Fgoogle-drive-slack-thread.png?alt=media" alt="A Slack thread where a teammate mentions eesel and the eesel app answers from a Drive document, links the source file and adds a reminder"><figcaption><p>The same answer in a Slack thread, with the source linked.</p></figcaption></figure>
{% endstep %}
{% endstepper %}

## Things to know

* **Nothing re-syncs on its own.** Ask your agent to re-sync Google Drive when files change, or pick the files again in the picker.
* **A re-sync covers what you already picked.** It refreshes indexed files, finds new files in picked folders, drops files deleted or trashed in Drive, and updates renamed ones. A loose file outside your picked folders needs picking.
* **Up to 2,500 files a day per workspace.** Each file inside a picked folder counts. A sync that would pass the cap stops with a daily limit message instead of syncing part of the batch.
* **Some files are skipped.** Files over 50 MB, legacy `.doc`, `.xls` and `.ppt` files, images, video, audio, Google Forms, Maps, Sites and shortcuts.
* **Deleting a file in eesel is not enough.** A file you delete from eesel but leave in a picked folder comes back on the next re-sync. Move it out of the folder in Drive to keep it out.
* **Your agent sees what the connected Google account sees.** A file that account can't open can't be picked or synced.
* **Older connections can't re-sync.** A Google Drive connected before the move to our current integration provider shows a legacy warning. Reconnect it and pick your files again.

## Troubleshooting

<details>

<summary>A file is not being answered from?</summary>

If you added the file recently, re-sync, or pick it in the picker if it is not inside a folder you picked. Otherwise check that the file is a supported type and under 50 MB, that it is owned by or shared with the connected Google account, that it is not in the trash, and that it is not nested more than 20 folder levels below the folder you picked.

</details>

<details>

<summary>Answers are out of date?</summary>

Nothing refreshes on its own. Ask your agent to re-sync Google Drive. It refreshes the files already indexed and finds new files in the folders you picked. A file picked on its own that never synced needs picking again.

</details>

<details>

<summary>Sync stopped with a daily limit message?</summary>

Run the sync again the next day, or get in touch to have the 2,500-file daily limit raised.

</details>

<details>

<summary>Connection expired or showing a legacy warning?</summary>

Google access can expire or be revoked. Disconnect and reconnect to refresh it. The same fix moves a legacy connection onto the current integration. A reconnect is a new connection, so pick your files again afterwards.

</details>

## FAQ

<details>

<summary>How do I add an AI agent to Google Drive?</summary>

Connect Google Drive to eesel, pick the files and folders you want, and your eesel agent answers from them. Ask it in the dashboard chat to connect Google Drive, sign in with Google, then choose files in the picker. See [Set up eesel in Google Drive](#set-up-eesel-in-google-drive).

</details>

<details>

<summary>Can I connect Google Drive to ChatGPT or Claude?</summary>

Yes, through eesel. Once Google Drive is connected, you can talk to your eesel agent from Claude, ChatGPT or Cursor, and it answers from your Drive files. See [Use eesel from Claude and other assistants](https://docs.eesel.ai/apis-and-developer-resources/use-eesel-from-claude-and-other-assistants.md), [Use eesel from ChatGPT](https://docs.eesel.ai/apis-and-developer-resources/use-eesel-from-chatgpt.md) and [Claude Code and MCP clients](https://docs.eesel.ai/apis-and-developer-resources/claude-code-and-mcp-clients.md).

</details>

<details>

<summary>Which Google Drive file types can my agent read?</summary>

Google Docs, Sheets and Slides, modern Word, Excel and PowerPoint files (`.docx`, `.xlsx`, `.pptx`), PDFs, and text-based files such as `.txt`, `.md`, `.csv`, `.html`, JSON and XML. Images, video, audio, Google Forms, Maps, Sites and shortcuts are skipped, and so are legacy `.doc`, `.xls` and `.ppt` files.

</details>

<details>

<summary>Can my agent change anything in my Google Drive?</summary>

No. The integration is read-only and exposes no actions at all. Your agent reads the files you picked and can never edit, move, rename or delete anything in your Drive.

</details>

<details>

<summary>Why is my agent not answering from a file I added to Google Drive today?</summary>

Nothing re-syncs on its own, so a new file waits for the next re-sync. Ask your agent to run one. A re-sync finds new files inside the folders you picked. A file outside them needs picking in the picker. If a re-sync still misses a file in a picked folder, pick the folder again once: folders picked before 3 November 2026 are only remembered after that.

</details>

<details>

<summary>What happens if I delete or rename a file in Google Drive?</summary>

Both are reconciled on the next re-sync. A deleted file is dropped from your agent's knowledge, and a renamed file is updated to match.

</details>

<details>

<summary>Does Google Drive re-sync on its own?</summary>

No. Content refreshes when you ask your agent to re-sync, or when you pick files again in the picker.

</details>

## Related pages

* [Internal operations](https://docs.eesel.ai/use-cases/internal-operations.md)
* [Integrations overview](https://docs.eesel.ai/integrations/overview.md)
* [Set up from Claude Code or the terminal](https://docs.eesel.ai/getting-started/set-up-from-a-coding-agent.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.eesel.ai/integrations/knowledge/google-drive.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.
