Duaer

Integrations

Set up Copper credentials in Duaer

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

The Duaer Copper API credential:

  1. In Copper, open Settings > Integrations > API Keys, click Generate API Key, and put it in API Key.
  2. Email is the email of the user who generated the key; Copper requires them to match.

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

Copper API fields in Duaer

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

  • API Key (required, secret)
  • Email (required)

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

Duaer nodes that use it: Copper, Copper Trigger.

Save the connection in Duaer

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

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

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

In this section