Integrations
Set up Zammad credentials in Duaer
Store Zammad 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.
Choose a Zammad credential type
The Duaer Zammad node supports two credentials. Both take the Zammad address, such as https://support.example.com, in Base URL:
- Zammad Token Auth API: recommended. In Zammad, open your avatar > Profile > Token Access, create a token with the permissions you need, such as ticket.agent, and put it in Access Token. An admin must first enable API Token Access under Settings > System > API.
- Zammad Basic Auth API: put the Zammad account in Email and Password.
Turn on Ignore SSL Issues (Insecure) for a self-signed certificate.
Zammad Basic Auth API
In Duaer, choose Zammad Basic Auth API when you create a credential, then fill in these fields:
- Base URL (required)
- Email (required)
- Password (required, secret)
- Ignore SSL Issues (Insecure): Whether to connect even if SSL certificate validation is not possible. Default: off.
Duaer nodes that use it: Zammad.
Zammad Token Auth API
In Duaer, choose Zammad Token Auth API when you create a credential, then fill in these fields:
- Base URL (required)
- Access Token (required, secret)
- Ignore SSL Issues (Insecure): Whether to connect even if SSL certificate validation is not possible. Default: off.
Duaer nodes that use it: Zammad.
Save the connection in Duaer
Open Credentials and create Zammad. 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 Zammad secret values appear in Duaer node parameters?
No. In Duaer, Zammad secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a Zammad 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 Zammad 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.