Skip to content
Merulan

Google Drive setup

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

Connecting Google Drive 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

Google Drive refuses the connection until every item holds.

  • A Google account, and a Workspace administrator who allows the connected application when the domain restricts third-party access.
  • A Drive folder an operator may nominate as an approved root.
  • A deployment that carries the scope attestation setting, because an approved root is verified against it.

Credentials

Google Drive 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

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

  • https://www.googleapis.com/auth/drive.readonly
  • https://www.googleapis.com/auth/drive.file

Google treats the read-only Drive scope as restricted, so the grant is read-only and no pipeline writes back to Drive.

Verification

Broker-registered application governs the Google Drive connection. Google holds the broker-registered application to its restricted-scope review, and a Workspace administrator may still block it for the domain.

  • 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.