Duaer

Integrations

Set up Segment credentials in Duaer

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

The Duaer Segment API credential needs one key:

  1. In Segment, open the source to write to (an HTTP API or Node.js source) and copy the Write Key under Settings > API Keys.
  2. Put it in Write Key and save.

Segment API fields in Duaer

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

  • Write Key (secret)

Duaer nodes that use it: Segment.

Save the connection in Duaer

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

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

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

In this section