Help center Core configuration Integrations & migrations Configure Zoho Desk authorization Updated Thursday, October 29, 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. Requires Administer all integrations. Before you begin You need Administer all integrations and authorization to connect the intended provider organization. Obtain credentials through your approved provider process; keep them out of screenshots and support messages.Confirm the existing Zoho organization’s actual Data center and approved OAuth application. A Grant code is a one-time authorization value exchanged for connection access; it is not your ordinary password or a reusable API key. Use the provider’s approved process to obtain it.Choose approved test records and people before sending messages, creating engineering work or making calls. Record the current connection identity and enabled options so the test has a clear expected result. Configure and verify Open Settings → Integrations → Zoho Desk. Review duplicate-configuration warnings before editing; settings and authorization are blocked until all duplicate rows are removed.For a valid single configuration, verify Client ID, Redirect URI and Data center against the approved provider application. The trusted regional endpoint locks after connection.Enter Client secret and a current one-time Grant code as needed. Each blank input preserves its stored value; each has a separate explicit Clear checkbox.Choose Save Changes for configuration edits. Use Exchange grant code to exchange the current grant, then inspect the resulting connection details.Use Refresh access or Verify connection for the specific authorization/check needed. Review OAuth API domain, Desk API domain, Organization ID and Token expiry.Set Active and Save Changes when ready. Verify the supported downstream workflow independently of connection health.If removal is required, read the Remove confirmation: it removes every configuration row, including duplicates. Plan the reconnection and dependent work before confirming. Settings reference Connection and operating controlsSettingWhat it controlsHow to chooseClient 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 every saved configuration row, including duplicate rows. Review the confirmation and dependent work.Read the confirmation and review dependent work first. Behavior to knowSupported region choices include US, Europe, India, Australia, Japan, Canada, Saudi Arabia, Singapore, UAE, UK and China.Duplicate configuration blocks settings and authorization until all duplicate rows are removed. Remove deletes every configuration row; review the consequence before confirming. Recommended use Confirm region, application and organization together before enabling Active. Matching only the application name is not enough to establish the intended customer environment.Leave write-only credential inputs blank when you intend to preserve them. Use an explicit Clear checkbox only for a planned credential change, then verify the resulting connection.Use Active for a planned operational pause. Remove affects every configuration row, including duplicates, and requires a deliberate recovery plan for dependent work. This page has no customer-field mapping or full-resynchronization controls. Worked example: connect the correct regional support organization Illustrative situation: a B2B team’s approved Zoho Desk organization is hosted in its European data center. The administrator has confirmed that region from the actual provider account and has the matching application Client ID and Redirect URI. Do not infer region from the customer’s address or copy this example as a universal default.Open Zoho Desk settings and inspect any duplicate-configuration warning before editing. For a valid single configuration, select the matching Data center, enter the approved application values and use the current Client secret and one-time Grant code. Keep those values out of the operational test record.Save Changes and Exchange grant code. Inspect OAuth API domain, Desk API domain, Organization ID and Token expiry. Have the account owner confirm that the returned organization and domains correspond to the intended regional organization before enabling Active.If the returned identity or region is unexpected, stop operational use and resolve the mismatch. The trusted region becomes locked after connection; do not assume it can simply be edited afterward. Review the reconnection and downstream consequences before any Remove action.If exchange fails, check the current grant, application/redirect details and region. A used or invalid one-time grant is not repaired by repeatedly resubmitting it. Obtain a new value through the approved provider process when necessary, then verify connection evidence again.Once the correct connection is verified, save Active and test the specific supported downstream workflow your team intends to use. Confirm its actual result separately; healthy authorization does not prove a ticket, message or other operational task has run.Document the organization identity, region, responsible owner and non-secret verification result. On later unrelated edits, blank credential fields preserve saved values; do not select Clear just because the secret is not displayed. Troubleshooting ProblemWhat to checkSettings and authorization actions are blockedCheck the duplicate-row warning. All duplicate rows must be removed before normal configuration; the Remove action warns that it removes every row.Grant exchange failsVerify the current one-time grant, application/redirect details and selected region. Do not assume a previously used grant remains valid.Credentials appear blank after reopeningThey are write-only; blank input preserves stored values. Use the distinct Clear checkbox only when intentional.Data center cannot be changedThe trusted regional endpoint locks after connection. Review the intended organization and recovery before removing configuration.A valid connection did not perform a customer workflowVerify Active and the specific supported downstream surface; authorization alone is not proof of operational processing. Related configuration Integrations → Use the data synchronization logOrganization → Configure agent roles and division accessManage companies and contacts with the full support relationship in view Was this article helpful? Yes No Thank you for your feedback.