Duaer

Integrations

Set up HighLevel credentials in Duaer

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

Choose a HighLevel credential type

The Duaer HighLevel node supports two credentials:

  • HighLevel OAuth2 API: create an app on the HighLevel Marketplace, set Redirect URL to the Duaer OAuth Redirect URL, and put Client ID and Client Secret in the credential. Fill in Scope as the dialog suggests: locations.readonly contacts.readonly contacts.write opportunities.readonly opportunities.write users.readonly, and tick the same scopes in the app. Click Connect my account and pick the sub-account.
  • HighLevel API: put the legacy API Key from the sub-account’s Settings > Business Profile. It targets the HighLevel v1 API and only serves the older HighLevel node version.

HighLevel API

In Duaer, choose HighLevel 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: HighLevel.

HighLevel OAuth2 API

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

  • Authorization URL (required): Default: White-Label. Options: White-Label, Standard.
  • Client ID (required)
  • Client Secret (required, secret)
  • Scope (required): Separate scopes by space, scopes needed for node: 'locations.readonly contacts.readonly contacts.write opportunities.readonly opportunities.write users.readonly'.

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: HighLevel.

Save the connection in Duaer

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

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

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

In this section