Integrations
Set up NVIDIA Nemotron credentials in Duaer
Store NVIDIA Nemotron 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 an NVIDIA API key
The Duaer NVIDIA Nemotron credential works two ways, depending on where the model runs:
- NVIDIA cloud: sign in to build.nvidia.com, click Get API Key on any model page, and put the nvapi- key in API Key. Keep Base URL at the default https://integrate.api.nvidia.com/v1.
- Self-hosted NIM container: change Base URL to the container address, such as http://nim:8000/v1. Leave API Key empty when the container needs no authentication.
When Duaer runs in Docker, do not use localhost in Base URL. Use the NIM container’s service name or the host address.
NVIDIA Nemotron fields in Duaer
In Duaer, choose NVIDIA Nemotron when you create a credential, then fill in these fields:
- Base URL (required): Use the default for build.nvidia.com cloud, or change it to point at a self-hosted NIM container (e.g. http://localhost:8000/v1) Default: https://integrate.api.nvidia.com/v1.
- API Key (secret): Required for build.nvidia.com cloud. Leave blank for a self-hosted NIM that does not require authentication.
When you save, Duaer tests the connection with these values.
Duaer nodes that use it: NVIDIA Nemotron Embeddings, NVIDIA Nemotron Chat Model.
Save the connection in Duaer
Open Credentials and create NVIDIA Nemotron. 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 NVIDIA Nemotron secret values appear in Duaer node parameters?
No. In Duaer, NVIDIA Nemotron secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a NVIDIA Nemotron 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 NVIDIA Nemotron 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 digital organization. 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.