How to Connect Google Drive to an AI Agent, Step by Step
· DoubleX
Quick answer
To connect Google Drive to an AI agent, open the Connectors screen, choose Google Drive, sign in with your Google account, and pick the connection type: personal, team, or company. Then choose which actions the agent can run, such as read-only, and test with a simple file search. In DoubleX Agentes, this takes a few minutes.
Connecting Google Drive is what lets an AI agent find, read, and create the files your team already keeps there: proposals, contracts, reports, shared folders. The setup is short, but two choices matter a lot: who the connection belongs to, and what the agent is allowed to do with your files. This guide covers only the connection itself.
What is the Google Drive connector in DoubleX Agentes?#
The Google Drive connector is a link between your Google account and the platform that lets agents use Drive's tools. According to the product, an agent with this connector can search, read, create, move, copy, and share files and folders.
A connector is one system tied to the platform. Agents use that system's tools only if you allow it. The same Google family also includes Gmail, Google Calendar, Google Sheets, Google Docs, and Google Slides, each connected separately. The Sheets, Docs, and Slides connectors can also find files by name.
What do I need before connecting?#
You need an account on the platform, a Google account that can open the files you want the agent to use, and a decision about who should own the connection. Creating an account is free and requires no credit card.
Before you start, check these items:
| Item | Why it matters |
|---|---|
| DoubleX Agentes account | The Connectors screen lives inside it |
| Google account with access to the files | The agent sees only what that account can see |
| An agent already created | You attach the connector to a specific agent |
| Role with permission to manage connectors | Company-wide connections are usually an admin decision |
| List of folders the agent should use | Helps you judge whether read-only is enough |
How do I connect Google Drive on the Connectors screen?#
Open the Connectors screen, select Google Drive, authorize your Google account, choose the connection type, and then attach it to the agent. The steps below follow the real flow in DoubleX Agentes.
- Create or open the agent that will work with your files on the Agents screen.
- Go to the Connectors screen and find Google Drive in the list.
- Start the connection and sign in with the Google account that has access to the files.
- Approve the access Google asks for.
- Choose the connection type: personal, team, or company (explained in the next section).
- Back in the agent, turn on Google Drive and choose which actions it may run.
- Save, then run a small test request.
Passwords, tokens, and keys for connections are stored encrypted with AES-256-GCM. For the technical details on connectors, see the Connectors reference.
Personal, team, or company connection: which one should I choose?#
Choose personal when the files belong to one person, team when a group shares the same folders, and company when everyone should use the same Drive resources. A personal connection only works for that person, like your own email would.
| Connection type | Who it applies to | Good fit |
|---|---|---|
| Personal | Only the person who connected it | Your own Drive, drafts, private folders |
| Team | Members of a team | A sales or finance shared folder |
| Company | The whole company | Shared policies, templates, company-wide folders |
A few practical rules help here:
- Start personal if you are testing. You can widen it later.
- Use team connections when a department has its own folders and its own agents.
- Use company connections sparingly, since more people's agents will reach the same files.
- Remember that roles (owner, admin, member) and sharing by person, team, or company also control who can use an agent.
How do I limit what the agent can do with my files?#
For each agent, you choose which systems it uses and, inside each system, which actions it may run. For Google Drive, that means you can keep the agent read-only or also allow it to create, move, copy, and share.
A sensible way to decide:
| Level | Actions allowed | When to use it |
|---|---|---|
| Read-only | Search and read files and folders | First tests, research, answering questions from documents |
| Read and create | Plus creating files and folders | Agents that produce reports or organize new material |
| Full | Plus moving, copying, and sharing | Trusted routines with clear rules |
Actions that change data can stay turned off. Even when they are on, the agent asks for confirmation before sending, deleting, or changing something in your systems, and it shows the steps it took. Every task keeps a full history: the request, each tool the agent used, and the result.
Start with read-only and enable more only when a real task needs it. Sharing deserves the most caution, because it can expose a file to people outside the folder's usual audience.
How do I test that the agent sees the right files?#
Send a few simple requests that only read files, then check the task history to confirm which tools the agent used and which files it found. If the results match what you expect, the connection is working.
Copy and adapt these test requests:
- "Search my Google Drive for the folder named Contracts 2025 and list the files inside it."
- "Find the most recent file with 'pricing' in the name and tell me when it was last modified."
- "List the folders at the top level of my Drive."
- "Try to open the file 'Payroll' and tell me whether you can access it."
The last request is a useful negative test: if the agent can open a file it should not, review the connected account and the connection type. Then open the task on the Tasks screen and read the tool-by-tool history.
Once the connection behaves as expected, see what you can automate in Google Drive with an AI agent and Google Drive prompts and requests to give your AI agent. If your files are mostly spreadsheets, connecting Google Sheets is the natural next step.
Frequently asked questions#
Does the agent see my entire Google Drive?#
It sees what the connected Google account can open. You narrow what it can do through the actions you allow for that agent, and you can keep it read-only.
Can I use the same connection for several agents?#
Connectors are configured per agent, so each agent uses only the systems and actions you enable for it. This lets different areas have their own agents with their own permissions.
Is my Drive content used to train AI models?#
No. Your company's content is not used to train models, and requests only go to AI providers that do not use what they receive for training. You can also choose zero retention on the Models screen.
Can the agent delete or share files without asking?#
Before sending, deleting, or changing something in your systems, the agent asks for confirmation and shows what it did. You can also turn off actions that change data.
Do I need to code to connect Google Drive?#
No. You connect it from the Connectors screen. If you want to automate it further, there is a REST API, a CLI, and an MCP server, and you can start with the Introduction.
Related guides
- How to Connect Google Calendar to an AI AgentLearn how to connect Google Calendar to an AI agent step by step: authorize access, choose personal, team or company scope, set permissions and test it.
- How to Connect Google Sheets to an AI Agent, Step by StepLearn how to connect Google Sheets to an AI agent: authorize the connector, pick personal, team or company scope, and set read-only or write access per agent.