Integrations
Set up Google Vertex AI credentials in Duaer
Store Google Vertex AI 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.
Google Vertex AI fields in Duaer
In Duaer, choose Google Vertex AI 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.
- Project (required): Select a Google Cloud project, or select Custom to enter a project ID. Default: Custom. Options: Custom.
- Project ID (required): Google Cloud project to use with Vertex AI. Shown when Project is Custom.
Duaer nodes that use it: Embeddings Google Vertex, Google Vertex Chat Model.
Save the connection in Duaer
Open Credentials and create Google Vertex AI. 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 Vertex AI secret values appear in Duaer node parameters?
No. In Duaer, Google Vertex AI secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a Google Vertex AI 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 Vertex AI 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.