Duaer

Integrations

Set up Zendesk credentials in Duaer

Store Zendesk 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.

Create a Zendesk API token

The Duaer Zendesk API credential:

  1. In the Zendesk Admin Center, open Apps and integrations > APIs, turn on token access, create an API token, and copy it.
  2. Subdomain is the part in <subdomain>.zendesk.com. Email is an agent’s email address. API Token is the token.

The node acts as the account behind that email, with the same permissions.

Zendesk API

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

  • Subdomain: The subdomain of your Zendesk work environment.
  • Email
  • API Token (secret)

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

Duaer nodes that use it: Zendesk, Zendesk Trigger.

Zendesk OAuth2 API

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

  • Client ID (required)
  • Client Secret (required, secret)
  • Subdomain (required): The subdomain of your Zendesk work environment.
  • Custom Scopes: Define custom scopes. Default: off.
  • Enabled Scopes: Scopes that should be enabled. Default: read write. Shown when Custom Scopes is on.

Duaer uses the OAuth2 Authorization Code grant for this type.

In the provider’s app settings, register the OAuth Redirect URL that the Duaer credential dialog shows (https://<your-duaer-host>/rest/oauth2-credential/callback). Then click Connect my account in Duaer and approve access.

Optional settings shared by every Duaer OAuth2 credential: Ignore SSL Issues (Insecure), Token Expired Status Code, Encrypted Tokens (JWE), JWKS URI. They are described under OAuth2 API.

Duaer nodes that use it: Zendesk, Zendesk Trigger.

Save the connection in Duaer

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

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

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

In this section