Documentation

Connect Zoho Recruit

Connecting Zoho Recruit is a sign-in with nothing to copy out. Live updates are the longer half: Zoho sends them through webhooks attached to workflow rules, which you build one event at a time.

Before you start

Voyse authorises through Zoho's European sign-in. If your Zoho account is hosted in another region, the sign-in won't complete — Zoho ties an authorisation to the region your organisation is registered in. Ask Voyse support before you spend time on it.

For the webhooks later on, you'll need the Manage Workflow permission in Zoho Recruit.

Connect it

  1. Select Integrations in the sidebar.
  2. Under Connect an ATS, choose Zoho Recruit.
  3. Select Connect with Zoho. Zoho's sign-in opens.
  4. Sign in and agree to the access Voyse asks for. You're returned to the Integrations page.
  5. The pill by the provider's name reads Connected, and Sync status fills in once the first import finishes.

Voyse asks Zoho to read job openings, departments and clients, to work with candidates and applications, and to read your account settings — which is also what it checks the connection against, so declining that part means the connection can't be saved at all.

Add the webhooks

Zoho doesn't sign its webhooks, so Voyse identifies them by a secret it gives you, sent as a parameter on the URL. Each event needs its own webhook and its own workflow rule, which is why this section is longer than the rest of the page.

  1. On the Voyse Integrations page, copy the Webhook URL and the Secret key from the Webhooks section.
  2. In Zoho Recruit, go to Setup → Automation → Actions → Webhooks and select Configure Webhook.
  3. Fill in the new webhook:
    • Name — what the event is, such as Voyse job created.
    • URL to Notify — the webhook URL you copied.
    • Method — POST.
    • Module — Job Openings for job events, Candidates for the rest.
    • Append Custom Parameters — two pairs: auth-token set to the secret key you copied, and action set to the event name from the table below.
  4. Save, then go to Setup → Automation → Actions → Workflow rule, create a rule for the same event on the same module, and under the rule's actions associate the webhook you created in step 3.
  5. Repeat for each event you want. Back in Voyse, Last webhook changes from Never the first time one arrives.
What happened action value Module
A job opening was created job_created Job Openings
A job opening was edited job_updated Job Openings
A job opening was deleted job_deleted Job Openings
A candidate was hired application_hired Candidates
A candidate was deleted candidate_deleted Candidates

Voyse ignores anything with an action it doesn't recognise, so a typo shows up as an event that arrives and changes nothing. The candidate deletion event is what withdraws that person's personalised links, so it's worth having if you use them.

Treat the secret key as a credential — it's the only thing telling Voyse the message came from your Zoho.

What comes across

Job openings, with their departments. Applications go back the other way, and your stages are read so a hire or a rejection in Zoho is reflected in Voyse.

Capabilities lists Job Sync, Application Submit and Webhook Events as essential, and Candidate Notes — a summary of what a candidate asked, written to their profile — as optional. Check capabilities re-tests it.

Working with one client only

If you're an agency running several clients in one Zoho Recruit account and want Voyse to see only one of them, account owners get a Data siloing section on the Integrations page. Enter that client's record ID and every import and submission is filtered to it. Leave it empty to work across everything.

To find the ID, open the client record in Zoho Recruit and copy the long number from the address, after /tab/Clients/.

If it didn't work

  • Zoho's sign-in refuses or returns an error — most often the region, as above.
  • Last webhook stays Never — check the auth-token parameter matches the secret key exactly, and that the workflow rule is active. A webhook with no rule attached never fires.
  • Events arrive but nothing changes in Voyse — the action parameter is missing or misspelled.

The rest of the page — sync status, the activity log, disconnecting — is covered in Connect your ATS.