Integrations
Set up SMTP credentials in Duaer
Store SMTP 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.
Fill in your mail server
The Duaer SMTP credential takes the outgoing server your mail provider gives you:
- Port 465: keep SSL/TLS on (the default). Port 587: turn SSL/TLS off; the connection is then upgraded with STARTTLS.
- Gmail: set Host to smtp.gmail.com. With 2-Step Verification on, create an app password in your Google Account and use it as Password, not your sign-in password.
- QQ Mail and 163 Mail: turn on the SMTP service in the web mail settings and generate an authorization code; use that code as Password. Host is smtp.qq.com or smtp.163.com, port 465.
- Company mail or your own server: use the host, port, and encryption your admin gives you.
An authentication error usually means the sign-in password was used instead of an authorization code or app password, or SMTP is not enabled at the provider.
SMTP fields in Duaer
In Duaer, choose SMTP when you create a credential, then fill in these fields:
- User
- Password (secret)
- Host
- Port: Default: 465.
- SSL/TLS: Default: on.
- Disable STARTTLS: Default: off. Shown when SSL/TLS is off.
- Client Host Name: The hostname of the client, used for identifying to the server.
Save the connection in Duaer
Open Credentials and create SMTP. 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 SMTP secret values appear in Duaer node parameters?
No. In Duaer, SMTP secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a SMTP 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 SMTP 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.