Read Zoho Recruit (recruiting ATS/CRM) via its API v2 — search/get Candidates (dedup + criteria search before paying for external people data), list/search Clients (the agency's customer companies — an outbound exclusion list), and read Job Openings (the JD a search is built from). Use when the user mentions Zoho Recruit, checking the ATS before sourcing externally, or turning a job opening into search filters. Keys: self-serve OAuth connect — pick your data center and click Connect.
Zoho Recruit is a recruiting CRM, and one of the 54 tools hyreflow connects to Claude, ChatGPT and other AI assistants. Through hyreflow, an AI agent can run 11 actions, all of which look something up. Zoho Recruit costs no hyreflow credits, and runs on your own Zoho Recruit account.
You connect hyreflow once over MCP, and Zoho Recruit comes with it, next to the other 53 tools. You do not need to run a separate Zoho Recruit MCP server.
In Claude, ChatGPT or any other MCP client, add a custom connector named hyreflow with the server URL https://recruit.hyreflow.ai/api/v2/mcp. The MCP setup guide on hyreflow.ai has the exact steps for each app.
A browser window opens. Sign in, choose the workspace the assistant may act on, and approve. The connection is live.
Zoho Recruit runs on your own Zoho Recruit account. Connect it on the Integrations page in hyreflow, and hyreflow charges no credits for its calls.
Tell Claude or ChatGPT what you want done with Zoho Recruit in plain language. The assistant picks the Zoho Recruit action that fits and runs it through hyreflow.
Using Cursor, Claude Code or another client? Every one is covered in the MCP setup guide.
Through hyreflow, an AI agent can run 11 Zoho Recruit actions, all of which look something up. Zoho Recruit costs no hyreflow credits, and runs on your own Zoho Recruit account.
| Zoho Recruit action | What it does | Cost through hyreflow |
|---|---|---|
| Search candidates | Looks something up | no hyreflow credits |
| Search clients | Looks something up | no hyreflow credits |
| Search job openings | Looks something up | no hyreflow credits |
| Search records | Looks something up | no hyreflow credits |
| List clients | Looks something up | no hyreflow credits |
| List job openings | Looks something up | no hyreflow credits |
| List records | Looks something up | no hyreflow credits |
| Get candidate | Looks something up | no hyreflow credits |
| Get fields | Looks something up | no hyreflow credits |
| Get job opening | Looks something up | no hyreflow credits |
| Zoho Recruit action | What it does | Cost through hyreflow |
|---|---|---|
| Get record | Looks something up | no hyreflow credits |
One credit is priced on the pricing page. The full price list for every tool is in the pricing tables.
Ask for the outcome and your agent composes the run itself. Or start from a skill, a whole pipeline it already knows end to end.
browse all skills →hyreflow ships a written playbook for Zoho Recruit, and the agent loads it before the first call. Auth, rate limits, what each call costs, which actions need your approval, and the mistakes worth avoiding. It is the difference between an agent that knows the tool and one that guesses at it.
Read the Zoho Recruit docs →HOW in lib/zoho_recruit.py.
api-console.zoho.com, paste its Client ID and Client Secret, pick your data center (us, eu, in, au, jp, ca, sa or cn) and click Connect. No refresh token is ever pasted — Hyreflow stores the connection and refreshes it automatically.get_fields to read an account's real field names (they vary per account).Candidates, Clients, Job_Openings, Contacts.Generic (any module): list_records, get_record, search_records, get_fields. Candidates: search_candidates, get_candidate. Clients: list_clients, search_clients. Job Openings: list_job_openings, search_job_openings, get_job_opening.
criteria, email, phone or word. criteria looks like ((Field:operator:value)and(Field:operator:value)) (≤10 conditions); escape a comma or paren inside a value with a backslash.per_page caps at 200; page on the response's paging info.get_fields(module=...) rather than guessing.Read source, not a write target: dedup + search Candidates before sourcing externally, build the outbound exclusion list from Clients, and turn a Job Opening's description into people_search filters.
Call via the CLI: hyreflow tools execute zoho_recruit <method> --payload '{...}' (preview with --dry-run; hyreflow tools get zoho_recruit <method> returns the live contract + cost). Only the methods listed below are callable.
get_candidate(candidate_id: str) -> Any — GET /Candidates/{id}.get_fields(module: str) -> Any — GET /settings/fields?module= — the account's field API names for a module (custom fields included). Needs scope ZohoRecruit.settings.fields.READ.get_job_opening(job_opening_id: str) -> Any — GET /Job_Openings/{id} — the full record, including the job description field.get_record(module: str, record_id: str) -> Any — GET /{module}/{id} — one full record.list_clients(*, page: int | None = None, per_page: int | None = None, fields: str | None = None) -> Any — GET /Clients — the agency's client companies (Client_Name, Website, …), one page ≤200.list_job_openings(*, page: int | None = None, per_page: int | None = None, fields: str | None = None) -> Any — GET /Job_Openings — one page of job openings (Job_Opening_Name, Job_Opening_Status, Client_Name…).list_records(module: str, *, page: int | None = None, per_page: int | None = None, fields: str | None = None, sort_by: str | None = None, sort_order: str | None = None) -> Any — GET /{module} — one page of records (per_page ≤200). fields = comma-separated API names.search_candidates(*, criteria: str | None = None, email: str | None = None, phone: str | None = None, word: str | None = None, page: int | None = None, per_page: int | None = None) -> Any — GET /Candidates/search — e.g. criteria ((Current_Job_Title:contains:engineer)and(City:equals:Austin)), or email=[email protected] for an exact dedup check, or word= for a keyword across the record.search_clients(*, criteria: str | None = None, word: str | None = None, page: int | None = None, per_page: int | None = None) -> Any — GET /Clients/search — e.g. criteria (Website:contains:acme.com) or (Client_Name:equals:Acme).search_job_openings(*, criteria: str | None = None, word: str | None = None, page: int | None = None, per_page: int | None = None) -> Any — GET /Job_Openings/search — e.g. criteria (Job_Opening_Status:equals:In-progress).search_records(module: str, *, criteria: str | None = None, email: str | None = None, phone: str | None = None, word: str | None = None, page: int | None = None, per_page: int | None = None) -> Any — GET /{module}/search — exactly one of criteria | email | phone | word. No match → {"data": []}.Yes. hyreflow is a connector for Claude, ChatGPT and other AI assistants. Once hyreflow is connected, you ask for the outcome in plain language and the assistant calls Zoho Recruit for you. hyreflow exposes 11 Zoho Recruit actions this way.
Yes. Zoho Recruit runs on your own Zoho Recruit account. You connect it to hyreflow once, hyreflow charges no credits for the calls, and Zoho Recruit bills you as before.
Zoho Recruit costs no hyreflow credits, and runs on your own Zoho Recruit account.
Add the hyreflow MCP server to your assistant and sign in. hyreflow calls the Zoho Recruit API directly and exposes its actions as tools the assistant can run, so there is no separate Zoho Recruit server to install.
Connect hyreflow to Claude or ChatGPT and ask for the outcome. It reads the playbook above before it makes a single call.