Skip to content
Merulan

Dropbox setup

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

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

Dropbox refuses the connection until every item holds.

  • A Dropbox account, and a member who may approve a connected application.
  • A Dropbox folder an operator may nominate as the root a Pipeline reads.

Credentials

Dropbox 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

Dropbox carries no scope list in Merulan: the broker application in Nango Cloud holds the requested scopes for this Source.

Merulan declares no Dropbox scope for this Source, so a scope change is made in the broker and takes effect on the next grant.

Verification

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