Integrations
Set up RabbitMQ credentials in Duaer
Store RabbitMQ 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.
Connect to RabbitMQ
The Duaer RabbitMQ credential:
- Hostname and Port must be reachable from the Duaer server. The port is usually 5672 without encryption and 5671 with TLS.
- User, Password, and Vhost are an account and virtual host set up in RabbitMQ; Vhost defaults to /. On a hosted service such as CloudAMQP, take them from its AMQP URL.
- For TLS, turn on SSL. Passwordless is on by default and means client-certificate authentication, so fill in Client Certificate and Client Key; turn it off to use a user name and password over TLS. Add CA Certificates when the server certificate is not from a public CA.
RabbitMQ fields in Duaer
In Duaer, choose RabbitMQ when you create a credential, then fill in these fields:
- Hostname
- Port: Default: 5672.
- User
- Password (secret)
- Vhost: Default: /.
- SSL: Default: off.
- Passwordless: Whether to use passwordless connection with certificates (SASL mechanism EXTERNAL) Default: on. Shown when SSL is on.
- CA Certificates (secret): SSL CA Certificates to use. Shown when SSL is on.
- Client Certificate (secret): SSL Client Certificate to use. Shown when SSL is on.
- Client Key (secret): SSL Client Key to use. Shown when SSL is on.
- Passphrase (secret): SSL passphrase to use. Shown when SSL is on.
Duaer nodes that use it: RabbitMQ, RabbitMQ Trigger.
Save the connection in Duaer
Open Credentials and create RabbitMQ. 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 RabbitMQ secret values appear in Duaer node parameters?
No. In Duaer, RabbitMQ secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a RabbitMQ 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 RabbitMQ 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.