Zoho Desk

Zoho Desk is a cloud-based customer support and help desk platform for managing tickets, contacts, and agent workflows across channels. The Zoho Desk REST API exposes this data — tickets, threads, contacts, accounts, agents, tasks, and more — for programmatic access. Nexla connects to the Zoho Desk API using OAuth 2.0 so you can ingest support data into your pipelines and push new tickets, comments, and contacts back into Zoho Desk.

Power end-to-end data operations for your Zoho Desk API with Nexla. Our bi-directional Zoho Desk connector is purpose-built for Zoho Desk, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Zoho Desk or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Zoho Desk workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Zoho Desk credential, you need to register an OAuth 2.0 client in the Zoho API console to obtain a Client ID and Client Secret. Nexla uses the OAuth 2.0 authorization code flow to authenticate with the Zoho Desk API, so you will authorize access to your Zoho Desk portal when you create the credential in Nexla.

To register your OAuth client, follow these steps:

1. Sign in to the Zoho API console using your Zoho account credentials.

2. Click GET STARTED (or Add Client if you already have registered clients), then select the Server-based Applications client type.

3. Enter the required client details:

   • Client Name — a name for your application (for example, "Nexla Integration").
   • Homepage URL — the URL of your application's home page.
   • Authorized Redirect URI — the redirect URI that Zoho will return the authorization response to. Use the OAuth callback URL provided by Nexla when configuring the credential.

4. Click CREATE. Zoho generates a Client ID and Client Secret for your application.

5. Copy the Client ID and Client Secret and store them securely, as you will enter them when creating your Nexla credential.

6. Confirm the OAuth scopes your integration needs. Zoho Desk scopes take the form Desk.<resource>.<operation> (for example, Desk.tickets.READ or Desk.tickets.ALL). Provide the scopes that cover the endpoints you plan to use, as a space-separated list, when you create the credential.

Zoho Desk data centers are region-specific. The authorization and token endpoints default to accounts.zoho.com; if your Zoho account is hosted in another region (for example, EU, IN, or AU), adjust the authorization and token URLs to the corresponding data center domain. For full details on OAuth registration, scopes, and data centers, see the Zoho Desk API Documentation and the Zoho OAuth 2.0 setup guide.

Authenticate

Credentials required

An OAuth authentication flow where users must authorize an application to access their data

