Integrations
Set up MQTT credentials in Duaer
Store MQTT 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 an MQTT broker
The Duaer MQTT credential:
- Match Protocol and Port: usually 1883 for Mqtt, 8883 for Mqtts, and the broker’s WebSocket port for Ws.
- Fill in Username and Password when the broker requires sign-in.
- Client ID is generated when empty. To receive QoS 1 and 2 messages sent while offline, turn Clean Session off and set a fixed Client ID; otherwise every connection counts as a new client.
- For certificate authentication, turn on SSL, keep Passwordless on, and fill in Client Certificate and Client Key. Add CA Certificates for a private CA.
MQTT fields in Duaer
In Duaer, choose MQTT when you create a credential, then fill in these fields:
- Protocol: Default: Mqtt. Options: Mqtt, Mqtts, Ws.
- Host
- Port: Default: 1883.
- Username
- Password (secret)
- Clean Session: Whether to use clean session - set to false to receive QoS 1 and 2 messages while offline. Default: on.
- Client ID: Client ID. If left empty, one is autogenerated for you.
- 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.
- Reject Unauthorized Certificate: Whether to validate Certificate. Default: off. 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.
Duaer nodes that use it: MQTT, MQTT Trigger.
Save the connection in Duaer
Open Credentials and create MQTT. 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 MQTT secret values appear in Duaer node parameters?
No. In Duaer, MQTT secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a MQTT 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 MQTT 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.