Skip to content
Merulan

Google Sheets setup

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

Connecting Google Sheets 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 Sheets refuses the connection until every item holds.

  • A Google account with read access to the spreadsheets a Pipeline reads.
  • A Workspace administrator who allows the connected application when the domain restricts third-party access.

Credentials

Google Sheets 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 Sheets requests the scopes the registry declares, and a grant missing one of them fails the first collection read.

  • https://www.googleapis.com/auth/spreadsheets.readonly

The grant is read-only, so a Google Sheets pipeline never writes a cell back.

Verification

Broker-registered application governs the Google Sheets connection. Google admits the broker-registered application, 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.