Integrations
Set up IMAP credentials in Duaer
Store IMAP 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 IMAP credential lets Email Trigger (IMAP) read new mail:
- Port defaults to 993. Keep SSL/TLS on.
- Gmail: set Host to imap.gmail.com and use an app password as Password.
- QQ Mail and 163 Mail: turn on IMAP in the mail settings and use the authorization code as Password. Host is imap.qq.com or imap.163.com.
- Turn on Allow Self-Signed Certificates only for your own server with a self-signed certificate.
IMAP fields in Duaer
In Duaer, choose IMAP when you create a credential, then fill in these fields:
- User
- Password (secret)
- Host
- Port: Default: 993.
- SSL/TLS: Default: on.
- Allow Self-Signed Certificates: Whether to connect even if SSL certificate validation is not possible. Default: off.
Save the connection in Duaer
Open Credentials and create IMAP. 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.
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 IMAP secret values appear in Duaer node parameters?
No. In Duaer, IMAP secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a IMAP 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 IMAP 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.