Skip to content
Help Center
Submit a request Sign in

Tags

Configure Zoho Desk authorization

Updated Monday, October 26, 2026 · Marc Staine

Zoho Desk configuration stores the connection to an existing Zoho OAuth application. Choose the correct region during initial authorization and verify the resulting organization before enabling use.

Applies to: Supportbench Core. Location: Settings → Integrations → Zoho Desk. Access and available controls depend on your role and account capabilities.

Before you begin

  • Confirm you can administer integrations and have access to the intended provider workspace.
  • Record the existing connection and routing choices. Use a representative test record before enabling broad synchronization.
  • Obtain credentials through your approved provider process; do not place secrets in articles, screenshots or support messages.

Configure and verify

  1. Open this integration from Settings → Integrations.
  2. Review the connection identity and enter only the provider details requested by the page.
  3. Choose the available synchronization, routing or activity options described below.
  4. Save settings and use the displayed verification action when available.
  5. Inspect one representative record on both sides and review the integration status before relying on automated processing.

Settings reference

Connection and operating controls

SettingWhat it controlsHow to choose
Client ID / Redirect URIApplication identity and the redirect configured in Zoho.Use the exact existing application details.
Data centerInitial region selection; the trusted regional endpoint becomes locked after connection.Match the Zoho organization’s region.
Client secret / Grant codeWrite-only secret and one-time authorization grant. Blank preserves stored values; explicit Clear controls remove configured values.Use a current grant and avoid clearing credentials during unrelated edits.
Exchange grant codeExchanges the supplied one-time grant for connection access.Check region, application and redirect details first.
Refresh access / Verify connectionRefreshes authorization or verifies the resulting connection.Review status after each action.
OAuth API domain / Desk API domain / Organization ID / Token expiryRead-only connection evidence.Confirm the intended organization and region.
ActivePauses/resumes the installed connection without removing configuration.Use this for an operational pause.
RemoveRemoves the connection.Read the confirmation and review dependent work first.

Behavior to know

  • Supported region choices include US, Europe, India, Australia, Japan, Canada, Saudi Arabia, Singapore, UAE, UK and China.
  • A duplicate-configuration warning can block settings and authorization actions until the configuration is reconciled.

Recommended use

  • Enable only the flows your support process needs and identify an owner for connection failures.
  • Test mappings and routing with representative records before broad use. Review existing data before a resynchronization or removal.

Worked example

  1. Obtain the existing Zoho OAuth application details.
  2. Choose its region and enter Client ID, Redirect URI, secret and current grant.
  3. Exchange the grant, verify the organization, then enable Active.

Troubleshooting

ProblemWhat to check
The item is missing from a picker.Check Active, division access, parent hierarchy, enabled modules, and the user’s role. Reopen the consuming form after saving.
The form rejects a save.Read the displayed validation message. Check required values, text limits and permitted scope; do not change unrelated settings to bypass validation.
An existing record still shows an old value.A configuration change and a record change are different operations. Inspect the record and relevant references before assuming the save failed.
  • Integrations → Use the data synchronization log
  • Organization → Configure agent roles and division access

Was this article helpful?