An AI teammate for the part of your job that still lives in your inbox.
Connect Gmail to an Oya AI employee and they can read, search, draft, and send mail using your account — with the same audit trail and skill stack they use elsewhere. No SMTP credentials, no shared inbox tools, no relays.
What it does
Read, search, and triage
Your AI employee reads new mail, searches threads by query or label, and surfaces what needs your attention. Pair it with a routine to get a daily inbox digest.
Draft and send on your behalf
Compose replies, send fresh messages, and add attachments — all from the agent. Drafts can be saved for human review or sent immediately depending on how you configure trust.
Multiple Gmail accounts per Oya account
Connect a personal inbox and a shared support inbox to the same employee, or split them across two employees. Each account is its own connection with its own scopes.
How to connect Gmail
- 1
Click Connect Gmail in your AI employee
Open the agent’s Channels & Apps page, click Gmail, and pick the Google account to connect. The popup is Google’s standard OAuth flow.
- 2
Approve the requested scopes
We request only what your employee needs — read, send, modify (for labels and drafts). You can review every scope before approving in Google’s consent screen.
- 3
Choose how aggressive your agent is
In the agent’s system prompt or via specific skills, decide whether the employee drafts and waits for approval, or sends directly. Both modes are first-class.
- 4
Connect a second account (optional)
Repeat for any additional inbox — personal, shared support, sales aliases. Each one gets its own connection and you can route work between them.
Detailed walkthrough with screenshots: Channels & Apps in the docs.
What it doesn’t do (yet)
We’d rather be upfront about the edges than promise things we don’t deliver.
- Gmail’s send-rate limits apply — your employee inherits whatever rate limit Google has for your account class.
- Group/aliased sender addresses (e.g. send-as) need to be set up in Gmail itself first; we use whichever sender Gmail allows.
- Calendar invitations sent via Gmail are best handled through the Google Calendar integration — we don’t generate ICS attachments here.
Frequently asked
What scopes does Oya request from Google?
Only what’s needed: gmail.readonly (or gmail.modify when drafts are enabled), gmail.send, and basic profile info. We do not request access to Drive, Calendar, or anything else from this connection — those are separate integrations with their own consent flows.
Will my AI employee read all of my email?
Only when the agent runs and the run involves email. We don’t do background scanning. Every read is tied to a run you (or a routine you set up) initiated, and shows up in your run history.
Can the agent send email without my approval?
Yes, if you configure it to. Most teams start with a "draft and notify" pattern — agent prepares the reply, you approve in Slack — and graduate to direct send for tasks where they trust it. Both are first-class.
Can I connect multiple Gmail accounts?
Yes. Click Connect Gmail again for each additional inbox. Each is its own connection with its own scopes, tokens, and audit log.
How do I disconnect?
From the agent’s Channels & Apps page, click Disconnect on the Gmail tile. We immediately revoke the OAuth tokens. You can also revoke from your Google Account → Security → Third-party apps for belt-and-braces.
Do you store my emails?
Only the emails your employee processed during a run are stored — in your run history, so you can audit what happened. We don’t bulk-import or index your inbox, and we don’t use your email to train any AI model.
A note on AI accuracy
Oya’s AI employees are powered by large language models and may produce inaccurate, incomplete, or out-of-date responses. They are tools to assist your work, not authoritative sources. Always verify important information — especially numbers, dates, names, and any business or financial action — before relying on AI-generated output. If your AI employee suggests a destructive action (deleting data, sending money, posting publicly), confirm it yourself before approving.
No model training
Your data is not used to train AI models. It’s used to do the work you asked for, then logged in your run history for your audit.
Full audit trail
Every AI employee action maps to a run in Oya. Inputs, outputs, tools used, cost — all visible and auditable.
Stop writing the same email three times a day.
Connect Gmail in 30 seconds. $10 in free credits to start.