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

# Google Docs

### Overview

The Google Docs integration links nexos.ai with your Google Docs, allowing document content to be available directly inside your workspace. It makes it easier to locate key information, review shared notes, access project documentation, and stay updated on collaborative content without opening multiple files. This integration helps teams work more efficiently by keeping important documents and knowledge easily accessible.

### Setting up the integration (as an admin)

1. Click on your **Profile icon.**
2. Go to **Management** -> **Apps.**
3. Find **Google Docs** in the list.
4. Set the integration to **Active** (enabled).

### Connecting your account (as a member)

1. Click on your profile icon.
2. Go to **Get apps** -> **My apps.**
3. Find **Google Docs** and select **Connect**.
4. You will be redirected to Google Docs. Sign in if prompted.
5. Review the access request screen (it will list what nexos.ai can access in **Google Docs**) and select **Accept** to approve.
6. Return to nexos.ai. **Google Docs** should now show as connected in **My Apps**.

### Use Google Docs in Chat (turn it on for a conversation)

1. Open **New Chat.**
2. Click on a "**+**" -> **Integrations.**
3. **Toggle on** **Google Docs** to use it in that conversation.

### Use Google Docs in Agents (turn it on for an agent)

1. Open **Agents** and select the agent you want to update.
2. Select the **Studio** icon (top-right), then open **Settings**.
3. Scroll to **Integrations** and turn **Google Docs** **on**.
4. **Save** your changes, then test the agent.


---

# 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.nexos.ai/workspace/integrations/google-docs.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.