Integration

Connect Gmail to Polaris

The honest version: Gmail is in the catalog, the Google sign-in flow has not shipped, and the product says pending rather than pretending.

What connecting buys

Gmail sits in the Polaris connection catalog as an OAuth connection, meaning it is authorized by signing in with Google rather than by pasting a token. That flow is not live yet, so Gmail stays pending on a worker and no credential is stored. Workers can be hired with Gmail on their list today, and the writing they do lands in Docs until the flow ships.

Auth mode: Google OAuth
Status: Pending, flow not shipped
Credential stored: None

Why this page starts with a limitation

Three connections in the Polaris catalog authorize through Google rather than through a pasted token: Gmail, Drive and Calendar. Google sign-in is a different mechanism from the token flow that powers the other ten, and it arrives with the worker execution runtime rather than ahead of it.

Until then, the product tells you the truth in the connect panel: the connection is pending, and nothing is faked. No placeholder credential is stored, no worker claims to have read your mail, and the connection badge on the worker card stays honest about the state it is in.

We would rather publish this page saying so than publish a page describing a mailbox integration you cannot have this afternoon.

What the Gmail connection covers

The catalog entry describes Gmail as reading and sending email. That is the intended surface of the connection, and it is roadmap rather than a shipped capability.

Reading
A support or sales worker briefed on a mailbox can work from what actually arrived rather than from a summary somebody typed into a task.
Drafting and sending
Reply drafts are the obvious first job, and the interesting question is where the human sits in the loop when the medium is email rather than a task comment.
Authorization scope
Google's own consent screen defines what an OAuth grant covers. When the flow ships, that screen is where the boundary is set and displayed.

Email work you can run today, without the connection

Two of the three reasons people ask for Gmail have answers already.

Works now

A worker drafts the email as a versioned doc, you copy it out and send it
Follow-up tracking as real tasks with owners and due dates
Slack connected instead, where a lot of the same signal already lives
Delivery arrives as a comment you can edit before anything goes out

Waits for the flow

A worker reading an inbox directly
Sending from your address
Triage that starts the moment a message lands
Threading a reply into an existing conversation

Workers that will want this connection

Hire an AI support specialist

Hand it the backlog on Friday and read eighteen drafted replies, sorted by severity, before you send a single one.

Hire an AI SDR

It does the twenty minutes of account research nobody has time for, and hands you a first line that could only have been written about that company.

Hire an AI executive assistant

Every commitment made in a meeting becomes a task with a name and a date on it before the next meeting starts.

A template library that stays in your team's voice

Templates go stale the same way documentation does, except a stale template gets sent to a customer.

Account briefs waiting for you before the first call

Ten minutes of research changes a first call. Nobody has ten minutes before a first call.

Every commitment from the meeting, owned and dated

The decisions were good. The problem is the eleven commitments that existed only in a document nobody reopened.

Questions people ask

+Can a Polaris worker read my Gmail today?

No. Gmail authorizes through Google sign-in and that flow has not shipped, so the connection stays pending and no credential exists to read anything with. The connect panel says exactly this rather than showing a connected state that would not be true.

+Why not accept a Google app password or an API key instead?

Because that would trade a proper consent screen for a long-lived credential with a scope nobody reviewed. The ten token connections in the catalog use tokens because their providers issue scoped ones. Google's answer is OAuth, so Gmail waits for OAuth.

+Should I still hire a worker with Gmail on its list?

If email is genuinely part of the role, yes. The worker is created and does everything else it was hired for, and the Gmail badge sits at pending. When a credential is stored for a connection, every worker in the organisation carrying it flips to connected at once.

+What is the closest thing that works now?

Drafting. A worker writes the email as a doc in Polaris, versioned and commentable, and delivers it as a comment on the task. You read it, edit it and send it yourself, which for outbound and support replies is where most teams want the human anyway.

Every tool a Polaris worker can be given

One catalog, one credential per tool per organisation, authorized by an owner and used by every worker who carries it.

Connect Google Calendar to Polaris

Scheduling is the one thing an assistant is asked for first, and it is the one connection still waiting on Google sign-in.

Connect Google Drive to Polaris

Files a worker produces already arrive as attachments on the task. Files your team already keeps in Drive are the part still waiting.