Zoho Desk (Edge)

Configure Zoho Desk as a Source in your Pipeline

Perform the following steps to configure your Zoho Desk Source:

1. Click Pipelines in the Navigation Bar.

2. Click + Create Pipeline in the Pipelines List View.

3. On the Select Source Type page, select Zoho Desk.

4. On the Select Destination Type page, select the type of Destination you want to use.

5. In the Configure Source screen, specify the following:

   

   • Source Name: A unique name for your Source, not exceeding 255 characters. For example, Zoho Desk Source.

   • In the Connect to Zoho Desk section, specify the following:

     • Client ID: The client ID of the client that you created in the Zoho API Console.

     • Client Secret: The client secret of the client.

     • Region: From the drop-down, select the data center of your Zoho account. For example, select United States if you log in to Zoho at accounts.zoho.com. Default value: United States. The following data centers are supported:

       Region	Zoho Accounts URL
       United States	accounts.zoho.com
       Europe	accounts.zoho.eu
       India	accounts.zoho.in
       Australia	accounts.zoho.com.au
       Japan	accounts.zoho.jp
       Canada	accounts.zohocloud.ca
       Saudi Arabia	accounts.zoho.sa
       Singapore	accounts.zoho.sg
       United Arab Emirates	accounts.zoho.ae
       China	accounts.zoho.com.cn

6. Click Authorize, and then do the following in the window that opens:

   1. Log in to your Zoho account. To ingest all the objects, log in as a user with the Administrator profile in Zoho Desk.

   2. If you belong to more than one Zoho Desk portal, select the portal whose data you want to replicate, and click Submit.

      

   3. Select the I allow Hevo to access the above data from my Zoho account check box, and click Accept.

      

   Once the authorization is successful, you are redirected to the Configure Source screen.

7. Click Test & Continue to test the connection to your Zoho Desk Source. Once the test is successful, you can proceed to set up your Destination.

---

Data Replication

Hevo replicates data for all the objects selected on the Configure Objects page during Pipeline creation. By default, all supported objects and their available fields are selected. However, you can modify this selection while creating or editing the Pipeline.

Hevo ingests the following types of data from your Source objects:

• Historical Data: The first run of the Pipeline ingests all the data of the selected objects.

• Incremental Data: Once the historical load is complete, Hevo ingests data as per the sync frequency as follows:

  • For the Account, Contact, Task, and Ticket objects, Hevo ingests the records that were created or updated since the previous run. For each ticket or task that is ingested, Hevo also ingests its child records, such as comments and time entries, and replaces the existing child records of that ticket or task in the Destination.

  • For all the other objects, Hevo ingests the entire data in each run.

You can resync only the Groups, Label, Organization, Profile, and Role objects.

Zoho Desk limits the number of API calls that a portal can make in a day, as per its edition, and the number of calls that can run at the same time. Read API credits. These limits are shared by all the applications that read data from the portal. If Zoho Desk returns a server error, or a rate limit error that asks Hevo to wait for 10 minutes or less, Hevo retries the request up to four times, at an interval of five seconds. If the daily API credits of your portal are used up, Hevo stops ingesting the affected objects in that run, and resumes in the next run as follows:

• For the Account and Contact objects, Hevo continues from the record at which the ingestion stopped.

• For the Task and Ticket objects, Hevo ingests the records that were created or updated since the last completed run.

• For all the other objects, the object fails in that run, and Hevo ingests its entire data in the next run.

Note: You can create a Pipeline with this Source only using the Merge load mode. The Append mode is not supported for this Source.

---

Schema and Primary Keys

Hevo uses the following schema to upload the records in the Destination. For a detailed view of the objects, fields, and relationships, click the ERD.

---

Data Model

The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:

---