JobMinglr for Zoho Recruit

Help and troubleshooting

Symptom, cause, fix — for the JobMinglr extension for Zoho Recruit. Almost everything here is one of three things: the bridge token, the Recruit connection, or an automation that is not switched on.

Last updated 22 August 2026

Check these three first

Three settings account for the large majority of support requests. Confirming them takes a minute and often ends the investigation:

The bridge token in the extension settings matches the one on your JobMinglr company profile.
The connection named jobminglr_recruit exists and shows as connected.
Both automations are on — the Job Openings workflow rule, and the schedule on jm_syncApplicants.

Symptoms and fixes

Symptom	Likely cause	Fix
Test connection fails in the JobMinglr panel	The gateway base URL or the bridge token is wrong, or the token has been rotated.	Re-check `bridge_base_url` (no trailing slash) and paste the bridge token again from JobMinglr → Company Profile → ATS Integrations. Tokens are long; copy, do not retype.
The sync run logs a 401 or “unauthorized”	The bridge token in the extension settings no longer matches the one on your JobMinglr account.	Ask JobMinglr support to confirm the current token, then update the setting. A rotated token invalidates the old value immediately.
No candidates are arriving	Most often nobody has applied yet. Otherwise: the schedule is not enabled, or your openings never reached JobMinglr.	Use Preview applicants in the panel. If it lists people, the schedule is the problem — check `jm_syncApplicants` is scheduled and enabled. If it lists nobody, confirm your openings synced (next row).
Openings are not reaching JobMinglr	The workflow rule is inactive, is missing the `jobId` argument, or only fires on Create.	Open the Job Openings workflow rule and confirm it triggers on Create and on Edit of Job Opening Status, and that the `jm_pushJob` action passes the record id as `jobId`. Then edit one opening to fire it.
Openings created before install never synced	The workflow rule only fires on save, so pre-existing openings are unknown to JobMinglr.	Edit each opening status once to trigger the push, or ask support to backfill your openings.
The sync fails with a connection or token error from Zoho	The `jobminglr_recruit` connection is missing, renamed, unauthorised, or its authorising user was deactivated.	Go to `Setup` → `Developer Space` → `Connections` and confirm a connection named exactly `jobminglr_recruit` exists, has scope `ZohoRecruit.modules.ALL`, and is connected. Re-authorise it if not.
A candidate arrived but is not linked to any opening	The opening they applied to had not been pushed to JobMinglr, so there was no opening to associate to.	Push the opening (edit its status), then associate the existing candidate to it manually. Later deliveries for that role will link themselves.
The same person appears twice	A candidate delivered earlier was deleted from Recruit and then applied again, or the same person applied to two different openings.	Two openings means two pipeline entries by design. For the deleted-then-redelivered case, merge the duplicates in Recruit.
Candidates stopped arriving after they had been working	The scheduled function was disabled, the connection expired, or the bridge token was rotated on the JobMinglr side.	Check the function log for the last run and its error, in that order: schedule enabled, connection connected, token current.

Where Zoho keeps the logs

Every run of either function leaves a log entry in Recruit, and that log is the fastest way to see what actually happened:

Setup → Developer Space → Functions → select jm_pushJob or jm_syncApplicants → its execution history, with the response from JobMinglr for each run.
Setup → Automation → Actions → Functions to confirm the workflow rule is actually invoking jm_pushJob.

A run that reports zero candidates is a healthy run

The sync only creates records when someone has applied since the previous run. Zero is the normal result most of the time, and does not mean the setup is broken.

Data, privacy and removal

Candidates delivered into your Recruit account are yours, and stay there if you uninstall the extension.
To stop all processing, uninstall the extension and delete the jobminglr_recruit connection. Access ends immediately.
For a data access, correction or deletion request, see the privacy policy or email privacy@jobminglr.com.

Contact support

Email support@jobminglr.com. Including these five things usually means the first reply is the answer rather than a question:

Your Zoho Recruit organisation id (the org_id in the extension settings).
Which function is involved — jm_pushJob or jm_syncApplicants.
The date and time of a run that went wrong, with your timezone.
The text of the error from the Zoho function log.
What you expected instead — a candidate you know applied, an opening you expected to sync.

Never send the bridge token itself. Support can look it up, and ask us to rotate it if you believe it has been exposed.