Duaer

Integrations

Set up Twake credentials in Duaer

Store Twake 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 Twake credential type

Duaer has two Twake credentials:

  • Twake Cloud API: used by the Twake node. Add the Duaer app under Integrations in the Twake workspace and copy the Workspace Key.
  • Twake Server API: connects to a self-hosted Twake server. Host URL is the server address; Public ID and Private API Key come from the app credentials generated on the server.

Duaer has no dedicated node for this service. In the HTTP Request node, set Authentication to Predefined Credential Type and pick the Twake Server API credential. Refer to custom operations.

Twake Cloud API

In Duaer, choose Twake Cloud API when you create a credential, then fill in these fields:

  • Workspace Key (secret)

When you save, Duaer tests the connection with these values.

Duaer nodes that use it: Twake.

Twake Server API

In Duaer, choose Twake Server API when you create a credential, then fill in these fields:

  • Host URL
  • Public ID
  • Private API Key (secret)

Save the connection in Duaer

Open Credentials and create Twake. 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 Twake secret values appear in Duaer node parameters?

No. In Duaer, Twake secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.

What usually stops a Twake 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 Twake expects, then confirm you can create credentials in that project.

In this section