Search Google Drive, download files as context, and upload upstream files (e.g. a generated image) back to Drive. Runs through the Nango proxy.
| Category | 🗄️ Storage |
| Connection | ⚡ OAuth 2.0 one-click, handled by Nango |
| Actions | 3 total — 2 read, 1 write |
Once connected, Google Drive exposes the following actions. The AI can call them with #-mentions in chat, an agent can be granted a subset as tools, and a workflow can run them in an integration-action node.
| Action | Type | What it does | Proxy |
|---|---|---|---|
Search Filessearch-files | Read | Search Google Drive files. | Yes |
Get Fileget-file | Read | Download a Google Drive file as base64-encoded bytes. | Yes |
Upload Fileupload-file | Write | Upload an upstream file (image, doc, HTTP download) to Drive. | Yes |
Actions tagged Write create, update, or delete data. In chat and agent paths they pause for your confirmation before running; workflows treat their deterministic wiring as implicit consent. Agent tools covers how to scope which actions an agent may use.
Google Drive is governed per organization: an admin sets a monetary spend cap and a monthly call quota. A quota of 0 disables the integration — it never means unlimited. See the Integrations overview for the full governance model.