Field	Required	Secret	Description
Authorization URL	No	No	The URL endpoint where users authenticate and authorize access
Client ID	Yes	Yes	A unique public identifier assigned to your application
Access Scope	No	No	A space-separated list of permissions your application requests
Token URL	No	No	The URL endpoint where authorization codes are exchanged for access tokens
Client Secret	No	Yes	A private key used to authenticate your application when requesting tokens

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter the Authorization URL and Token URL for your Zoho data center. These default to the standard Zoho Accounts endpoints (https://accounts.zoho.com/oauth/v2/auth and https://accounts.zoho.com/oauth/v2/token); adjust the domain if your portal is hosted in another region.

4. Enter the Client ID and Client Secret you obtained when registering your OAuth client in Prerequisites.

5. Enter the Access Scope as a space-separated list of the Zoho Desk scopes required for your use case (for example, Desk.tickets.READ Desk.contacts.READ).

6. Complete the OAuth authorization flow when prompted, signing in to Zoho and granting the requested access to your Zoho Desk portal.

   Keep your Client Secret confidential. If it is compromised, regenerate the client credentials in the Zoho API console and update the Nexla credential. Access is limited to the scopes you authorize, so request only the scopes your pipelines need.

   For details on OAuth registration, scopes, and available endpoints, see the Zoho Desk API Documentation.

7. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Zoho Desk connector tile, then select the credential that will be used to connect to Zoho Desk, and click Next; or, create a new Zoho Desk credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Zoho Desk endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

List List Users

Retrieve list_users. This endpoint template fetches the list of users from your Zoho Desk portal.

• This endpoint reads from the list/users API path and returns records under the response's data array. Nexla automatically handles pagination to retrieve subsequent pages of results.

For detailed information about response fields and available parameters, see the Zoho Desk API Documentation.

List List User Groups

Retrieve list_user_groups. This endpoint template fetches the list of user groups from your Zoho Desk portal.

• This endpoint reads from the list/user/groups API path and returns records under the response's data array. Nexla automatically handles pagination to retrieve subsequent pages of results.

For detailed information about response fields and available parameters, see the Zoho Desk API Documentation.

List List Contacts

Retrieve list_contacts. This endpoint template fetches the list of contacts from your Zoho Desk portal.

• This endpoint reads from the list/contacts API path and returns records under the response's data array. Nexla automatically handles pagination to retrieve subsequent pages of results.

For detailed information about response fields and available parameters, see the Zoho Desk API Documentation.

List List Accounts

Retrieve list_accounts. This endpoint template fetches the list of accounts from your Zoho Desk portal.

• This endpoint reads from the list/accounts API path and returns records under the response's data array. Nexla automatically handles pagination to retrieve subsequent pages of results.

For detailed information about response fields and available parameters, see the Zoho Desk API Documentation.

List List Agents

Retrieve list_agents. This endpoint template fetches the list of agents from your Zoho Desk portal.

• This endpoint reads from the list/agents API path and returns records under the response's data array. Nexla automatically handles pagination to retrieve subsequent pages of results.

For detailed information about response fields and available parameters, see the Zoho Desk API Documentation.

List List Departments

Retrieve list_departments. This endpoint template fetches the list of departments from your Zoho Desk portal.

• This endpoint reads from the list/departments API path and returns records under the response's data array. Nexla automatically handles pagination to retrieve subsequent pages of results.

For detailed information about response fields and available parameters, see the Zoho Desk API Documentation.

List List Tickets

Retrieve list_tickets. This endpoint template fetches the list of tickets from your Zoho Desk portal.

• This endpoint reads from the list/tickets API path and returns records under the response's data array. Nexla automatically handles pagination to retrieve subsequent pages of results.

For detailed information about response fields and available parameters, see the Zoho Desk API Documentation.

List List All Threads

Retrieve list_all_threads. This endpoint template fetches the list of all threads from your Zoho Desk portal.

• This endpoint reads from the list/all/threads API path and returns records under the response's data array. Nexla automatically handles pagination to retrieve subsequent pages of results.

For detailed information about response fields and available parameters, see the Zoho Desk API Documentation.

List List Contracts

Retrieve list_contracts. This endpoint template fetches the list of contracts from your Zoho Desk portal.

• This endpoint reads from the list/contracts API path and returns records under the response's data array. Nexla automatically handles pagination to retrieve subsequent pages of results.

For detailed information about response fields and available parameters, see the Zoho Desk API Documentation.

List List Tasks

Retrieve list_tasks. This endpoint template fetches the list of tasks from your Zoho Desk portal.

• This endpoint reads from the list/tasks API path and returns records under the response's data array. Nexla automatically handles pagination to retrieve subsequent pages of results.

For detailed information about response fields and available parameters, see the Zoho Desk API Documentation.

List List Products

Retrieve list_products. This endpoint template fetches the list of products from your Zoho Desk portal.

• This endpoint reads from the list/products API path and returns records under the response's data array. Nexla automatically handles pagination to retrieve subsequent pages of results.

For detailed information about response fields and available parameters, see the Zoho Desk API Documentation.

List List Articles

Retrieve list_articles. This endpoint template fetches the list of knowledge base articles from your Zoho Desk portal.

• This endpoint reads from the list/articles API path and returns records under the response's data array.

For detailed information about response fields and available parameters, see the Zoho Desk API Documentation.

List List Events

Retrieve list_events. This endpoint template fetches the list of events from your Zoho Desk portal.

• This endpoint reads from the list/events API path and returns records under the response's data array. Nexla automatically handles pagination to retrieve subsequent pages of results.

For detailed information about response fields and available parameters, see the Zoho Desk API Documentation.

List List Attachments

Retrieve list_attachments. This endpoint template fetches the list of attachments from your Zoho Desk portal.

• This endpoint reads from the list/attachments API path and returns records under the response's data array. Nexla automatically handles pagination to retrieve subsequent pages of results.

For detailed information about response fields and available parameters, see the Zoho Desk API Documentation.

List List Calls

Retrieve list_calls. This endpoint template fetches the list of calls from your Zoho Desk portal.

• This endpoint reads from the list/calls API path and returns records under the response's data array. Nexla automatically handles pagination to retrieve subsequent pages of results.

For detailed information about response fields and available parameters, see the Zoho Desk API Documentation.

List List Call Comments

Retrieve list_call_comments. This endpoint template fetches the list of call comments from your Zoho Desk portal.

• This endpoint reads from the list/call/comments API path and returns records under the response's data array. Nexla automatically handles pagination to retrieve subsequent pages of results.

For detailed information about response fields and available parameters, see the Zoho Desk API Documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Zoho Desk data sources can also be manually configured to ingest data from any valid Zoho Desk API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Zoho Desk data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Zoho Desk destination, and select the Send to Destination option from the menu. Select the Zoho Desk connector from the list of available destination connectors, then select the credential that will be used to connect to Zoho Desk, and click Next; or, create a new Zoho Desk credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Zoho Desk endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Create Ticket

Creates a new support ticket in Zoho Desk. Use this template when you need to automatically open tickets based on data from your Nexla flows.

• This endpoint sends each Nexset record as JSON in the request body via a POST request to the tickets endpoint. The request body should contain the ticket fields required by the Zoho Desk API.

The record structure must match the Zoho Desk API's expected format for ticket creation, including any required fields such as the department ID. For detailed information about request body formats and available fields, see the Zoho Desk API Documentation.

Update Ticket

Updates fields on an existing ticket, identified by ticket ID. Use this template to modify ticket properties such as status, priority, or assignee from your Nexla flows.

• This endpoint sends each Nexset record as JSON in the request body via a PATCH request to the tickets/{ticketId} endpoint, where the ticket ID identifies the ticket to update. Include the ticket ID and the fields to be changed in your record.

The record structure must match the Zoho Desk API's expected format for ticket updates. For detailed information about request body formats and available fields, see the Zoho Desk API Documentation.

Add Ticket Comment

Adds a comment (public reply or private note) to an existing ticket. Use this template to append comments to tickets from your Nexla flows.

• This endpoint sends each Nexset record as JSON in the request body via a POST request to the tickets/{ticketId}/comments endpoint, where the ticket ID identifies the ticket the comment is added to. Include the comment content and whether it is public or private in your record.

The record structure must match the Zoho Desk API's expected format for ticket comments. For detailed information about request body formats and available fields, see the Zoho Desk API Documentation.

Create Contact

Creates a new contact (end customer) in Zoho Desk. Use this template when you need to automatically add contacts based on data from your Nexla flows.

• This endpoint sends each Nexset record as JSON in the request body via a POST request to the contacts endpoint. The request body should contain the contact fields required by the Zoho Desk API.

The record structure must match the Zoho Desk API's expected format for contact creation. For detailed information about request body formats and available fields, see the Zoho Desk API Documentation.

Manual configuration

Zoho Desk destinations can also be manually configured to send data to any valid Zoho Desk API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Zoho Desk APIs expect JSON format for write operations. For update operations, include the ID of the object to be updated in the endpoint URL.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Zoho Desk endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Zoho Desk endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.