Files and knowledge
Google Drive for AI agents.
Managed auth, ready-made tools.
Find, read and organize the files in each user's Drive.
Tools
What your agent can do in Google Drive.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Google Drive connection.
-
Search files
Readgoogle_drive_searchFind files by name, type or content.
-
Read a file
Readgoogle_drive_get_fileRead a file's content and metadata.
-
Upload a file
Writegoogle_drive_uploadCreate a file in a folder.
-
Share a file
Writegoogle_drive_shareGive a person access to a file.
No tool matches that search.
Get started
Connect Google Drive
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect Google Drive
Each end user authorizes their own Google Drive account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Google Drive account, once. const connection = await agent200 .user("user_123") .connect("google_drive"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the Google Drive tools
Name the user, the model and the tools. The model decides which Google Drive tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "Find the Q3 board deck", tools: ["google_drive"], }); console.log(result.output);
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Google Drive connector and how to use it.
Connector: Google Drive, through Agent200. In code: "google_drive". What it does: Find, read and organize the files in each user's Drive. Page: https://www.agent200.com/tools/google-drive/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on Google Drive's own page, through the authorization link Agent200 returns. Never ask a user for a Google Drive password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: google_drive_search, google_drive_get_file. Write tools: google_drive_upload, google_drive_share. Name "google_drive" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/tools/google-drive/framework/claude/ https://www.agent200.com/tools/google-drive/framework/chatgpt/ https://www.agent200.com/tools/google-drive/framework/claude-code/ https://www.agent200.com/tools/google-drive/framework/muse/ https://www.agent200.com/tools/google-drive/framework/grok-bot/ https://www.agent200.com/tools/google-drive/framework/openai-dots/ https://www.agent200.com/tools/google-drive/framework/claude-duet/ https://www.agent200.com/tools/google-drive/framework/hermes-agent/ https://www.agent200.com/tools/google-drive/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /tools/google-drive.md
Guides
Use Google Drive with the AI you build on.
Step-by-step setup for Google Drive with a specific model, assistant or agent framework.
-
Google Drive + Claude
How to connect Google Drive to Claude
-
Google Drive + ChatGPT
How to connect Google Drive to ChatGPT
-
Google Drive + Claude Code
How to connect Google Drive to Claude Code
-
Google Drive + Muse
How to connect Google Drive to Muse
-
Google Drive + Grok Bot
How to connect Google Drive to Grok Bot
-
Google Drive + OpenAI Dots
How to connect Google Drive to OpenAI Dots
-
Google Drive + Claude Duet
How to connect Google Drive to Claude Duet
-
Google Drive + Hermes Agent
How to connect Google Drive to Hermes Agent
-
Google Drive + OpenClaw
How to connect Google Drive to OpenClaw
FAQ
Google Drive and Agent200, answered.
Who handles the Google Drive OAuth flow and the tokens?
Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Google Drive.
Does my agent act as the end user?
Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Google Drive connection, never another user's. It cannot reach anything the user or Google Drive has not authorized.
Can I limit what my agent can do in Google Drive?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.