Gmail
Connect Gmail and Maya works your inbox - reading, triaging and drafting. One scope, one connection, and every send waits for your click.
Cette page n'est pas encore disponible dans votre langue : voici la version anglaise.
Connect Gmail and Maya works your inbox - reading it, triaging it, and drafting the replies. Every send still waits for your click.
Maya is the only one of the ten agents who can reach your mail. That isn't a setting you trust us to honour - the email tools are only loaded into Maya's runtime, and only when a mailbox is connected. For Ashley, Blake or anyone else, those tools do not exist.
Maya drafts. You send.
There is no auto-send in Unyo, and there is no setting to turn one on. Every compose and every reply renders as an editable card, and the send fires on your click - never on the model's. The send tool is confirmation-gated by database config, not by prompt: if the model calls it, all it can produce is a card waiting for your click.
What connecting Gmail unlocks
Everything below is Maya. No other agent gains a single inbox capability from this connection.
Read and triage
- Ask for your inbox and get a rendered card, not a wall of numbered text.
- Filter to unread only.
- Open any message's full body.
- Set inbox preferences the backend honours: ignore newsletters by keyword, mark high-priority senders and domains, force a preferred reply tone.
Draft
- "Reply to the Uniqlo one" → a reply draft with the real recipient, the real
Re:subject and the real thread preserved. You pass the message id; the server looks up the sender, subject, thread and message id from your cached inbox. Maya cannot invent an address - if the id isn't real, the tool refuses rather than guessing. - "Reply to the top 3" → three drafts in one collapsible card, reviewed and sent individually.
- "Write to Jean about the Q2 report" → an editable compose card. If the ask is genuinely too vague, she asks one short question instead of drafting filler.
- Edit any field on the card - to, cc, bcc, subject, body. Your edits autosave after 1.5 seconds and survive a reload, a tab switch, or closing the browser.
- Change your mind - "make it shorter", "add Isadora in cc" - and Maya sees your current edited draft, not her original. Fields you didn't touch stay exactly as you left them.
Attach
- From Google Drive, through Google's own Picker (needs the separate Google Drive connection).
- From your Neural Core, by name.
- From your image library, by description.
- Or drag your own files onto the card.
- Up to 10 attachments per email.
Send
- One click. Double-tap it and it still only sends once - every confirmed draft carries a stable idempotency key, so a retry, a refresh or a resumed run cannot double-send.
- Your signature is injected server-side, in both HTML and plain text, and then frozen into the sent record - editing your signature later doesn't rewrite history.
- Want it to go later? Hit Schedule on the draft card and pick a time. It's interpreted as wall-clock time in your timezone and stored as a real UTC instant, so daylight saving can't move it.
Automatically, in the background
- Emails sent from Unyo are labelled in your real Gmail: Sent by Unyo on messages you send, and Answered by Unyo on the original when you reply (the reply also archives the original out of your inbox). Your mailbox stays honest about what came from where - in Gmail's own UI, on every device, whether or not you ever open Unyo again.
- The person you write to is saved as a contact in your Neural Core, so every agent knows who they are.
How much of your inbox Maya actually sees
Maya reads your latest ~10 messages per mailbox, cached for 5 minutes. She is not indexing your archive and she is not searching years of mail. If the thread you mean has scrolled past that window, open it in Gmail and tell her what it's about.
Connect Gmail
- Open Integrations from the sidebar (or go straight to
/integrations). - Find the Gmail card and click Connect.
- Sign in with your Google account.
- Review the permission screen and approve.
You'll land back where you started. If an agent hit the wall mid-conversation, the run picks itself back up - no retyping.
One Gmail account per user
Unyo stores one Gmail connection per account. You can connect Gmail and Outlook at the same time and pick a default - but not two Gmail addresses. When both are connected, each conversation locks to whichever mailbox it first used, with a lock icon in the mailbox pill. That's deliberate: it's what stops a reply going out from the wrong address halfway down a thread.
Permissions - what we ask for, and what we refused
Unyo requests one Gmail scope. Most tools in this category ask for three or four.
| What Google grants | What it lets Maya do |
|---|---|
gmail.modify | Read your inbox, compose, reply, send the drafts you approve, and manage the Sent by Unyo / Answered by Unyo labels. |
email, profile | Show you which Google account is connected, so you can tell at a glance. |
Scopes we deliberately do not request
| Scope | Why we don't ask |
|---|---|
mail.google.com | Full, unrestricted access to your entire Google Mail account - including permanent deletion. We dropped it outright. Maya has no way to permanently delete your mail. |
gmail.send | Redundant. gmail.modify already covers sending, and asking for both would be asking for more than we need. Removed in April 2026. |
That's not a rounding error. Unyo cut its Google footprint from 9 scopes to 5 across the whole product, and gmail.modify is now the only restricted scope we hold anywhere. Google is mid-verification and a CASA Tier 2 audit is in scope - an independent Tier 2 DAST (TAC Security, May 2026) returned 0 Critical, 0 High, 0 Medium.
Read the boundary, not the promise
"Your data is safe" is something anyone can type. "Maya is the only agent with your inbox, we hold one Gmail scope, and there is no code path that deletes your mail" is something you can check.
What Unyo does with your data
- Your token is encrypted at rest. Gmail access and refresh tokens are AES-256 encrypted via database-level functions - never written or read as a plain column. Verified at the cipher-byte level on 2026-07-16: 17 of 17 populated OAuth token columns are encrypted, zero plaintext tokens exist. The master key is unreachable by any client role.
- The token is never logged. Not in a console log, not in an error message, not in an HTTP response, not in a job payload. It's resolved transiently to make one call to Google, then dropped.
- No model is trained on your mail. Every model Unyo runs is on a no-training tier.
- Cached mail expires on a cron, not on a promise. A live job at 03:00 UTC daily deletes cached emails at 30 days and conversations at 90. Draft attachments you never send are swept at 04:00 UTC after 24 hours.
- Row-level security on everything. 109 of 109 public tables, 291 policies, verified live 2026-07-16. Your rows are reachable by your account and nothing else.
Full detail: Security and privacy.
Try these
Then edit the card, and press Send when you're happy with it.
Automations you can turn on
Both are off until you turn them on, and both draft - neither sends.
- Auto-Reply - when a new email arrives, Maya prepares a reply draft and notifies you. A missing settings row counts as off, not on.
- Daily Digest - a morning inbox summary at a time you choose (default 08:00): priority emails, newsletters, sent summary. Delivered as a notification, to Slack, or to Drive.
More in Automations.
Disconnecting and revoking - the honest version
In Unyo: open /integrations, find the Gmail card, click Disconnect. The connection row is deleted and Maya's email tools stop existing for your account immediately.
At Google: disconnecting in Unyo does not revoke Unyo's access at Google, and we won't pretend otherwise. Gmail, Drive and Calendar share a single Google grant, and Google's revoke endpoint kills the entire grant for every scope at once - calling it when you disconnect Gmail would silently break your Calendar and Drive too. So we don't.
To revoke at the source, go to myaccount.google.com/permissions and remove Unyo. That revokes everything Google-related in one action, which is exactly what you want when that's what you mean.
Deleting your Unyo account does revoke - there, killing the whole grant is the right behaviour. Account deletion purges roughly 80 tables atomically, revokes every provider that offers an API, and completes even if a provider is unreachable. See Your data and deletion.
Troubleshooting
"Reconnect from Integrations" instead of my emails. Google revoked the refresh token out of band - a password change, access removed from your Google account, or the token simply ageing out. Unyo detects this and marks the connection dead rather than quietly showing you an empty inbox. Reconnect from /integrations.
The Gmail card doesn't say Connected after I approved. Unyo only shows Connected when all three hold: the Gmail scope was granted, the connection is live, and your address came back verified. If you unticked a permission on Google's screen, reconnect and approve everything on it - Maya can't work with a partial grant.
Nothing happens when I click Connect. Allow pop-ups for the sign-in window, then try again.
Maya says she can't see an email I know is there. She reads the latest ~10 messages per mailbox. Older threads are outside her window.
Maya won't switch mailboxes mid-conversation. Correct, and deliberate. The conversation is locked to the mailbox it first used. Start a new conversation and it'll lock to the other one.
She wrote her name and title under the sign-off. She shouldn't - your signature is injected server-side on the way out. Click the signature preview on any draft card to edit it.
FAQ
Does Maya ever send an email without me?
No - and there is no toggle that would let her. Compose and reply both render an editable card, and the send only fires on your click. The send tool is confirmation-gated in the database - a model call to it can only ever produce a card, and the actual send runs from your click. This applies to background automations too: overnight triage prepares drafts and a summary, and every one of those drafts is still sitting there waiting for you in the morning.
Can I connect more than one Gmail account?
No. Unyo stores one Gmail connection per user. You can connect Gmail and Outlook simultaneously and choose your default mailbox - each conversation then locks to one of them so replies never leave from the wrong address. But two Gmail addresses on one Unyo account isn't supported.
Can the other agents read my inbox?
No. The email tools are mounted only for Maya, and only when a mailbox is connected. For every other agent they aren't restricted - they aren't there. If you ask Ashley to email someone, she hands the job to Maya, and Maya draws it up as a card you approve.
Can Maya delete my emails?
Not permanently - we never requested the scope permanent deletion requires. Day to day she reads, drafts, sends what you approve, and applies the Sent by Unyo / Answered by Unyo labels - replying archives the original out of your inbox, which is reversible in Gmail. And anything delete-shaped in Unyo is confirmation-gated in the database, so nothing is removed without your explicit approval.
Is my email used to train AI models?
No. Every model Unyo runs is on a no-training tier. On top of that, the triage path is built to keep most of your mail away from a model entirely: a free local pass - automated-sender patterns, your Neural Core contacts, urgency detection - resolves most emails with zero network calls. Only the genuinely ambiguous minority reaches a model, and only ever the sender name, the subject, and a 300-character preview.
What does connecting Gmail cost in credits?
Reading your inbox, opening a message, and drafting a reply are all zero-credit tools. You're billed on the real cost of the model that did the thinking - never per message. New accounts get 2 500 free credits, no card. See Credits and billing.