Duaer

Integrations

Set up Wekan credentials in Duaer

Store Wekan 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 the Wekan credential

The Duaer Wekan API credential signs in with an account to get a session token:

  1. Put the Wekan account in Username and Password.
  2. Put the Wekan address, such as https://wekan.example.com, in URL.

When Duaer runs in Docker, do not use localhost for the host; use the service name or the host address.

Wekan API fields in Duaer

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

  • Username
  • Password (secret)
  • URL

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

Duaer nodes that use it: Wekan.

Save the connection in Duaer

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

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

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

In this section