Duaer

Integrations

Set up Npm credentials in Duaer

Store Npm 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 an npm access token

The Duaer Npm API credential:

  1. On npmjs.com, click your avatar, open Access Tokens, click Generate New Token, and prefer a Granular Access Token limited to the packages and orgs you need.
  2. Put it in Access Token. Keep Registry Url at the default https://registry.npmjs.org, or change it for a private registry.

Npm API fields in Duaer

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

  • Access Token (secret)
  • Registry Url: Default: https://registry.npmjs.org.

When you save, Duaer tests the connection with these values.

Duaer nodes that use it: Npm.

Save the connection in Duaer

Open Credentials and create Npm. 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. The matching node is under the related node.

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 Npm secret values appear in Duaer node parameters?

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

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

In this section