Skip to content
Merulan

Gusto setup

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

Connecting Gusto redirects the operator to the provider and returns with a grant. Merulan holds the credential directly. An operator who holds the material below connects in one pass.

Prerequisites

Gusto refuses the connection until every item holds.

  • A Gusto company account, and an administrator who may approve a connected application.
  • Payroll history in Gusto for the periods a Pipeline reads.

Credentials

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

  • No secret is typed into Merulan. The browser grant returns an access token and a refresh token, and Merulan seals both.

Scopes

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

  • companies:read
  • employees:read
  • payrolls:read

Every Gusto scope is read-only, so no pipeline writes payroll back.

Verification

Provider app review governs the Gusto connection. Gusto reviews the registered application before it leaves the developer environment, so a production company connects only after that review clears.

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