Docs & storage
An AI agent that reads and files your Google Drive.
Connect Google Drive and an OpenHelm agent can watch the folders you choose, summarise new documents, assemble recurring reports from files spread across the Drive, and keep an index of what lives where, all on a schedule with a full run log.
What agents do with Google Drive. Recurring jobs, checked every run.
New-document summaries
When files land in a watched folder, produce a summary and email it to the people who need to know, with a link to the source.
Weekly report assembly
Pull the latest figures and updates from documents across Drive into a single weekly report, drafted and filed in the right folder.
Drive index and hygiene
Maintain a data table of key documents with owner, purpose and last-updated date, flagging stale or duplicate files.
Meeting-pack preparation
Before recurring meetings, gather the relevant documents, summarise changes since last time, and circulate a pre-read.
Connect Google Drive. A few minutes, once.
Connect Google Drive
Add Google Drive under Connections in the OpenHelm app and complete the hosted sign-in, or mint a connect link programmatically with POST /v1/connections/links.
Describe the job in plain English
Tell OpenHelm what you want done and how often. It drafts a plan with a schedule, the tools it will use, and a clear definition of done.
Approve the plan
No job fires until you have reviewed the plan. Set the autonomy level to control whether writes execute directly or queue for your approval.
It runs, self-checks and reports
Runs execute in isolated cloud sandboxes on schedule. An independent evaluator scores each run against the goal, and results arrive as logs, emails or data-table rows.
Or provision it over the API (see the Connections API docs):
curl https://api.openhelm.ai/v1/connections/links \
-H "Authorization: Bearer oh_live_..." \
-H "Content-Type: application/json" \
-d '{ "provider": "<provider id>", "name": "Google Drive" }'
# Returns a short-lived hosted link. Open it once to authorise,
# then poll GET /v1/connections until it shows as authenticated.Questions
Which files can the agent read?
Only what the connected Google account can see, and you can scope jobs to specific folders. Access is a standard revocable OAuth grant, and every file the agent touched is listed in the run log.
How does OpenHelm connect to Google Drive?
Through a scoped OAuth grant: you sign in to Google Drive once via a hosted connect flow, in the OpenHelm app or via a connect link minted with POST /v1/connections/links. OpenHelm stores no passwords, the grant is limited to what your jobs need, and you can revoke it at any time.
Can the jobs run on a schedule without me?
Yes, that is the point. Jobs run once, on an interval, or on a cron expression. A scheduler fires them, a watchdog times out anything hung, and a separate evaluator checks each run actually advanced the goal. You approve the plan before anything runs for the first time.
Is my Google Drive data safe?
Each run executes in an isolated cloud sandbox with scoped, revocable credentials and no middle-layer copy of your data. Every action is logged per run, results come back with evidence, and the agent never fabricates data it could not verify.
More in Docs & storage
Give your product a team that never clocks off.
Start free in the browser, or run it on your Mac with your own Claude Code or Codex plan.