Duaer

Integrations

Set up Rocket credentials in Duaer

Store Rocket 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 a Rocket.Chat personal access token

The Duaer Rocket API credential:

  1. In Rocket.Chat, click your avatar, open Profile > Personal Access Tokens, enter a name, and click Add. An admin must allow this permission first.
  2. Put the Token from the dialog in Auth Key and the User ID in User ID. Put the server address, such as https://duaer.rocket.chat, in Domain.

Rocket API fields in Duaer

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

  • User ID
  • Auth Key (secret)
  • Domain

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

Duaer nodes that use it: RocketChat.

Save the connection in Duaer

Open Credentials and create Rocket. 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 Rocket secret values appear in Duaer node parameters?

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

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

In this section