Integrations
Set up TOTP credentials in Duaer
Store TOTP 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.
Get the TOTP secret
The Duaer TOTP API credential stores the seed of a two-factor setup; the TOTP node turns it into a 6-digit code:
- Turn on two-factor authentication in the service you sign in to. When the QR code appears, choose the option to show the key instead, copy the Base32 key such as BVDRSBXQB2ZEL5HE, and put it in Secret.
- Label is optional, in issuer:username form, such as GitHub:john-doe.
This secret is a full second sign-in factor. Use it only in digital organizations that really need to sign in unattended, and share the credential only with people who must have it.
TOTP API fields in Duaer
In Duaer, choose TOTP API when you create a credential, then fill in these fields:
- Secret (required, secret): Secret key encoded in the QR code during setup. Learn more (https://github.com/google/google-authenticator/wiki/Key-Uri-Format#secret).
- Label: Identifier for the TOTP account, in the issuer:username format. Learn more (https://github.com/google/google-authenticator/wiki/Key-Uri-Format#label).
Duaer nodes that use it: TOTP.
Save the connection in Duaer
Open Credentials and create TOTP. 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 TOTP secret values appear in Duaer node parameters?
No. In Duaer, TOTP secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a TOTP 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 TOTP 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 digital organization. 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.