Duaer

Integrations

Set up Zoho credentials in Duaer

Store Zoho 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 Zoho API client

The Duaer Zoho OAuth2 API credential serves the Zoho CRM node:

  1. In the Zoho API Console of your account’s data center (such as api-console.zoho.com; api-console.zoho.com.cn for China), click Add Client and choose Server-based Applications.
  2. Set Authorized Redirect URIs to the Duaer OAuth Redirect URL, then put Client ID and Client Secret in the credential.
  3. Authorization URL: accounts.zoho.com.cn for the China data center, accounts.zoho.com for all others. Access Token URL: your account’s data center, US, EU, IN, AU, or CN.
  4. Click Connect my account.

With the wrong data center in Access Token URL, consent succeeds but the token exchange fails. If your account lives on zoho.eu, pick EU; on zoho.in, pick IN; and so on.

Zoho OAuth2 API fields in Duaer

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

  • Authorization URL (required): Default: https://accounts.zoho.com/oauth/v2/auth. Options: https://accounts.zoho.com/oauth/v2/auth, https://accounts.zoho.com.cn/oauth/v2/auth.
  • Access Token URL (required): Default: US - https://accounts.zoho.com/oauth/v2/token. Options: AU - https://accounts.zoho.com.au/oauth/v2/token, CN - https://accounts.zoho.com.cn/oauth/v2/token, EU - https://accounts.zoho.eu/oauth/v2/token, IN - https://accounts.zoho.in/oauth/v2/token, US - https://accounts.zoho.com/oauth/v2/token.
  • Client ID (required)
  • Client Secret (required, secret)

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.

By default, Duaer requests these scopes: ZohoCRM.modules.ALL ZohoCRM.settings.all ZohoCRM.users.all.

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: Zoho CRM.

Save the connection in Duaer

Open Credentials and create Zoho. 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.

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 Zoho secret values appear in Duaer node parameters?

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

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

In this section