Duaer

Integrations

Set up Chargebee credentials in Duaer

Store Chargebee 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 Chargebee API key

The Duaer Chargebee API credential:

  1. In Chargebee, open Settings > Configure Chargebee > API Keys, create a Full-Access key (Read-Only if you only read), and put it in Api Key.
  2. Account Name is the site name: for https://acme.chargebee.com, use acme. Test sites carry a -test suffix; include it.

Chargebee API fields in Duaer

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

  • Account Name
  • Api Key (secret)

Duaer nodes that use it: Chargebee.

Save the connection in Duaer

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

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

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

In this section