Duaer

Integrations

Set up Customer.io credentials in Duaer

Store Customer.io 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 Customer.io API credentials

The Duaer Customer.io API credential has one set of fields per API:

  • Tracking API: in Customer.io, open Settings > Account Settings > API Credentials and copy the Tracking Site ID and API Key into Tracking Site ID and Tracking API Key.
  • App API: create a key under App API Keys on the same page and put it in App API Key.
  • Set Region to EU region or Global region to match your account.
  • Webhook Signing Key is optional. Copy it from Integrations > Reporting Webhooks; Customer.io Trigger uses it to verify deliveries.

Customer.io API fields in Duaer

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

  • Tracking API Key (required, secret): Required for tracking API.
  • Region (required): Should be set based on your account region. Default: Global region. Options: EU region, Global region.
  • Tracking Site ID: Required for tracking API.
  • App API Key (secret): Required for App API.
  • Webhook Signing Key (secret): Used to verify webhook authenticity. Found in Customer.io under Integrations → Reporting Webhooks.

Duaer nodes that use it: Customer.io, Customer.io Trigger.

Save the connection in Duaer

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

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

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

In this section