Utkrushta × Zoho Recruit · Integration
Three ways to connect Zoho Recruit to Utkrushta — from a 15-minute manual pilot to a two-click marketplace install — shown screen by screen, with everything we've verified in live testing.
First, the part that never changes
Once connected, the recruiter's only recurring action is something they already do every day: moving a candidate along their pipeline. Everything else — sending the test, scoring it, filing the result — happens on its own.
Candidate · Frontend Developer
Recruiter drags the stage to In Review — that's the whole action.
to priya@example.com
Test session created & emailed — no recruiter input.
Candidate · Frontend Developer
The score lands as a real, sortable field plus a note with the full report link — on the exact candidate page the recruiter already lives in. They never open a second tool.
The one-time setup — where the options differ
The options change only who does the one-time setup. Each screen below is what the recruiter sees, in order, labeled by who's doing the work.
Buildable this week. We provide the Connect button and a written guide; the recruiter creates three things inside Zoho's settings by hand.
Sync candidates & push scores automatically.
Connect Zoho RecruitOne button — all the token & security setup happens behind it.
Drag a Number field into the layout:
5 clicks, once. Our guide shows exactly where.
Save — setup done. From here it's the everyday loop above.
Same three Zoho-side steps — but a wizard inside Utkrushta walks the recruiter through each one with copy-paste values and live checkmarks as we detect each piece.
Same one-click connect as Option 1.
Connect Zoho RecruitWizard confirms each item as it detects it — nothing silently misconfigured.
We publish “Utkrusht” on the Zoho Marketplace. The extension provisions the field, webhook, and rule by itself on install — the only path to a true zero-setup experience.
Auto-send assessments on stage change; scores land on the candidate. ★★★★★
InstallRecruiter never opens Setup. Two clicks total.
Side by side
| Setup step | Option 1 · Manual | Option 2 · Wizard | Option 3 · Marketplace |
|---|---|---|---|
| Connect the account | 1 click | 1 click | 1 click |
| Create the score field | Recruiter, manual | Recruiter, guided | Automatic |
| Create the webhook | Recruiter, manual | Recruiter, guided | Automatic |
| Create the workflow rule | Recruiter, manual | Recruiter, guided | Automatic |
| Send tests, forever after | Just move stages | Just move stages | Just move stages |
The bottom row never changes. Only the one-time rows move from manual toward automatic as we invest more in building.
The account connection fully disappears behind one button — we handle all tokens, security, and region detection. But the score field, webhook, and workflow rule cannot be created through Zoho's normal API — we proved it in testing (a hard 400 error). The only mechanism that can provision them automatically is a published Marketplace extension that declares them on install. That single fact is what separates Option 3 from the other two.
Testing phase
Before writing any production code, we ran the entire flow live against a real Zoho Recruit account. Every piece works; this is no longer theory.
Each of these would have been a shipped bug if we'd built from documentation alone. All are now pinned down.
Zoho's login response hands back one address, but Recruit's data actually lives at recruit.zoho.in. The “official” one returns 404.
The fine-grained permission strings in the guide are refused by Zoho's own console. One broader permission (modules.ALL) is what actually works.
Writing a note where you'd expect fails with a method error. Notes go through a separate endpoint with the candidate's id attached.
Creating the score field via API returns a hard error — it must be made in Zoho's settings, or bundled into a Marketplace extension. This shapes the three options above.
Changing a candidate's stage in Zoho instantly sent a request to our test endpoint, straight from recruit.zoho.in. The make-or-break piece is solid.
Webhooks exist on Zoho's Professional & Enterprise plans only — not the free tier. Real customers on paid plans are unaffected.
We proved the score field can't be auto-created via API. We strongly suspect the webhook and workflow rule are the same — which would confirm the Marketplace extension is truly the only route to Option 3. One quick follow-up test will settle how much Option 2's wizard could automate.
Recommendation
Ship Option 1 for the first design-partner customer — buildable now, API fully proven. Add Option 2's wizard as customers grow. Invest in the Option 3 extension when we commit to polished self-serve — it's the only path to the true two-click install.