Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.mantrixflow.com/llms.txt

Use this file to discover all available pages before exploring further.

Notion is useful when operational planning, editorial calendars, release checklists, or internal knowledge bases need to be pulled into structured reporting tables.

​
Current connection form

The current Notion source form asks for:
  • Connection Name
  • Integration Token
  • The token field expects a Notion integration token, usually starting with secret_....
  • The integration must be explicitly shared to the databases or pages you want to read.

​
Good first use cases

  • planning database exports for reporting
  • release checklist visibility outside Notion
  • operational page snapshots in a SQL destination

​
Before you connect

  • Create a Notion integration with the access level your workspace allows.
  • Share the target databases or pages with that integration before testing.
  • Start with databases or pages so you can confirm the visible content quickly.

​
Step by step

  1. Open Connections and click + New Connection.
  2. Keep the role set to Source and choose Notion.
  3. Fill the form with real values, for example:
    • Connection Name: Product Wiki
    • Integration Token: secret_...
  4. Click Test Connection and save only after the test succeeds.
  5. Create a pipeline and start with one high-value resource so validation stays simple.

​
Common resources in the current source preview

  • databases
  • pages
  • users
The current Notion preview is intentionally narrow. It does not document extra unpublished resource variants beyond these three surfaces.

​
Real-world example

An operations team syncs a Notion release checklist database into PostgreSQL so engineering managers can combine planning status with GitHub and deployment reporting.

​
Troubleshooting

  • If the test succeeds but the expected content is missing, confirm that the integration was shared to the specific pages or databases.
  • Notion resources are often better validated with a manual full-sync run first.
  • Start with one workspace area before expanding the connection scope.