Integration

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.

What connecting buys

Google Calendar is an OAuth connection in the Polaris catalog, covering events and scheduling. Authorization happens through Google sign-in, and that flow has not shipped, so the connection stays pending on a worker and stores no credential. Time-bound work in Polaris runs on task due dates and the Focus lane's three horizons rather than on calendar events.

Auth mode: Google OAuth
Status: Pending, flow not shipped
Works today instead: Due dates and Focus horizons

Where time lives in Polaris right now

Polaris already has a model of time, and it is not a calendar. Focus is the home screen, and it sorts the non-negotiables across three horizons: today, this week, and the next thirty days. Tasks carry due dates and owners. That is the spine deadlines hang from.

A calendar answers a different question. It says when a specific hour is spoken for, which is what an executive assistant needs before it can propose anything. Until the Google flow ships, a worker cannot see that layer, and the connect panel says so.

What the Calendar connection covers

The catalog describes it as events and scheduling. Roadmap, not shipped.

Reading availability
Knowing which hours are already committed is the precondition for every scheduling task anybody would assign a worker.
Events
The meeting is where most follow-up work is generated, and the follow-ups are the part that reliably goes missing.
Consent at Google
When the flow ships, the boundary is whatever Google's consent screen grants, shown to the person authorizing it.

Running scheduling work without the connection

Less elegant, entirely functional.

1
Keep the commitment as a task
A meeting that matters becomes a task with a due date and an owner, which puts it in Focus where the team already looks.
2
Let the worker prepare, not book
Agendas, pre-reads and the briefing note are the valuable half of a meeting. A worker delivers those as docs regardless of whether it can see a calendar.
3
Capture the follow-ups where they were said
With Slack connected, the thread after a meeting becomes prefilled task suggestions in the Inbox, which is the failure mode calendars never fixed anyway.

Workers that will want this connection

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.

Hire an AI recruiter

Every candidate is scored against the same written rubric, and the rubric is a file your hiring manager wrote and can change.

Hire an AI project coordinator

The unglamorous half of running projects, done every week without anyone having to be the person who nags.

Interview scheduling, including the reschedules

Four calendars, two time zones, a candidate who can only do early mornings, and a panellist who declines twice. This is the job.

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.

Dependencies as dated items, not as things people said in a meeting

Two teams agree something in a call. Neither writes it down. Three weeks later each is waiting for the other. A worker makes the promise a tracked item.

Questions people ask

+Can a Polaris worker schedule meetings for me?

Not yet. Google Calendar authorizes through Google sign-in and that flow has not shipped, so no worker can read availability or create events. Scheduling-adjacent work such as agendas, pre-reads and follow-up capture does run today.

+How does Polaris handle deadlines without a calendar?

Through tasks and Focus. Every task carries an owner and a due date, and Focus arranges the non-negotiables across today, this week and the next thirty days. It is a commitment view rather than an hour-by-hour grid.

+Is interview scheduling possible with a recruiter worker?

Partly. A recruiter worker can screen candidates, prepare the interview pack and track each stage as tasks. Proposing and booking the slot itself needs calendar access, so a person does that step for now.

+Will connecting Calendar later require rehiring my workers?

No. Connections belong to the organisation, not to a worker. A worker already carrying the pending Calendar connection moves to connected the moment a credential exists, keeping its instructions, skill files and history.

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 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.

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.