Skip to main content
Zoho Recruit is an applicant tracking system (ATS) and recruitment software that helps businesses manage their hiring process, from posting job openings and tracking candidates to scheduling interviews and managing client relationships.

​
Configuring Zoho Recruit as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Zoho Recruit option from the list of connectors. Click Next and you’ll be prompted to add your access.

​
1. Add account access

You’ll need to provide OAuth2 credentials to authorize Nekt to access your Zoho Recruit data. The following configurations are available:
  • Authentication Mode (default: custom): Choose the authentication mode to use. Default uses Nekt’s OAuth app, while Custom uses a custom OAuth app created by you.
    • Default: You will be prompted to authenticate directly. Please use a Zoho Recruit account with proper access. Using an account with insufficient permissions will result in an error.
    • Custom: You will need to manually provide your own Client ID, Client Secret, and Refresh Token.
  • Client ID (if Custom mode): The OAuth2 Client ID from your Zoho Developer Console. You can create one by registering a Server-based Application in the Zoho API Console.
  • Client Secret (if Custom mode): The OAuth2 Client Secret associated with your Client ID. (Masked as a password field).
  • Refresh Token (if Custom mode): The OAuth2 Refresh Token obtained through Zoho Recruit’s OAuth flow from an account with proper access. (Masked as a password field).
  • Zoho Domain (optional, default: com): The Zoho domain suffix matching your account region. Use com for US, eu for Europe, in for India, com.au for Australia, or jp for Japan.
  • Start Date (optional): The earliest date from which records will be synced incrementally.
Once you’re done, click Next.

​
2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select entire groups of streams or pick specific ones.
Tip: The stream can be found more easily by typing its name.
Select the streams and click Next.

​
3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.
  • Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
  • Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
  • Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
    • Incremental: every time the extraction happens, we’ll get only the new data, which is good if you want to keep every record ever fetched.
    • Full table: every time the extraction happens, we’ll get the current state of the data, which is good if you don’t want to have deleted data in your catalog.
Once you are done configuring, click Next.

​
4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can define some additional settings:
  • Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
  • Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.
Once you are ready, click Next to finalize the setup.

​
5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

​
API Limitations

The Zoho Recruit API enforces rate limits on requests. If a rate limit is reached (HTTP 429), the connector automatically reads the X-ACCESSTOKEN-RESET response header to calculate the exact time remaining until the limit resets. It then waits for this duration (plus a small buffer) before safely retrying the request, ensuring continuous and reliable data extraction.

​
Streams and Fields

Below you’ll find all available data streams from Zoho Recruit and their corresponding fields:
Records of individuals who have applied or been sourced for job positions.
Active and historical job positions within your organization or client companies.
Associated candidates for each Job Opening. Streamed incrementally using Updated_On.
Contact persons at client companies involved in the recruitment process.
Scheduled and completed interviews linking candidates to job openings.
Client companies that have open positions or recruitment agreements.
Notes attached to various records in Zoho Recruit, such as candidates, job openings, or clients.

​
Skills for agents

Download Zoho Recruit skills file

Zoho Recruit connector documentation as plain markdown, for use in AI agent contexts.