Integrations
Set up JWT Auth credentials in Duaer
Store JWT Auth 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 JWT key type
The Duaer JWT Auth credential serves the JWT node (sign and verify tokens) and JWT authentication in Webhook, Wait, and Respond to Webhook. Match Key Type and Algorithm:
- Passphrase: a shared secret in Secret, with Algorithm HS256, HS384, or HS512. Signer and verifier use the same secret; use at least 32 random characters.
- PEM Key: an asymmetric key pair, with an RS, ES, or PS algorithm. Signing needs Private Key; to verify only, Public Key is enough.
Algorithm must match the one the other side signs with, or verification fails.
JWT Auth fields in Duaer
In Duaer, choose JWT Auth when you create a credential, then fill in these fields:
- Key Type: Choose either the secret passphrase or PEM encoded public keys. Default: Passphrase. Options: Passphrase, PEM Key.
- Secret (secret): Shown when Key Type is Passphrase.
- Private Key (secret): Shown when Key Type is PEM Key.
- Public Key (secret): Shown when Key Type is PEM Key.
- Algorithm: Default: HS256. Options: HS256, HS384, HS512, RS256, RS384, RS512, and 7 more.
Duaer nodes that use it: JWT, Respond to Webhook, Wait, Webhook.
Save the connection in Duaer
Open Credentials and create JWT Auth. 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 JWT Auth secret values appear in Duaer node parameters?
No. In Duaer, JWT Auth secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a JWT Auth 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 JWT Auth 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.