Google Workspace
Give your agents full access to Gmail.
Agents read the inbox, follow threads, draft replies in your voice, apply labels, and send when you tell them to. Put one on a schedule and the inbox is triaged before you open it.
5,000 free credits to start.
Agent reach
Gmail 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 Gmail
Helios searches the Gmail API v1 at run time. The agent finds the endpoint the task needs and calls it.
- Search Gmail's entire API surface at run time and call any endpoint your scopes allow.
- Search and read messages and threads with Gmail's full query syntax.
- Compose drafts, reply in thread, and send when the task calls for it.
- Apply and manage labels, archive, and mark read to shape the inbox.
- Read attachments into the sandbox and analyze them with code.
- Combine with a CRM so every reply carries account context.
Examples
Tasks you can hand to a Gmail agent
Triage the inbox before you open it
A morning agent reads what arrived overnight, labels it, drafts replies to the easy ones, and hands you a short list of what needs a human.
Every morning, triage overnight mail: label it, draft the easy replies, list what needs me.
- gmail·search `newer_than:1d -in:chats`
- gmail·apply labels by topic
- gmail·create 4 draft replies
- slack·DM me the needs-a-human list
31 messages triaged
- 4 drafts ready to review and send
- 22 labeled and archived
- 5 flagged for you, ranked by urgency
Turn inbound interest into CRM records
When a prospect writes in, the agent enriches the sender, creates or updates the CRM record, and files the thread against it.
For inbound sales mail, enrich the sender and create the CRM record.
- gmail·search label:inbound-sales is:unread
- apollo·enrich sender by email domain
- attio·upsert person and company records
- gmail·label thread `crm-synced`
6 inbound leads captured
- 6 companies enriched with size, industry, and funding
- 2 matched existing accounts and were merged
- Owners assigned by territory
Chase the threads that went quiet
The agent finds conversations that stalled after your last message and drafts a follow-up that references what was actually discussed.
Find threads where I sent the last message 5+ days ago and draft a follow-up.
- gmail·search sent threads with no reply
- gmail·read each thread for context
- gmail·draft 7 follow-ups in thread
7 follow-ups drafted
- Each references the last concrete next step
- 3 include the pricing page they asked for
- All waiting in Drafts for your review
Extract data from attachments
Invoices, reports, and spreadsheets land in the inbox. The agent opens them in its sandbox, pulls the numbers, and writes them where you keep them.
Pull totals from vendor invoices in my inbox into the finance sheet.
- gmail·fetch attachments from label:invoices
- code·parse 9 PDFs and extract totals
- google-sheets·append rows to Vendor Spend
9 invoices processed
- $41,208 total added for March
- 1 invoice flagged: amount differs from the PO
Triggers
How a Gmail workflow starts
Gmail 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
Gmail 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.
FAQ
Questions, answered
Put an agent on Gmail.
Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook.