Integration
Notion integration
Last updated
Use Notion as your CMS, Mentionwell as your blog engine, and Super.so / Potion / Feather as your renderer. When direct Notion push ships, articles land in Notion as database rows so your team can review and edit collaboratively before flipping the Live toggle. Today you can already reach Notion via the signed-webhook adapter path.
How it works
- Create a Notion integration at
notion.so/my-integrations. Share the database with it. - Paste the integration token into Connect.
- Map properties: Title, Slug, Body (page content), Status, Featured Image, Excerpt, Tags.
- Pick render path. Super.so + a custom domain is the most common combo for marketing sites.
What gets written into Notion
- A new database row per article.
- Page content in Notion blocks (paragraphs, headings, lists, callouts, images).
- Featured image as a Files & media property (or external URL).
- Status property — “Drafted by Mentionwell” → “Approved” → “Live” (or whatever your status options are).
- JSON-LD as a hidden text property your renderer consumes.
Questions
How does Notion render as a public site?
Notion isn’t a public CMS by default. Pair it with Super.so, Potion, or Feather to get a public domain. Mentionwell writes into the Notion database; the rendering tool turns it into a website.
Why use Notion as a blog backend?
Notion is great for teams that want internal review + collaboration on every article before it goes live. Mentionwell pushes drafts in; your team comments and edits in Notion; the rendering tool publishes when you mark a post Live.
What about images?
Featured images are stored as Notion file properties (or external URLs to R2 mirrors, depending on your renderer’s preference).
Is Notion good for SEO?
On its own, no — but Super.so, Potion, and Feather all add the missing schema, sitemap, OG tags, and meta you need. Mentionwell ships the JSON-LD as a property so your renderer just consumes it.