Skip to content
Merulan

Attio setup

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

Connecting Attio 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

Attio refuses the connection until every item holds.

  • An Attio workspace, and a member who may approve a connected application.
  • A Merulan seat that may install a Source.

Credentials

Attio 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

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

  • record_permission:read
  • object_configuration:read
  • list_configuration:read
  • list_entry:read
  • comment:read
  • note:read

The connection facet declares no scope of its own. The list above is the read set the Attio adapter exercises, and the broker application grants it.

Verification

Broker-registered application governs the Attio connection. Attio 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.