Integrations

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.

What connecting buys

Polaris connections are the tool access you give an AI worker. The catalog holds fourteen entries: Slack, Notion, Linear, GitHub, Gmail, Google Calendar, Google Drive, Figma, HubSpot, Stripe, Supabase, WhatsApp, Instagram and web search. Thirteen need a credential, which an owner or admin authorizes once for the whole organisation. Nine are checked live against the provider before anything is stored. Web search needs nothing.

Connections in the catalog: 14
Need a credential: 13 of 14
Verified live before storing: 9
Who can authorize: Owners and admins

What a connection actually is

A worker in Polaris is a member row, a set of instructions, a few skill files and a list of connections. The connection list is the part that decides what the worker can reach outside the workspace. Everything else is what it knows; connections are what it can touch.

The list is fixed. Fourteen tools, chosen because they are where small teams already keep their work, and no free-text field where somebody can paste an arbitrary endpoint. When the copilot interviews you about a new hire, the tool question offers names from this catalog and nothing else.

Two consequences follow. A worker cannot acquire access you did not grant, and the set of credentials your organisation holds is short enough to read in one screen.

The catalog

Auth mode and credential type come straight from the connection catalog in the product. Live check means Polaris calls the provider with the credential and refuses to store it if the provider says no.

Connection	Credential	Live check	What it covers
Slack	One-click OAuth, or a bot token	Yes	Channels the bot was invited to, and posting
Notion	Internal integration secret	Yes	Pages shared with the integration
Linear	Personal API key	Yes	Issues visible to the key's owner
GitHub	Fine-grained access token	Yes	Repos, issues and pull requests in the token's scope
Stripe	Restricted key	Yes	Payments and invoices at the key's scopes
Figma	Personal access token	Yes	Design files and comments
HubSpot	Private-app token	Yes	CRM contacts and deals
WhatsApp	Meta system-user token	Yes	Chats on the WhatsApp Business app
Instagram	Long-lived page token	Yes	Posts and engagement data
Supabase	Service-role or restricted key	No live check yet	A project database and its auth
Gmail	Google OAuth	Flow not live	Reading and drafting email
Google Drive	Google OAuth	Flow not live	Docs, sheets and files
Google Calendar	Google OAuth	Flow not live	Events and scheduling
Web search	None	Not applicable	Open web research inside every session

How authorizing works

The same four steps for every credentialled tool in the catalog.

1
Open the connection
Click a pending connection on a worker card, or open it from Configure. Members see the panel; only owners and admins get the input, and everyone else is told to ask one of them.
2
Hand over the credential
Paste the token, or for Slack click through the provider's own consent screen and copy nothing at all. The field is a password field and the value never lands in a form log.
3
Polaris calls the provider
For the nine connections with a live check, Polaris makes a real API call with the credential. A rejected token produces the provider's own error text and nothing is written.
4
Stored once, org-wide
The verified credential is stored server-side against your organisation, and every worker in the org carrying that connection flips from pending to connected in the same moment. Revoking deletes it and flips them all back.

What the credential can and cannot reach

Held server-side

One row per organisation per tool, written by the edge function that verified it
Read by the server when a worker uses the tool, never sent to the browser
Replaceable by pasting a new token over the old one
Deletable in one click, org-wide, by an owner or admin

Bounded by the provider, not by us

A worker sees exactly what the token sees, no more and no less
Scoping happens where you create the token, in the provider's own console
A read-only key stays read-only inside Polaris
Revoking at the provider kills the access even if the row still exists

Every connection page

Fourteen pages, one per tool, each with its own credential, its own security conversation and the worker roles that ask for it.

Connect Slack to Polaris

Six scopes, no access to direct messages, and a bot that only reads the channels somebody invited it into.

Connect Notion to Polaris

Notion decides what Polaris can see, page by page, because an internal integration only reaches what you explicitly share with it.

Connect Linear to Polaris

A Linear API key carries one person's visibility, so the account you make it on decides what every worker can see.

Connect GitHub to Polaris

Fine-grained tokens let you hand over three repositories instead of an account, which is the whole reason to use them here.

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

Connect Figma to Polaris

A Figma token belongs to a person, and Polaris shows you which person it verified, which is the detail worth checking before you store it.

Connect HubSpot to Polaris

Private-app tokens are scoped where you create them, which makes HubSpot one of the easier connections to grant narrowly.

Connect Stripe to Polaris

This is the one connection where the key you choose matters more than anything on this page.

Connect Supabase to Polaris

Supabase is the connection where a careless key choice does the most damage, and the only one Polaris cannot yet check for you.

Connect WhatsApp to Polaris

For a lot of companies WhatsApp is the support desk, the sales channel and the customer record, and none of it is written down anywhere else.

Connect Instagram to Polaris

Engagement data is the only honest input to a content calendar, and it is the input most calendars are written without.

Web search in Polaris

Nothing to authorize, nothing to store, and every query a worker runs appears in the activity feed while it works.

AI workers you can hire, brief and assign

Every role below is a teammate you hire in chat, brief with an editable skill file, and assign work to on the same board as your people.

How an AI worker gets tool access

The interesting part of tool access is not the list. It is where the credential lives and who can read it.

AI worker

The difference between an agent you prompt and an agent you assign work to.

Skill file

The capability an agent has, written down where a person can read and edit it.

What an AI worker actually does, department by department

Twelve functions, sixty recurring jobs, and the exact tool connection each one needs.

What an AI worker costs, and how the hours are counted

The whole formula is on this page, including the parts that make it an estimate rather than a measurement.

Questions people ask

+Can I connect a tool that is not in the Polaris catalog?

Not today. The catalog is a fixed list of fourteen and the hiring flow only offers names from it. When somebody asks for something outside the list, the copilot can search the MCP market to see what exists, but nothing outside the catalog can be authorized in the product.

+Who is allowed to authorize a connection?

Only the owner or an admin of the organisation. The check happens on the server, not in the interface, so a member who opens the panel is told to ask an owner rather than being shown a disabled input they could work around.

+Do I have to connect the same tool again for every new worker?

No. A credential belongs to the organisation, not to a worker. Authorize Slack once and every worker that carries the Slack connection, including ones hired months later, is connected the moment they are created.

+Can anyone read the token back out of Polaris?

The browser cannot. Credentials are written by an edge function into a table the client never selects from, and the interface only ever shows the label the provider returned, such as the workspace name or the account login. Reading it back would mean going through the server, which no product surface does.

+What happens to a worker when I revoke a connection?

The stored credential is deleted and every worker in the organisation carrying that connection returns to pending in the same action. The worker keeps its instructions and skill files, so re-authorizing later puts it straight back to work.

+Which connections are not fully live yet?

The three Google connections, Gmail, Drive and Calendar, are OAuth and that flow has not shipped, so they stay pending and store nothing. Supabase accepts and stores a key but has no live verification call yet, and the product labels it as unvalidated rather than pretending otherwise.