Skip to content
Merulan

Notion setup

What an operator supplies to connect the Notion Source, and the verification the provider requires.

Connecting Notion opens a Nango Connect session in the operator browser. Nango holds the credential, and Merulan holds a handle to it. An operator who holds the material below connects in one pass.

Prerequisites

Notion refuses the connection until every item holds.

  • A Notion workspace, and a member who may approve a connected application.
  • Page or database sharing with the connected application, because Notion grants reach per shared page.

Credentials

Notion stores the credential under the brokered custody the registry declares, so Merulan never shows the secret again once the connection is saved.

  • No secret is typed into Merulan. The Connect session returns a connection handle, and Merulan stores the handle rather than the token.

Scopes

Notion requests the scopes the registry declares, and a grant missing one of them fails the first collection read.

  • read_content
  • read_user_information

Both Notion scopes are read-only, and an unshared page stays invisible whatever the grant says.

Verification

Broker-registered application governs the Notion connection. Notion admits the broker-registered application, so no separate Merulan review stands before production use.

  • Connect and map a Source runs the connect ceremony and binds collections once the credential is in hand.
  • Integrations lists every Source that carries a setup page, with its ceremony and verification posture.