Connect Gmail to SAGARIS, one mailbox at a time
Yes. SAGARIS connects a Gmail mailbox over OAuth and syncs it into the unified inbox, where mail sits on the same deal timeline as calls and texts. Replies go out from the address you connected rather than from a shared SAGARIS address, so the person you are emailing sees you. The grant is per mailbox, not a domain-wide delegation.
Connected. You can connect a Gmail mailbox over OAuth today. Mail syncs into the SAGARIS inbox and SAGARIS sends from your address rather than from one of ours.
Last verified October 5, 2026. All integrations
What moves, and which way
OAuth, per mailbox. Tokens are encrypted before they are stored.
- Into SAGARIS
- The mail in the connected mailbox syncs into the unified SAGARIS inbox and lands on the deal timeline beside the calls, texts and meetings for the same contact. That is what lets a reply be read in the context of the call that preceded it, and what lets the AI draft a follow-up that refers to something the buyer actually said rather than to a template.
- Back into Gmail
- Mail SAGARIS sends goes out from the mailbox you connected, under your own address and your own domain's reputation. Labels are applied back in Gmail where the grant covers it, so the state you see in SAGARIS and the state you see in Gmail are the same state rather than two copies drifting apart.
- The boundary
- The grant covers reading, labelling and sending for the one mailbox you connect. It is not a domain-wide delegation, so connecting a team means each person connects their own mailbox, and revoking is done per mailbox in your own Google account security settings. Sending from a connected mailbox is also a different path from sending on the SAGARIS mail infrastructure, with a different reputation attached, so a high-volume outbound programme is a separate conversation rather than an extension of this one.
Connecting a mailbox
- 01
Open the mailbox connection step
Connecting the business mailbox is part of setting up a SAGARIS workspace rather than an optional extra, because a revenue record with no mail in it is missing most of the conversation.
- 02
Authorize with Google
You are sent to Google, you sign in as the owner of that mailbox, and you grant read, label and send for it. The grant is yours and you can revoke it from your own Google account security settings at any time.
- 03
The mailbox syncs onto the timeline
Mail arrives in the unified inbox and is attached to the contact and deal it belongs to, so a thread and the calls around it read as one history.
- 04
Each teammate connects their own
There is no domain-wide grant, so a second rep connects a second mailbox. That is more clicks and a cleaner consent story: nobody is granted access to a colleague's mail by an administrator's decision.
How we checked
The Gmail OAuth client resolves from GMAIL_OAUTH_CLIENT_ID and falls back to GOOGLE_CALENDAR_CLIENT_ID, so the Google credentials probe covers it. On the production service at app.sagaris.ai, GET /api/calendar/google/connect answered 401 Unauthorized, which is past the 503 not-configured guard, proving a real client id is set. The paired control was /api/calendar/microsoft/connect in the same process on the same day, which answered 503 with a not-configured message. The scope behaviour is read from src/lib/mailbox/gmail-oauth.ts rather than from documentation. This status was first measured on September 18, 2026 and re-probed on October 5, 2026 with the same result.
Verified October 5, 2026. If this is out of date or wrong, email founders@sagaris.ai and we will correct it and move the date.
Gmail and SAGARIS, the questions people actually ask
- MOST ASKED
Yes. Replies and follow-ups go out from the mailbox you connected, under your own address, rather than from a shared SAGARIS address. The recipient sees you.
No. The grant is per mailbox and each person connects their own. No administrator can grant SAGARIS access to a colleague's mail on their behalf, and each person can revoke their own grant from their Google account security settings.
Reading, labelling and sending for the one mailbox you connect. Label actions only run when the granted scopes cover them, which the product checks rather than assumes.
Encrypted before they are stored, and scoped to your workspace. Revoking the grant in Google cuts access immediately regardless of what we hold.
That is a different question from connecting a mailbox, and worth treating as one. Mail sent from a connected mailbox carries your own domain's reputation. Volume sending belongs on dedicated infrastructure with its own warmup and deliverability handling, so raise it with us rather than assuming the mailbox connection scales into it.
Next door
What this connects to
- The unified inboxWhat the mailbox looks like once mail, SMS and calls share one timeline.
- The Google Calendar connectionThe other half of the Google grant, and what the booking flow writes against.
- Outlook and Microsoft 365The answer is different, and you need it before a trial rather than during one.