What is Zero-Latency ATS Sync?
Zero-Latency ATS Sync is an integration pattern in which a sourcing tool and an applicant tracking system (ATS) send each other every change as it happens, through webhooks, instead of waiting for a scheduled check. Scheduled polling can delay an update by up to 15 minutes on Zapier's free plan (Zapier Help Center, Oct 2026).
Definition reviewed on
How does zero-latency ATS sync work?
What is the difference between webhooks and polling?
Zero-Latency ATS Sync relies on events rather than schedules. With polling, one system asks the other for changes at a fixed interval, so an update waits for the next check: every 15 minutes on Zapier's free plan and every 1 to 2 minutes on paid plans (Zapier Help Center, Oct 2026). With a webhook, the ATS sends a message to the other system as soon as the change happens, which removes the wait between a change and the next check. Greenhouse, for example, posts a JSON payload over HTTPS when a candidate changes stage, through its candidate_stage_change event (Greenhouse documentation, Oct 2026), and Lever documents an equivalent candidateStageChange event. The limit is delivery: a webhook can fail when the receiving system is down, so both sides need retries and a periodic reconciliation that catches whatever was missed.
Which changes should flow in each direction?
A Zero-Latency ATS Sync is bidirectional only when both systems publish their changes. From the sourcing tool to the ATS, the useful events are a new candidate added to a job, the score with the written reason behind it, and the conversation history. From the ATS back to the sourcing tool, stage changes matter most: a rejected, hired or archived candidate should stop receiving outreach at once. Without that return path, a candidate rejected in the ATS on Monday can be contacted again by the sourcing tool on Tuesday. Both ATS vendors cited here document such events, for example hire_candidate and reject_candidate in Greenhouse, candidateHired and candidateArchiveChange in Lever (vendor documentation, Oct 2026). The limit: field mapping differs per ATS, so stage names, custom fields and duplicate rules must be set for each connection rather than assumed.
What should a buyer check before trusting an ATS sync?
Zero-Latency ATS Sync is a design goal, so a buyer should test it rather than take it on trust. Five checks cover most risks. First, the mechanism: webhooks or polling, and at what interval. Second, direction: does a rejection in the ATS reach the sourcing tool, or only the reverse? Third, failures: Greenhouse retries a failed webhook up to 7 times over about 15 hours and Lever up to 5 times (vendor documentation, Oct 2026), so ask how the tool recovers a missed event. Fourth, objections and erasure under GDPR Article 17 should reach both systems. Fifth, duplicates: one person, one record. TrueCalling's pricing lists ATS integration from the Business plan; confirm which connector covers your ATS, and in which direction it syncs, before you buy. Our guide to ATS integration for AI sourcing walks through a setup.
How does zero-latency ATS sync differ from scheduled syncing?
| Scheduled sync | Zero-Latency ATS Sync (the pattern) |
|---|---|
| Polling every 1 to 15 minutes, depending on the plan. | A webhook event is sent when the change happens. |
| One-way push into the ATS. | Stage changes also flow back to the sourcing tool. |
| Opt-outs reconciled by hand between systems. | Objections and erasure requests propagated to both systems. |
| Missed updates found by chance. | Retries plus periodic reconciliation recover failed events. |
Related terms
- Autonomous Sourcing Copilot
AI agent that runs brief → shortlist → first contact while the recruiter approves each action.
- WhatsApp Sourcing Automation
Sourcing method where software drafts and manages first contact on WhatsApp, with recruiter approval.
- TrueFit 360
TrueCalling's candidate fit score: 0 to 100, with matched skills, gaps and a written reason.
FAQ: Zero-Latency ATS Sync
Is real-time ATS sync really zero latency?
No. "Zero-latency" names the design goal of sending each change as an event instead of waiting for a scheduled check. Events still take network time, can fail and are retried: Greenhouse retries a failed webhook up to 7 times over about 15 hours. What disappears is the polling delay, not every delay.
What is the difference between an ATS sync and an ATS import?
An import copies data once; a sync keeps two systems consistent over time. An import is enough to load a past talent pool, but it goes stale the next day. A sync carries every later change, such as a stage move or an opt-out, between the ATS and the sourcing tool.
Which ATS events matter most for sourcing?
Stage changes, rejections, hires and deletions. They tell the sourcing tool to stop contacting a candidate who is already in process, rejected or hired, and to remove someone who asked for erasure. Greenhouse and Lever both publish webhook events for these changes, such as candidate_stage_change and candidateStageChange.
Does TrueCalling sync with my ATS?
It depends on your ATS and your plan. TrueCalling's pricing page lists one ATS integration on the Business plan and unlimited ATS integrations on Enterprise, and Deel, the global hiring platform, has a native integration. Ask which connector covers your ATS, and in which direction it syncs, before you commit.
Sources
- Zapier Help Center: "How Zap triggers work" (polling intervals by plan) (accessed 5 Oct 2026)
- Greenhouse developer documentation: Recruiting webhooks (accessed 5 Oct 2026)
- Lever developer documentation: Webhooks (accessed 5 Oct 2026)
- Regulation (EU) 2016/679 (GDPR): Articles 14, 15, 17, 20 and 22 (EUR-Lex) (accessed 5 Oct 2026)
- TrueCalling pricing page (plans and included integrations) (accessed 5 Oct 2026)
See Zero-Latency ATS Sync in action
30-minute demo of TrueCalling against one of your open roles: sourcing, scoring, and outreach end-to-end.