Duaer

Integrations

Set up Paddle credentials in Duaer

Store Paddle 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 Paddle Classic vendor credentials

The Duaer Paddle API credential calls the Paddle Classic API (vendors.paddle.com). Paddle Billing accounts do not have these credentials:

  1. In the Paddle Classic dashboard, open Developer Tools > Authentication, copy the Vendor ID, and generate an Auth Code.
  2. Put them in Vendor ID and Vendor Auth Code. For a sandbox account, turn on Use Sandbox Environment API.

Paddle API fields in Duaer

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

  • Vendor Auth Code
  • Vendor ID
  • Use Sandbox Environment API: Default: off.

Duaer nodes that use it: Paddle.

Save the connection in Duaer

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

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

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

In this section