Duaer

Integrations

Set up Intercom credentials in Duaer

Store Intercom 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 an Intercom access token

API Key in the Duaer Intercom API credential takes an app access token:

  1. In the Intercom Developer Hub, create an app for your workspace.
  2. Open the app’s Configure > Authentication, copy the Access token, and put it in API Key.

The Duaer Intercom node calls api.intercom.io in the US region. Workspaces hosted in the EU or Australia region fail.

Intercom API fields in Duaer

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

  • API Key (secret)

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

Duaer nodes that use it: Intercom.

Save the connection in Duaer

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

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

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

In this section