Duaer

Integrations

Set up Google Service Account credentials in Duaer

Store Google Service Account connection details in Duaer for digital-organization nodes to use at runtime. Secrets are protected by the instance encryption key and are not written into node parameters.

Create a service account key

The Duaer Google Service Account API credential signs in with a service account JSON key, with no browser consent:

  1. In the Google Cloud console, open IAM & Admin > Service Accounts and create a service account.
  2. Open it, then Keys > Add key > Create new key. Choose JSON and download the file.
  3. Put client_email from the JSON into Service Account Email, and the whole private_key value, including the BEGIN and END lines, into Private Key.
  4. Enable the APIs your nodes use in the same project.
  5. For Google Drive or Google Sheets, share the target file or folder with the service account email.

To act as a Google Workspace user, first authorize the service account client ID for the scopes you need under Security > API controls > Domain-wide delegation in the Workspace admin console. Then turn on Impersonate a User in the credential and fill in Email.

For the HTTP Request node, turn on Set up for use in HTTP Request node and list the scopes in Scope(s). Other nodes add their scopes automatically.

Google Service Account API fields in Duaer

In Duaer, choose Google Service Account API when you create a credential, then fill in these fields:

  • Region: The region where the Google Cloud service is located. This applies only to specific nodes, like the Google Vertex Chat Model. Default: Global (multi-region) - global. Options: Global (multi-region) - global, EU (multi-region) - eu, US (multi-region) - us, Africa (Johannesburg) - africa-south1, Asia Pacific (Changhua County) - asia-east1, Asia Pacific (Hong Kong) - asia-east2, and 38 more.
  • Service Account Email (required): The Google Service account similar to user-808@project.iam.gserviceaccount.com.
  • Private Key (required, secret): Enter the private key located in the JSON file downloaded from Google Cloud Console.
  • Impersonate a User: Default: off.
  • Email: The email address of the user for which the application is requesting delegated access. Shown when Impersonate a User is on.
  • Set up for use in HTTP Request node: Default: off.
  • Scope(s): You can find the scopes for services here (https://developers.google.com/identity/protocols/oauth2/scopes) Shown when Set up for use in HTTP Request node is on.

Duaer nodes that use it: Evaluation Trigger, Evaluation, Google BigQuery, Google Books, Google Chat, Google Cloud Storage, Google Docs, Google Drive, Google Drive Trigger, Gmail, Gmail Trigger, Google Sheets, Google Sheets Trigger, Google Slides, Google Translate.

Save the connection in Duaer

Open Credentials and create Google Service Account. Fill in the key, OAuth, or server fields. After you save, digital-organization nodes reference this credential instead of putting the secret in a parameter.

Credential values are protected by the instance encryption key. If you change or lose that key, stored credentials cannot be decrypted. See the hosting notes on encryption keys.

Who can use this credential

Who can see or edit it follows projects and roles. Do not paste secrets into chat or variables. External vaults are covered under external secrets.

Questions

Do Google Service Account secret values appear in Duaer node parameters?

No. In Duaer, Google Service Account secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.

What usually stops a Google Service Account credential from saving in Duaer?

Wrong fields, an OAuth callback that does not match the instance URL, or a role that cannot create credentials. Check the fields Google Service Account expects, then confirm you can create credentials in that project.

In this section