Skip to main content
The Notion integration makes your team’s notes, wikis and trackers available in client work. Ask what was decided in the Contoso kickoff notes, pull rows from a risk register database, or add a finished summary to a project page. Hebno cites each page and row it reads, and writes to Notion only after you confirm.

At a glance

Before you start

You need:
  • A Notion workspace where you can open the pages you want to use.
  • Permission to share those pages with an integration. In Notion, that means full access to the page or database.
  • If your Notion workspace restricts connections, a workspace owner may need to approve the Hebno integration.
Notion does not use scope strings. Access is limited to the pages and databases you pick on Notion’s consent screen, and to the capabilities the Hebno integration declares:
Hebno can read only the pages and databases you share during connection. A page nested under a shared page is included. To add more later, select Reconnect and tick the extra pages, or use Add connections from a page’s menu in Notion.

Connect Notion

1

Check the integration is allowed

An owner or admin controls this under Admin → Connectors → Catalogue. If Notion shows Blocked, ask an admin to set it to Allow.
2

Start the connection

Open Settings → Connections, find Notion under Knowledge and select Connect. You can also select Connect on the prompt that appears in chat the first time you use Notion.
3

Choose what to share

Sign in to Notion, pick the workspace, tick the pages and databases Hebno may use, and select Allow access. Hebno returns you to the app with a Notion connected message.
The row shows Connected with your workspace name. Admins can revoke any member’s connection from Admin → Connectors → Connections.

What Hebno reads

The workspaces your organisation selects are stored in the knowledge index and searched by meaning, with permissions inherited from Notion. Opening a specific page reads it as it is now, with your connection. Only the excerpts a reply used are stored with the conversation as its sources. Search in Notion matches titles, not the text inside pages. Hebno searches titles first, then opens the matching pages and reads their bodies, so name the page, database or client in your request. To filter a database, Hebno queries it by property, for example status or owner.
Excerpts a reply uses become part of the conversation. Anyone you share the conversation with can read them, even if they cannot open the page in Notion.

What Hebno writes

Every write appears first as a confirmation card. You can change any field before you select Confirm.
Confirmation card for Notion with editable fields

A Notion change pending confirmation. Nothing is written until you confirm.

Hebno adds content at the end of a page. It never rewrites or deletes existing blocks, archives pages, changes database properties or schemas, or changes sharing. Linking marks which Notion page or database belongs to a project, so you can ask about “the project wiki” or “the risk register” without naming it.
  1. Open the project and select Brain.
  2. Under Linked records, select Link record, then Notion.
  3. Search by title and select the page or database.
The page or database must be one you shared during connection. In chats tagged to the project, Hebno starts with the linked page or database, and write cards default to it as the parent. See Linked records.

Use Notion in chat

  • Attach: open the + menu, choose Sources → Notion, and pick a page or a database row. Or type / and choose Notion.
  • Ask: name the page, database or client in your request. For example:
    Summarise the Contoso Retail kickoff notes in Notion and list the decisions and the open questions.
    Which high-severity items are still open in the Contoso risk register? Draft a risk slide from them.
    Add a page called Week 3 readout under the Contoso Retail project page with this summary.
  • Research runs show a Reviewing Notion step, with a chip for each page or row Hebno read.
  • Agents can read Notion on a schedule. Writes an agent proposes appear in agent approvals for review.

Troubleshooting