Skip to main content

​
Connect Notion

Notion is connected once for your whole organization, then deployed to the Chief Projects that should use it. Each deployment syncs the Notion pages and databases you pick into that Project’s knowledge, and gives Chief Notion tools in a task — searching, reading, and (with your approval) creating and editing pages, database rows, and comments.
Chief - the Notion section in Organization Integrations with Connect Notion workspace
Notion connects with an Access token from a connection you create on Notion’s Connections page and paste into Chief.
⚠️ Important: Only a Chief organization owner can manage the Notion integration. On a plan that does not include it, the Notion section is hidden and Organization › Integrations shows a Connect Chief to your team’s tools card with Notion and a See plans link. On the Notion side, a workspace admin needs to create the connection.

​
Steps

  1. Open Organization › Integrations, expand Notion, then expand How to connect Notion to see its six setup steps. Connect Notion workspace is a separate control that opens the form where you enter the token and select Projects.
  2. Open Notion’s Connections page. Follow the link in the panel and click New connection.
  3. Configure the connection. Name it Chief, choose Access token as the authentication method, select your workspace under Installable in, and click Create connection.
  4. Grant capabilities. On the connection’s Configuration tab, enable every required capability: Read content, Update content, Insert content, Read comments, Insert comments, and Read user information including email addresses.
  5. Copy the access token. In the Integration token section, copy the Access token and paste it into the Access token field in Chief. It’s verified against Notion and stored securely; it’s never shown again.
  6. Share pages with the connection. On the connection’s Content access tab, click Edit access and select the pages and databases you want available to Chief.
  7. Under Select projects, pick at least one Project, then click Connect. Chief shows a workspace card with its Bot user, Install type, and Deployed projects. Each Project starts with nothing synced until you choose its pages (next section).
  8. Choose which Notion operations run automatically. In a task, expand Using: and click the Notion icon to open Tools & integrations. Under Connected, click the Notion row, then turn on the operations you want Chief to run without asking each time.
⚠️ Important: All required capability boxes must be checked, or the integration won’t work. Notion can only see pages you explicitly share with the connection, so the page picker in Chief is limited to those.

​
Choose what each Project syncs

On the workspace card, click Edit pages for a deployed Project and choose a Sync mode:
  • Pick pages — choose specific pages and databases to index. Selecting a database syncs all of its rows.
  • Sync everything shared — index every Notion page and database shared with the connection.
Click Save selection. Saving replaces the current selection; if you removed pages, Chief asks Remove pages from the search index? before they stop being searchable. Use Add to project to deploy the workspace to another Project, and Undeploy (→ Undeploy from this project?) to remove it from one — that Project’s ingested pages are deleted from its knowledge base. Under Real-time updates, paste the Webhook URL into the Webhooks tab of your Notion connection, click Start verification, and copy the Verification token back into Notion so edits sync automatically, usually within a minute.

​
What Chief can do once connected

  • Search and read the synced pages and databases alongside your Library in every Project the workspace is deployed to.
  • Use Notion tools in a task — search Notion, read pages and comments, query databases, and create or update pages, rows, and comments. Writes show a confirmation card unless you turn on Create & edit pages, rows, and comments in Tools & integrations — see managing integration permissions.

​
Reconnect or disconnect

If Notion rejects the stored token, the Integrations header shows Reconnect required and the card explains that syncing is paused. Click Reconnect (or Update secret) and paste a new access token; a full re-sync of all deployed Projects is queued. To disconnect, click Remove on the workspace card and confirm Disconnect Notion?. Every page it ingested is deleted from the knowledge base in every Project it was deployed to; reconnecting re-ingests from scratch. To drop a single Project instead, use Undeploy — see connection status.

​
FAQ

Chief shows “Couldn’t verify the integration token with Notion. Confirm you pasted the internal integration token and that it has access to your workspace.” Confirm you copied the Access token from the connection’s Integration token section, that every required capability is enabled on its Configuration tab, and that the connection is installable in your workspace. Then try again.
Notion only exposes what you explicitly share. On the connection’s Content access tab, click Edit access and add the page or database. Then, in Chief, click Edit pages for the Project and add it to the selection — or switch that Project to Sync everything shared.
No. The connection belongs to your organization. Once an owner deploys the workspace to your Project, its synced pages and Notion tools are available to everyone in that Project. If a task shows Notion setup required, ask an organization owner to connect a workspace or deploy it to your Project.
It’s one of the required capabilities for the integration to function. All listed capabilities must be enabled in Notion or the connection won’t work.