Google Workspace
Give your agents full access to Google Drive.
Agents find files, read them, organize folders, and manage sharing. Each agent has a real computer, so it can download a file, open it, analyze it, and write the result back to Drive.
5,000 free credits to start.
Agent reach
Google Drive API v3
The full surface, searched at run time.
Connect with
- Helios OAuth app
- Your own OAuth app
Event triggers
Not yet
Manual, schedule, and signed webhook are available.
What the agent can do
What agents do with Google Drive
Helios searches the Google Drive API v3 at run time. The agent finds the endpoint the task needs and calls it.
- Search the Drive API surface at run time and call any endpoint your scopes allow.
- Search files and folders with Drive's full query syntax.
- Download files into the sandbox to read, parse, and analyze with code.
- Create folders, move files, rename, and organize by content.
- Upload generated artifacts - reports, exports, cleaned data - back to Drive.
- Read and update sharing permissions on the files a task touches.
Examples
Tasks you can hand to a Google Drive agent
Organize a folder that got out of hand
The agent reads what each file actually contains, proposes a folder structure, and files everything where it belongs.
Organize the `Shared Uploads` folder by content and tell me what you did.
- google-drive·list 340 files in `Shared Uploads`
- code·classify by content and date
- google-drive·create folders and move files
- slack·post the summary to #ops
340 files organized
- 7 folders created by document type
- 22 near-duplicates grouped for review
- Nothing deleted
Audit who has access to what
A scheduled agent sweeps a folder for files shared beyond your domain and reports each one with its sharing settings.
Weekly, flag any file in `Finance` shared outside the company.
- google-drive·list files and permissions in `Finance`
- code·filter external and link-shared files
- slack·DM the finance lead
3 files shared externally
- 1 open to anyone with the link
- 2 shared with a former contractor
- Suggested revocations listed
Extract data from a pile of documents
Point the agent at a folder of contracts or reports. It opens each one, pulls the fields you name, and writes a table.
Read every contract in `Vendor Agreements` and build a renewal table.
- google-drive·download 28 PDFs
- code·extract term, renewal date, and value
- google-sheets·write `Vendor Renewals`
28 contracts parsed
- 4 renew within 60 days
- $310k total annual commitment
- 2 contracts missing a stated term
Deliver reports where people look for them
Whatever an agent produces - a cleaned export, a monthly report, a scraped dataset - lands in the right Drive folder automatically.
On the 1st, generate the monthly report and file it in Drive.
- clickhouse·query last month's usage
- code·render report as PDF
- google-drive·upload to `Reports/2025`
March report filed
- Uploaded to `Reports/2025/March.pdf`
- Shared with the leadership group
Triggers
How a Google Drive workflow starts
Google Drive does not emit event triggers yet. Workflows that use it start by hand, on a schedule, or from a signed webhook.
Manual
Run it from the app with an optional JSON payload. Every workflow supports this.
Schedule
A cron expression or a plain sentence such as every weekday at 9am. Times are UTC.
Signed webhook
A public URL per workflow. Requests are signed with HMAC-SHA256 and expire after five minutes.
Works with
Google Drive works with the rest of your stack
One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox.
Templates
Ready-to-run Google Drive workflows
Copy the prompt, connect your tools, and start a run.
FAQ
Questions, answered
Put an agent on Google Drive.
Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook.