Google Workspace
Give your agents full access to Google Docs.
Agents draft, edit, and read documents where your team writes. Hand an agent a research task and it comes back with a real doc - sourced, structured, and shared with the people who need it.
5,000 free credits to start.
Agent reach
Google Docs API v1
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 Docs
Helios searches the Google Docs API v1 at run time. The agent finds the endpoint the task needs and calls it.
- Search the Docs API surface at run time and call any endpoint your scopes allow.
- Create documents and write structured content with headings, lists, and tables.
- Read existing documents as context for research, drafts, and summaries.
- Apply batch edits: insert, replace, and restructure sections.
- Combine with web search and scraping to draft from live sources.
- Save drafts to a Drive folder and share them with the right people.
Examples
Tasks you can hand to a Google Docs agent
Draft a research brief from live sources
Give the agent a topic. It searches the web, reads what it finds, and writes a sourced brief into a new document.
Research the SOC 2 audit process for a Series A startup and write me a brief.
- web·search and read 14 sources
- code·outline and cluster findings
- google-docs·create `SOC 2 Brief` with citations
- google-drive·share with the ops folder
`SOC 2 Brief` created
- 1,900 words across 5 sections
- Every claim linked to a source
- Timeline and cost table included
Turn a rough outline into a first draft
The agent reads your bullet points and your existing docs for voice, then writes a draft that already sounds like you.
Expand the outline in `Q2 Launch Plan` into a full draft in our voice.
- google-docs·read outline and 3 prior plans
- google-docs·write expanded draft in place
Draft expanded
- 6 sections written from 22 bullets
- Matched the structure of prior launch plans
- Open questions left as inline comments
Summarize a long document for the team
The agent reads a dense doc, writes a one-page summary with the decisions and owners, and posts it where people will see it.
Summarize the architecture RFC into one page and post it to Slack.
- google-docs·read `Storage RFC` (11k words)
- google-docs·create one-page summary doc
- slack·post summary to #engineering
RFC summarized
- 3 proposals compared on cost and latency
- Recommendation and its two risks
- 4 open questions with owners
Keep a living document current
A scheduled agent refreshes the sections that go stale - metrics, roadmap status, open risks - and leaves the prose alone.
Every Monday, refresh the metrics and status sections of the board update.
- postgres·query current metrics
- github·read roadmap milestone progress
- google-docs·replace metrics and status sections
Board update refreshed
- Metrics table rebuilt from the warehouse
- Roadmap status pulled from 4 milestones
- Narrative sections left untouched
Triggers
How a Google Docs workflow starts
Google Docs 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 Docs 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 Docs workflows
Copy the prompt, connect your tools, and start a run.
FAQ
Questions, answered
Put an agent on Google Docs.
Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook.