Notion
What connecting Notion does today: the connection only, with approval-gated page comments and appends built for outbound actions.
Connecting Notion links one Notion workspace to your nima workspace. That is all it does today: nima does not read, search or import your Notion content. The only other thing built on the connection is a pair of outbound actions that can comment on or append to a page, and both need a person's approval.
Connecting Notion: on for every workspace. Writing to Notion: not available yet. Nothing from Notion enters the pipeline, and nima writes nothing to Notion today (see Writing to Notion through outbound actions).
Connect Notion
A nima owner or admin connects Notion from Integrations, the home screen of the admin panel. Members cannot connect integrations. A nima workspace holds one Notion connection, so connecting again replaces the existing one.
Open Integrations and choose the Notion card, then start the connection. nima sends you to Notion's authorization screen.
On Notion's page picker, choose the Notion workspace and select the pages you want nima to reach. Notion has no scope list: access is exactly the pages you select, plus what the Notion integration itself is allowed to do.
Confirm. Notion returns you to Integrations, and the card shows the connected workspace. If Notion reports an error or no authorization code comes back, you return to Integrations with an error message and nothing is stored.
Notion's connection has no refresh token, and nima stores the access token encrypted. The sign-in link nima hands to Notion is valid for 10 minutes; if it expires, start the connection again.
What nima does with Notion today
Today nima does nothing with Notion content. It reads no pages or databases, imports nothing, and creates no signals from Notion. There is no Notion search tool in the MCP server and no Notion route in the REST API beyond connecting, checking status and disconnecting.
| Question | Answer |
|---|---|
| Do Notion pages become signals? | No. There is no webhook and no polling. |
| Can an agent or nima's Slack assistant search Notion? | No. No MCP tool or API route exposes Notion content. |
| Does the connection change anything in Notion? | Not by itself. Only an approved outbound action does. |
The Notion card on Integrations still describes search and reading. That description is out of date: neither is available.
To bring Notion material into nima, paste it into a signal or use a source that nima does ingest. See Integrations for the list.
Writing to Notion through outbound actions
Outbound dispatch has two Notion actions, notion_comment and notion_append, and a person approves every one of them. Nothing in nima proposes either action yet, so a connected workspace never sees a Notion approval card today.
Not available yet. The two Notion actions are built, but nothing in nima proposes them today, so turning on outbound dispatch for your workspace does not by itself write anything to Notion. For how a workspace turns dispatch on, see Outbound actions.
| Action | What it does | Approval |
|---|---|---|
notion_comment | Posts a comment on a page, or a reply in an existing discussion. | Always asks. A workspace policy cannot make it automatic, because nima treats every Notion page as possibly visible outside the company. |
notion_append | Appends blocks to the end of a page, up to 8,000 characters. | Always asks. A workspace policy cannot make it automatic, for the same reason. |
The rules that apply once an action is proposed:
- Every write ends with a footer,
nima, on behalf of <person>, followed by a short reference. The reference also stops the same write from being posted twice. - An action carries at most 10 citations. A citation from an agent run must point at a URL the run actually read, or at nima itself. Any other link gets the whole action refused.
- A comment can be up to 6,000 characters, which is what a Notion comment holds. An append can be up to 8,000 characters, which is what the approval card can show. Longer content is cut, with a visible marker.
- If Notion answers 401 or 403, nima fails that action without retrying. For the next 10 minutes it refuses new Notion writes, unless a Notion write succeeds before then.
- nima matches a Notion account to a member by exact email (case-insensitive) when the Notion integration is allowed to read user email addresses. An owner or admin can also link a Notion account to a member by hand. If neither applies, a mention is plain text and notifies no one. See People and identities.
For how approval works across every integration, see Outbound actions and the outbound tools.
Disconnect Notion
Disconnecting Notion deletes the connection on nima's side and does not revoke nima at Notion. An owner or admin disconnects Notion from the Notion card on Integrations, or calls DELETE /v1/integrations/notion from a signed-in session; API keys and OAuth tokens are rejected on this route.
After disconnecting, nima can no longer reach your Notion workspace. To remove the integration from Notion as well, open the Notion workspace's connection settings and remove nima there. Nothing in Notion is changed or deleted by disconnecting.
The enable and disable toggle on the card only changes a label. It shows the integration as paused and does not stop nima's access, so use disconnect to end access.