Duaer

Integrations

Set up Google OAuth2 generic credentials in Duaer

Store Google OAuth2 generic 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.

Set the Google OAuth2 scopes

The Duaer Google OAuth2 API is the generic Google OAuth credential, for calling Google APIs without a dedicated node from HTTP Request:

  1. Create the client as in Create an OAuth client and enable the APIs you call in Google Cloud.
  2. Put Client ID and Client Secret in the credential. Put space-separated full scope URLs in Scope, such as https://www.googleapis.com/auth/drive.readonly.
  3. Click Sign in with Google to finish.

For Gmail, Sheets, Drive, and other services with a dedicated node, use the matching single-service credential, which comes with the scopes preset.

Google OAuth2 API fields in Duaer

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

  • Client ID (required)
  • Client Secret (required, secret)
  • Scope

Duaer uses the OAuth2 Authorization Code grant for this type.

In the provider’s app settings, register the OAuth Redirect URL that the Duaer credential dialog shows (https://<your-duaer-host>/rest/oauth2-credential/callback). Then click Connect my account in Duaer and approve access.

Optional settings shared by every Duaer OAuth2 credential: Ignore SSL Issues (Insecure), Token Expired Status Code, Encrypted Tokens (JWE), JWKS URI. They are described under OAuth2 API.

Save the connection in Duaer

Open Credentials and create Google OAuth2 generic. 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.

Scopes and APIs to enable

A Duaer Google credential works only when the Google Cloud project has the right API enabled and the OAuth consent requested the right scopes.

  • Enable APIs: in the Google Cloud console, open APIs & Services > Library and enable the APIs your nodes use. Google Drive needs Google Drive API; Google Sheets needs Google Drive API and Google Sheets API; Gmail needs Gmail API.
  • Service-specific credentials, such as Google Drive OAuth2 API or Google Sheets OAuth2 API, request that service’s scopes for you.
  • The generic Google OAuth2 API credential needs space-separated scopes in Scope, such as https://www.googleapis.com/auth/drive https://www.googleapis.com/auth/spreadsheets.

After changing APIs or scopes, reconnect the credential in Duaer. A 401 unauthorized_client error usually means an API is not enabled or a scope is missing.

Questions

Do Google OAuth2 generic secret values appear in Duaer node parameters?

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

What usually stops a Google OAuth2 generic 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 OAuth2 generic expects, then confirm you can create credentials in that project.

In this section