Duaer

Integrations

Set up Wise credentials in Duaer

Store Wise 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 a Wise API token

The Duaer Wise API credential:

  1. In Wise, open Settings > Integrations and tools > API tokens, create a token, and put it in API Token. Choose Full access to make transfers.
  2. Set Environment to Live, or Test with a Wise sandbox account.
  3. To read statements or execute transfers, generate an RSA key pair, upload the public key under Manage public keys on the same page, and put the private key in Private Key (Optional) for Strong Customer Authentication (SCA).

Wise Trigger registers a webhook with the service, so Duaer must be reachable from the internet.

Wise API fields in Duaer

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

  • API Token (secret)
  • Environment: Default: Live. Options: Live, Test.
  • Private Key (Optional) (secret): Optional private key used for Strong Customer Authentication (SCA). Only needed to retrieve statements, and execute transfers.

Duaer nodes that use it: Wise, Wise Trigger.

Save the connection in Duaer

Open Credentials and create Wise. 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.

Strong customer authentication

When Duaer calls Wise and the response is HTTP 403 with an x-2fa-approval header, the Wise API credential must include a private key. Duaer signs that one-time token with RSA-SHA256 and retries with X-Signature and x-2fa-approval. The node reads Private Key (Optional) on that credential. The field says the key is needed to retrieve statements and to execute transfers. If the key is missing, the node error links to this section.

  1. Create an RSA key pair. Keep the private key private.
  2. Register the public key on the Wise account that issued the API token.
  3. In Duaer, open the Wise API credential and paste the private key into Private Key (Optional).
  4. Run the workflow again.

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 Wise secret values appear in Duaer node parameters?

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

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

When does Duaer ask for a Wise private key?

When Wise returns HTTP 403 with an x-2fa-approval header and the Wise API credential has no private key. Paste the private key into Private Key (Optional) on that credential. Duaer uses it to sign the one-time token.

In this section