Make a Notion knowledge base answerable
Notion is where a great many teams keep everything they know, and its search is the reason nobody finds any of it.
- No script needed
- About two minutes
- One field
A Notion page cannot host a script, so the assistant lives on a site you control and reads your Notion pages through the Notion API — published or private, they only need to be shared with the integration.
The route through your admin
- Knowledge
- Connect Notion
The snippet lands in the pages you share with the integration.
Connect the workspace, pick the pages
Connect Notion from the Knowledge page (on Growth and above) and share the pages you want answerable. They arrive through Notion's API as structured content, are indexed like any other source, and every answer cites the page it came from.
- Share exactly what you choose
- The connector sees only pages shared with it — the rest of the workspace stays invisible.
- Ask, do not navigate
- A question in plain language beats guessing which nested page holds the answer.
- Cites the page
- The reader gets the answer and a link into the wiki itself.
- Uploads still work
- Exports and PDFs can be added as documents alongside, or instead of, the connector.
A Notion page cannot host a script, so the assistant lives on a site you control and reads your Notion pages through the Notion API — published or private, they only need to be shared with the integration.
Public docs or internal wiki
The same approach serves both. A published help centre built in Notion becomes a customer-facing assistant; an internal handbook becomes something the team can ask instead of interrupting each other over.
Why Notion needs the connector, not the crawler
A published Notion page is rendered in the browser — fetched raw, it is a script shell, which is why generic crawlers see nothing there. Matter Chat reads Notion through its API instead: connect the workspace and pages arrive as structured blocks, headings and tables intact, no rendering involved.
Find out what the wiki never covered
The ranked list of unanswered questions is a direct read on what your organisation has not actually written down. Most teams find that two or three important processes exist only in someone's memory.
Checking it actually worked
There is no snippet to verify here, so the check is on the knowledge instead: confirm the crawl found your pages, then test the boundary.
- 1Hard refresh the page — the launcher appears bottom-right.
- 2Ask it something your site answers, and check the reply cites a page.
- 3Ask it something your site does not cover, and check it declines.
- 4Open Conversations in the dashboard; both should be there.
On a different stack?
The snippet is the same everywhere. Only the place you paste it changes.
What Notion users ask
Short answers. If yours is not here, the assistant on this page will try it — and tell you honestly if it cannot.
Why can't you just crawl my public Notion site?
Published Notion pages are drawn in the browser by JavaScript, so a fetch-based crawler receives an empty shell — ours and search engines alike. The Notion connector reads the same pages through Notion's API instead, which is more reliable and also works for private pages.
Does it work with private Notion pages?
Yes — the connector (Growth and above) reads through Notion's API, so a page only needs to be shared with the integration, not published to the web. Nothing has to be public to be answerable; on any plan, exports can be uploaded as documents instead.
How current are the answers?
It re-crawls on a schedule and re-indexes what changed, so edits to a published Notion page reach the assistant without any manual step.
Can I use this for an internal team wiki?
Yes, and it is one of the better uses. Deploy it on an internal surface, domain-locked to it, so the answers stay where they belong.
From the blog
All posts- BuildingDomain locks and why “works on localhost” isn’t enoughDomain allowlists exist so your bot answers only where you installed it. Testing on localhost proves the script loads; it does not prove production embeds are locked down.Read
- EvaluatingThe best AI chatbot for a Webflow site, compared honestly (2026)Matter Chat, Social Intents, Ultimo Bots, Chatling, WeblyChat and Chatbase on a Webflow site: Apps marketplace or custom code, the paid-site-plan gate, CMS coverage, citations, handoff and pricing. Checked on the vendors' own pages.Read
- BuildingWhat to index first when your site is a messStart with the pages that already resolve real support questions. Noise, archives, and unfinished docs can wait — indexing them first makes answers worse.Read
Answer honestly. Capture the rest.
Point Matter Chat at your site and see what it can — and can't — answer. It's honest about both.
No credit card. 2 minute setup.
Every answer cites the source it came from. When there isn't one, it says so — and hands the visitor to you.
Installs on the tools you already run.