Google Drive
The Google Drive connection lets agents read approved Google Drive files without broad workspace access. Use it when an agent needs source documents, folders, exports, sheets, PDFs, or shared-team files as context. It is OAuth-based and follows the connected Google account's Drive permissions.
When to Use It
Use it when an agent needs durable source material from Drive, such as product docs, support policies, contracts, proposals, or onboarding material, rather than a one-off chat attachment. It is a read-oriented knowledge source, best for document lookup, file retrieval, and data collections.
Setup
- In Connections, click Add Integration and choose Google Drive from the Google provider group.
- Sign in with the account that can already access the folders or shared drives the agent should read.
- Name the connection so it explains the source, such as Support Drive or Sales Enablement Docs, then choose private or shared access.
- Attach the connection to a data collection, agent configuration, or workflow step that needs file context.
What the Tool Can Do
- Answer from company documents. Connect product docs, support policies, contracts, proposals, or onboarding material through a data collection.
- Summarize shared files. Read files the connected account can access and return a concise summary, risks, owners, or next steps.
- Prepare repeatable research. Use Drive folders as stable source material for recurring reports, customer review packs, or operational workflows.
- Keep access bounded. Access is limited to what the Google account can already see, so scope the account before connecting it.
Security and Confirmation
Google Drive is a read-oriented connection, but it is still sensitive because retrieved file content becomes agent context. Use the smallest practical Google account or shared drive scope, review which agents can use the connection, and check Tool Runs or data-source status when access fails.
Before you connect, confirm that:
- The Google account has access to the exact files or folders the agent should read.
- The source is not better handled as a one-off chat attachment.
- The connection name tells users which Drive area it represents.
- Shared access is intentional and approved for the team using it.
- Sensitive folders are excluded or not shared with the connected account.
- The agent or data collection using this source has a clear purpose.
| Area | How to think about it |
|---|---|
| Authentication | OAuth with Google. Reauthorize if the token expires or scopes change. |
| Permission boundary | The connected Google account and Drive sharing rules decide what can be read. |
| Recommended access | Private for personal work; shared only for team-owned folders or shared drives. |
| Write behavior | Treat this as read-only unless your released tool surface explicitly adds write functions. |
| Audit | Review tool runs, data-source sync status, and admin audit logs when results look wrong. |
Example Usage
For durable source material, create a data collection from the Drive connection instead of asking users to upload the same file repeatedly. This gives agents a reusable knowledge surface and makes it easier to review processing status, failed files, and source ownership.
Use the Support Drive data collection only. Answer the customer question,
cite the source document name, and say "not found" if the answer is not in
the connected Drive files.
Technical Notes
- Implementation: OAuth 2.0 source connection to Google Drive, exposed as a read-oriented knowledge source for data collections.
- Authentication/scopes: OAuth with Google. The connected account's Drive sharing rules determine which files are visible; reauthorize when the token expires or scopes change.
- Write behavior: read-only in this docs surface. Retrieved file content can become agent context, so scope the connected account to the minimum needed.
Common Problems
| Symptom | Likely cause | Fix |
|---|---|---|
| Agent cannot find a file | The connected account cannot access it, or the file is not included in the data collection | Share the folder/file with the connected account and refresh the source. |
| Authorization failed | OAuth token expired or the Google account changed security settings | Reconnect Google Drive from the connection detail. |
| Wrong documents are used | The agent has multiple sources and picked the wrong one | Name the data collection explicitly in the prompt or attach only the intended source. |
| Shared connection is missing | Access policy does not include your team or agent | Ask an admin to share the connection or use a personal connection. |