NotionFlare

Keep edits in sync

How NotionFlare keeps your site and Knowledge Base current after every Notion edit.

guidespropsUpdated Aug 14, 2026

When you edit a page in Notion, NotionFlare updates your public site and Knowledge Base so community /ask can use the new text — without manual export.

Loading diagram…

After you connect

  1. Finish OAuth under Dashboard → Notion.
  2. Confirm sync status in the dashboard (connection / verification should succeed).
  3. Create or edit a page in the linked Blog Posts database — Status, Title, Slug, and body all matter.

If sync is missing or failing, edits stay in Notion until you fix the connection or run a manual sync.

What triggers an update

Typical triggers:

  • Create or update a page in the linked database
  • Change Status (for example private → public)
  • Change Title or body content

Slug note: After the first sync, NotionFlare freezes the post URL slug so title edits do not break links. Changing the Notion Slug property alone does not rewrite the published URL. To change a slug, use the dashboard. Deleting a Notion page or setting Status to archived removes it from the site and from /ask.

Site vs Knowledge Base

  • Public site — Pages with Status public (blog, docs hub, site search).
  • Knowledge Base — Private + public posts for your Ask (plan post cap). Delete/archive removes them from /ask.
  • Official demo `/ask` — Only public docs (and creator public posts opted into platform discovery).

Private pages stay in your Knowledge Base; they do not appear on the open web.

How long does sync take?

Usually seconds to a couple of minutes after Notion notifies NotionFlare. If nothing moves, use Sync now under Dashboard → Notion, then re-check the site or Try /ask.

Sync now vs automatic sync

Automatic sync runs when Notion sends a change (create/update/Status). Sync now is a manual catch-up when webhooks were missed or you just reconnected. Prefer fixing the connection first; Sync now does not replace sharing the database with the integration.

Troubleshooting

Last updated on