Skip to content

Notion

Live

BirchSeek creates one page per article as a row in the Notion database you point it at, writing the whole body as Notion-flavored markdown in a single call. Notion has no publish-to-web API, so the page stays inside your workspace for review.

What BirchSeek does

  • Creates the page in the data source you choose, with the article body sent as markdown - no block-tree conversion, no HTML
  • Writes the properties you map: title, slug, tags, publish date, meta description, and a Draft option if your board has a status column
  • Keys idempotency on a text property you nominate (BirchSeek ID), holding birchseek:<article id>, so a regenerated title or slug still finds the same page
  • Replaces the page body on a refresh run, so a regenerated article genuinely lands instead of quietly returning the stale page
  • Reports no published URL: what Notion returns is a private workspace link, and treating it as a live URL would poison the article's canonical

Setup

  1. Create an internal connection

    As a workspace owner, open the Notion developer portal at app.notion.com/developers/connections, choose Internal connections and create one for your workspace. On the Configuration tab, enable the Read content, Update content and Insert content capabilities, then copy the Installation access token.

    On screen: The connection's Configuration tab with the three content capabilities enabled and the Installation access token behind a Show button.

  2. Share the database with the connection

    A new connection has no page access at all. Open your blog database in Notion, click ••• in the top right, choose Connections, and add the connection you just made. Skip this and every call comes back as a 404 telling you the database is not shared.

    On screen: The database's ••• menu with Connections open and BirchSeek listed as a connected app.

  3. Add a BirchSeek ID column and connect

    Add a plain Text property to the database - call it BirchSeek ID - and leave it empty. Paste the token and the database URL into BirchSeek, pick the data source, and map the title, BirchSeek ID and any optional properties. The connection test reads the schema back and refuses to save a mapping that would fail later.

    On screen: The connector form with a data source picker and a property mapping table, each row showing the Notion property's name and type.

The BirchSeek ID column is not decoration: Notion's API exposes no exact-match filter on a title or URL property, so a plain text column is the only durable way to find the page we wrote last time.

Notion reference

Start with BirchSeek.

30 cited articles a month.

Start for $99/month