Integration
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.
What connecting buys
Connecting Notion gives a Polaris worker the pages you share with your Notion integration, and nothing else. With the credential stored, Polaris can import whole page trees into Docs, where child pages become nested doc pages and blocks keep their structure. Notion authorizes with an internal integration secret that Polaris verifies against the Notion API before storing it.
- Credential
- Internal integration secret
- Access model
- Per-page sharing, chosen by you
- Verified live
- Against the Notion API
The access model is the feature
Notion internal integrations do not get a workspace. They get whatever pages a human has shared with them, one at a time, through the same connection menu people use to share with colleagues. That makes Notion the easiest connection in the catalog to reason about: if you did not share it, no worker can read it.
It also makes the failure mode obvious. A worker that reports an empty Notion is almost never broken. Somebody created the integration and never shared a page with it.
Connecting Notion
- 1
Create an internal integration
In Notion's integrations settings, create one for your workspace. The secret it hands back starts with ntn_ or secret_.
- 2
Share the pages it should see
Open each page or database you want reachable and share it with the integration by name. Sharing a parent covers its children, which is usually the move.
- 3
Paste the secret into Polaris
An owner or admin pastes it into the connect panel. Polaris calls the Notion users endpoint with it and stores it only if Notion answers, showing you the integration or workspace name it got back.
Importing Notion into Polaris Docs
Beyond giving a worker read access, the stored Notion credential drives a real importer that moves content into the Polaris Docs tree.
Pick from what the integration can see
The importer lists the pages the integration has been granted, so the picker is a direct reflection of what you shared and a decent audit of it.
Page trees stay trees
Child pages come across as nested doc pages rather than being flattened into one long document, so a wiki keeps the shape people navigate by.
Blocks keep their kind
Headings, bullets, numbered lists, to-dos, quotes, code, callouts, dividers and toggles map onto the equivalent Polaris block, and nesting becomes indentation.
The result is a Polaris doc
Once imported, pages are versioned, commentable and reviewable like anything else in Docs, and a worker can draft into them.
Connect, or move
Both are reasonable. The wrong answer is deciding by accident.
Keep Notion, connect it
- The team's wiki habits stay where they are
- Workers read the prior art before they write anything
- You keep Notion's database views, which Polaris does not have
- Nothing to migrate, nothing to break
Import into Docs
- One place for docs and the tasks that reference them
- Versioned files, comments and file review on the same pages
- No per-seat bill for people who only read
- Workers can draft directly into the tree instead of pasting
Workers and work this connection feeds
Hire an AI technical writer
The documentation debt on your team is not a writing problem, it is a nobody-has-two-free-hours problem, and this is the worker for those two hours.
Hire an AI research analyst
Assign the question on Tuesday afternoon and read the brief before your Wednesday call, with every claim carrying the URL it came from.
Hire an AI ops coordinator
It writes down how your company does things, so the answer stops living in whichever colleague happens to be on holiday.
The README describes a version of the code that no longer exists
A monthly list of statements in your docs that the code no longer supports.
Getting a process out of one person's head
The process exists. It is in someone's habits and in six months of Slack threads. A worker interviews and reads until it is on a page.
Policy documents that stay current and show their changes
A policy nobody has updated in three years is worse than no policy. A worker keeps the drafts moving and the versions visible. A qualified adviser signs them off.
Questions people ask
+Can a Polaris worker see my whole Notion workspace?
No, and Notion is the reason rather than Polaris. An internal integration reaches only the pages a human has shared with it. Grant one page and that is the extent of it; grant a top-level page and its children come with it.
+What does the Notion import bring across?
Page trees, with child pages as nested doc pages and blocks mapped to their Polaris equivalents, including headings, bullets, to-dos, quotes, code, callouts and toggles. Nesting becomes indentation. Notion database views are not part of it.
+Is the import a one-way copy or a live sync?
It is an import. Pages are read from Notion and written into Polaris Docs as real docs, after which the two are independent. Editing the Polaris copy does not touch Notion and vice versa.
+Where does the integration secret go?
It is verified against the Notion API and then stored server-side against your organisation, one row for the whole org. Every worker carrying the Notion connection uses it, and revoking removes it for all of them at once.
+Can a worker write back into Notion?
Drafting in Polaris is what the product does today: a worker creates versioned docs in the Docs tree and delivers them as comments on the task. Treat Notion as the source you connect and Docs as the place work lands.
Related
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.
Hire an AI technical writer
The documentation debt on your team is not a writing problem, it is a nobody-has-two-free-hours problem, and this is the worker for those two hours.
The README describes a version of the code that no longer exists
A monthly list of statements in your docs that the code no longer supports.
A Notion alternative for teams tired of maintaining the database
Notion is the best place to write the plan. The question is who executes it once the page is written.
Replacing Notion and Slack
A stack with a writing tool and a talking tool, and no place where a piece of work has an owner and a date.
Notion pricing, checked August 2026
Two seat prices and a second meter for AI, which is the part that surprises people on renewal.
Connect Slack to Polaris
Six scopes, no access to direct messages, and a bot that only reads the channels somebody invited it into.