Meet the new Scripe, live on October 7.Register

Integration

Notion pages as knowledge, and as a destination.

Positioning documents and playbooks in Notion feed the knowledge base; new ideas and published posts can land back in a Notion database.

NotionScripe

Two directions, one connection.

Pages you pick flow into the knowledge base; what Scripe produces can flow back into a database.

Knowledge base

  • Pricing decisionSynced
  • Brand voice playbookSynced
  • Product pagesSynced

Pick the pages, keep them current.

Positioning documents, playbooks, product pages: choose them in Notion, and Scripe reads them into the knowledge base. A changed page updates its document, a removed page removes it. Every idea and draft cites the passage it draws on.

Content plan

  • Idea · Why our onboarding takes six days · Lea Brandt
  • Published · The three-line brief every B2B team should steal
  • Idea · What 40 discovery calls taught us · Marcus Feld

Ideas and posts, back in Notion.

Through webhooks and Zapier or n8n, a new idea or a published post writes a row into the Notion database your team plans in.

Evidence
Outlier · Lea Brandt, 6.4× her average
Knowledge base · the 14 Sep call, Granola
Positioning · marketing leads, 11-50-person B2B

Every draft names the page.

When an idea or draft draws on a Notion page, the card names it and the hover card quotes the passage.

What the Notion connection does.

What the connection reads, how current it stays, and how a draft cites it.

All integrations
  • You pick the pages

    Only the pages you select are read; nothing else in the workspace.

  • Kept in sync

    Changes update the document; removed pages remove it.

  • Cited, not summarised

    Ideas and drafts quote the passage, and the link opens the page.

Questions about Notion

Build pipeline one post at a time