Zoho Recruit (Edge)

Configure Zoho Recruit as a Source in your Pipeline

Perform the following steps to configure your Zoho Recruit 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 Recruit.

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 Recruit Source.

   • In the Connect to Zoho Recruit section:

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

     • Client Secret: The Client Secret of the API client.

     • Region: The data center where your Zoho account is hosted. Select one of the following: US (zoho.com), Europe (zoho.eu), India (zoho.in), Australia (zoho.com.au), China (zoho.com.cn), or Japan (zoho.jp). The region must match the domain of the Zoho API Console in which you created the API client.

   • Click Authorize, log in to your Zoho account if prompted, select the check box to allow access, and then click Accept to grant Hevo the requested scopes.

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

   When you click this button, Hevo checks that the OAuth authorization is valid by reading the candidates of your Zoho Recruit organization.

---

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. To ingest a child object, you must also select its parent object. For example, to ingest the Interviewer Save object, you must also select the Interview Save object. The Data Model lists the child objects of each parent object.

Zoho Recruit stores records of the Clients, Candidates, Interviews, Job Openings, and Vendors modules in two states: saved records and drafts, which are records that a user started but did not save. Hevo loads each state into its own object. For example, it loads the saved candidates into the Candidate Save object and the draft candidates into the Candidate Draft object. The Account objects contain the records of the Clients module.

In the first run of the Pipeline, Hevo ingests all the data available for the selected objects in your Zoho Recruit organization. In the subsequent runs, as per the sync frequency, Hevo ingests data as follows:

Hevo ingests the child objects of a parent object along with it.

Zoho Recruit limits the number of API calls that an organization can make in a rolling 24-hour period, based on its edition and number of user licenses, and the number of calls that can run at the same time. Read API Limits. If Zoho Recruit returns a rate limit error, Hevo waits and retries the request. To understand how Hevo handles such scenarios, read Handling Rate Limit Exceptions.

---

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:

---