CoAgentorGoogle Drive
Connecting Google Drive lets you hand specific files to CoAgentor through Google's own file picker. Each file you choose becomes available inside your contexts — automatically downloaded, indexed, and kept in sync when you edit it in Drive.
What access CoAgentor requests
CoAgentor uses the drive.file OAuth scope. This is the narrowest scope Google offers for Drive integrations: it grants CoAgentor access only to the specific files you select via Google's file picker, and nothing else.
- We can read the files you hand us through the picker
- We cannot list, browse, or search any other file in your Drive
- We never create, modify, or delete files in your Drive
If you stop using CoAgentor with a particular file, the picker grant on that file lasts only as long as the connection. Disconnecting the integration revokes our access entirely.
Connecting your account
- Go to Integrations → and click the Data Sources tab
The Data Sources tab showing the Google Drive card — before connection
- Click Connect Google Drive
- Sign in with your Google account and authorise the requested permissions
Authorising CoAgentor to connect to your Google Drive account
- Your Drive connection will appear with a Connected badge showing your account email
Connection confirmed, with the option to disconnect
Connecting the account does not give CoAgentor access to any files yet — you'll choose them later, file by file, when building a context.
Connecting multiple Google Drive accounts
Depending on your plan, you can connect more than one Google account. Each account appears as a separate connection and can be picked from independently inside the context builder.
| Plan | Google Drive accounts |
|---|---|
| Free | 1 |
| Solo | 2 |
| Pro | Unlimited |
Disconnecting an account
- Go to Integrations → Data Sources →
- Click Disconnect next to the account you want to remove
- Confirm the prompt
Disconnecting removes all files and embeddings sourced from that account. Any contexts referencing that content will stop retrieving it. The context itself is not deleted — only the Drive-sourced data is removed. The picker grants on the previously selected files are also revoked at the Google end.
Troubleshooting
Picker doesn't open or shows an error — Refresh the page and try again. If the issue persists, check that your browser isn't blocking third-party scripts from apis.google.com (some privacy extensions and corporate networks do this).
File doesn't appear after picking — Make sure the file type is supported. If you picked an unsupported type, the picker will accept it but ingestion will fail in the background. See the full list of supported file types →.
A new file in a folder isn't syncing automatically — This is expected. Because CoAgentor only ever sees the specific files you hand it, new files added to a folder later need to be picked explicitly. Open the picker again to add them to your context.