Integrations
Set up Google credentials in Duaer
Store Google 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.
Get a Gemini API key
The Duaer Google Gemini(PaLM) Api credential uses an API key from Google AI Studio:
- Sign in to Google AI Studio, click Create API key, and pick a Google Cloud project.
- Copy the key. In Duaer, create a Google Gemini(PaLM) Api credential and paste it into API Key.
- Keep Host at the default https://generativelanguage.googleapis.com unless you use a proxy.
The Google Workspace Admin and YouTube credentials on this page use OAuth. To create the OAuth client, refer to Google OAuth2 single service credentials.
Google Workspace Admin OAuth2 API
In Duaer, choose Google Workspace Admin OAuth2 API when you create a credential, then fill in these fields:
- Client ID (required)
- Client Secret (required, secret)
- Custom Scopes: Define custom scopes. Default: off.
- Enabled Scopes: Scopes that should be enabled. Default: a preset value. Shown when Custom Scopes is on.
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.
By default, Duaer requests these scopes: https://www.googleapis.com/auth/admin.directory.group https://www.googleapis.com/auth/admin.directory.user https://www.googleapis.com/auth/admin.directory.domain.readonly https://www.googleapis.com/auth/admin.directory.userschema.readonly https://www.googleapis.com/auth/admin.directory.device.chromeos https://www.googleapis.com/auth/admin.directory.orgunit.readonly.
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.
Duaer nodes that use it: Google Workspace Admin.
YouTube OAuth2 API
In Duaer, choose YouTube OAuth2 API when you create a credential, then fill in these fields:
- Client ID (required)
- Client Secret (required, secret)
- Custom Scopes: Define custom scopes. Default: off.
- Enabled Scopes: Scopes that should be enabled. Default: a preset value. Shown when Custom Scopes is on.
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.
By default, Duaer requests these scopes: https://www.googleapis.com/auth/youtube https://www.googleapis.com/auth/youtubepartner https://www.googleapis.com/auth/youtube.force-ssl https://www.googleapis.com/auth/youtube.upload https://www.googleapis.com/auth/youtubepartner-channel-audit.
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.
Duaer nodes that use it: YouTube.
Google Gemini(PaLM) Api
In Duaer, choose Google Gemini(PaLM) Api when you create a credential, then fill in these fields:
- Host (required): Default: https://generativelanguage.googleapis.com.
- API Key (required, secret)
When you save, Duaer tests the connection with these values.
Duaer nodes that use it: Google Gemini, Embeddings Google Gemini, Google Gemini Chat Model.
Save the connection in Duaer
Open Credentials and create Google. 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 secret values appear in Duaer node parameters?
No. In Duaer, Google secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a Google 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 expects, then confirm you can create credentials in that project.
In this section
Built-in integrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Triggers start a workflow. Actions run a step after it has started.
IntegrationsRisks of community nodes in Duaer
Before you install a community node in Duaer, know the code comes from a source the instance admin trusts, and know what permissions it gets.
IntegrationsTroubleshoot community nodes in Duaer
When a Duaer community node will not install or run, check the version, permissions, and node docs, then the instance logs.
IntegrationsMake custom API calls for an app in Duaer
When a Duaer app node does not expose the API you need, use HTTP Request and reuse that app’s saved authentication.
IntegrationsIntegrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Community nodes are extra packages. Custom operations reuse saved authentication with HTTP Request.
CredentialsBuilt-in credentials in Duaer
Per-service credential notes for Duaer built-ins. The create flow is in the credentials overview; node docs link to the matching service page.
Create nodesCreate a custom node for Duaer
Write a node package for Duaer when built-in nodes and custom operations are not enough and you will reuse the step.