Google Drive + OpenAI Dots
Connect Google Drive to OpenAI Dots
with OpenAI models and the Agent200 SDK
Dots cannot send an API key to a custom MCP server, so this guide builds an always-on Google Drive agent with OpenAI's models and the Agent200 SDK.
On this page
Overview
OpenAI Dots use the plugins connected to a ChatGPT account, and ChatGPT’s custom MCP servers cannot send an API key. To give an always-on agent the Google Drive tools, build it with the Agent200 SDK and OpenAI’s models: this guide shows how.
Your agent then calls the Google Drive tools with each user’s own Google Drive connection: Agent200 runs the OAuth flow, stores the tokens and keeps them fresh.
- Connector
- Google Drive
- Works with
- OpenAI Dots · Your own agent code
- Authentication
- Managed OAuth, per end user
- You need
- An Agent200 API key
- Tools
- 4 tools
- Model in examples
openai/gpt-5.6-sol
Before you start
- An Agent200 API key. Create one on the API keys page of the dashboard.
- Google Drive enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- An end user with a Google Drive account. They approve access once, on Google Drive's own page.
- A model for your agent. The examples use openai/gpt-5.6-sol, through the same Agent200 API key.
Connect Google Drive to OpenAI Dots
-
1
Step 1: Create your Agent200 API key
Open the API keys page in the Agent200 dashboard and choose Create an API key. Copy the key and store it as an environment variable, AGENT200_API_KEY, or in your secrets manager. One key covers Google Drive and every other connector and model enabled for your project. Keep it out of chats, prompts and source control.
.envConceptual exampleStore the Agent200 API key as an environment variable # Keep the key out of your code, prompts and chats. export AGENT200_API_KEY="paste-your-key-here" -
2
Step 2: Set up the Agent200 SDK
Add the SDK to your project and create a client with the key from the environment.
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, }); -
3
Step 3: Let your user connect Google Drive
Each end user authorizes their own Google Drive account once, through managed OAuth. If the user has not connected yet, Agent200 returns an authorization link: show it to them, and they approve access on Google Drive's own page. Agent200 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); } -
4
Step 4: Run with the Google Drive tools
Name the user, the model and Google Drive in the tools. The model decides when a Google Drive tool is needed, and Agent200 executes the call with the user's own 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);
Test your connection
Run one request to check everything is wired up.
Ask
Find the Q3 board deck
What should come back
-
An answer in
result.output, built from the user's own Google Drive data. -
Behind the scenes, the model calls a Google Drive tool, such as
google_drive_search, and Agent200 runs it.
If Agent200 returns an authorization link instead, the user has not connected Google Drive yet. Go back to the connect step.
Get your API key
Create a key in the Agent200 dashboard. It reaches Google Drive and every other connector enabled for your project.
Instructions for AI agents
Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Google Drive to OpenAI Dots.
Goal: connect Google Drive to OpenAI Dots with Agent200. Guide: https://www.agent200.com/tools/google-drive/framework/openai-dots/ 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. Make sure Google Drive is enabled for the project in the Agent200 dashboard (Connectors), with the endpoints and scopes the task needs. 3. Add the Agent200 SDK to the project and create a client with that key. 4. Give every request a stable id for the end user. Agent200 uses only that user's own connections. 5. Connect the user's Google Drive account through Agent200. If Agent200 returns an authorization link, show it to the user and continue once they have approved access on Google Drive. 6. Run requests through Agent200 with a model (for example openai/gpt-5.6-sol) and "google_drive" in the tools. The model decides when a Google Drive tool is needed; Agent200 executes the call. 7. Check it works with this request: "Find the Q3 board deck" What should come back: - An answer in `result.output`, built from the user's own Google Drive data. - Behind the scenes, the model calls a Google Drive tool, such as `google_drive_search`, and Agent200 runs it. 8. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in Google Drive, then retry. The code on the guide page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
The whole guide is also available as Markdown, for agents and LLMs: /tools/google-drive/framework/openai-dots.md
Google Drive tools OpenAI Dots can call
-
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.
How it works
-
01
Your app sends the request
It calls Agent200 with the model, instructions, the input, the end user's id and the Google Drive tools.
-
02
The model picks a tool
The model decides whether a Google Drive tool is needed, and with which arguments.
-
03
Agent200 runs the call
It uses that user's own Google Drive connection, within the endpoints and scopes your project allows, and returns the result to the model.
-
04
Your app gets the result
Agent200 returns the completed result. Your app decides when the agent runs and what happens next.
Each user's own connection. Connections belong to individual end users. A request for one user never reaches another user's Google Drive account.
Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and Google Drive enforces what its API grants.
Troubleshooting
Why not connect Agent200 to a dot directly?
A dot uses the plugins connected to your ChatGPT account, and ChatGPT’s custom MCP servers cannot send an API key. Building the agent with the Agent200 SDK, as on this page, is the route that works.
The request says Google Drive authorization is required
The end user has not connected Google Drive yet, or the connection needs to be approved again. Agent200 returns an authorization link: show it to the user, let them approve access on Google Drive's own page, then run the request again.
OpenAI Dots does not use the Google Drive tools
Check that Google Drive is enabled for your project in the dashboard's Connectors settings and that it is in the tools you send with the request. Naming Google Drive in the request, or in the instructions, also helps the model choose the right tool.
A tool call is refused or returns less than expected
Agent200 runs only what your project allows (services, endpoints and scopes), and Google Drive returns only what the end user authorized. Widen the endpoints or scopes in the dashboard if the agent needs more, then ask the user to connect Google Drive again so they can approve the new access.
The results come from the wrong account
Every request names an end user (user_123 in the examples). Pass the id of the person your agent is working for: Agent200 then uses only that user's Google Drive connection, never another user's.
The API key was pasted into a chat or committed
Create a new key on the API keys page, update AGENT200_API_KEY wherever your app reads it, and stop using the old one. Keep keys in environment variables or a secrets manager, never in prompts, chats or source control.