ATS Integration 101: How to Connect a Candidate Sourcing Layer to Your Existing System in 7 Days

Your ATS is not broken. It does exactly what it was designed to do: manage candidates through a hiring workflow from application to offer. What it doesn't do — and was never designed to do — is generate candidates from scratch. The gap between your ATS and a full pipeline is a sourcing gap, not a technology gap. And in 2026, closing that gap takes seven days, not seven months.

What a sourcing layer actually is

A sourcing layer is any system that sits upstream of your ATS and generates candidate leads through advertising, outreach, or community engagement. It could be a social media campaign, a referral portal, a WhatsApp chatbot, or a combined system. The key requirement is that it connects to your ATS — so candidates who pass pre-screening enter as structured profiles, not emails in someone's inbox.

The three integration methods (in order of ease)

• Webhook push: the sourcing system sends candidate data to your ATS via an HTTP webhook whenever a candidate passes pre-screening — requires no ATS changes, just a webhook URL from your ATS admin
• API integration: a two-way connection that both pushes candidates in and reads ATS status updates back — more powerful but requires ATS API credentials and minor configuration
• Unified API middleware (Merge, Kombo, Finch): a layer that abstracts away ATS-specific APIs, allowing the same sourcing system to connect to dozens of different ATS platforms — ideal for agencies managing multiple clients

What you need from your ATS team to get started

• The webhook receiver URL from your ATS — available in most modern platforms in under 5 minutes
• Confirmation of which candidate fields your ATS expects: name, phone, email, role, pre-screening answers
• Agreement on candidate status: what stage should sourced candidates enter the ATS at
• Optional: ATS API key if you want two-way sync for candidate status updates

Day-by-day: 7 days to a connected sourcing pipeline

• Day 1: Define requirements profile and agree on ATS integration method with your IT or HRIS team
• Day 2: Set up webhook or API connection — typically under 2 hours with documentation
• Day 3: Build sourcing campaigns targeting your candidate profile on Meta or LinkedIn
• Day 4: Launch landing pages with pre-screening questions mapped to ATS fields
• Day 5: First test candidates pushed to ATS — verify data mapping and stage entry
• Day 6: Go live with full campaign — monitor candidate flow and ATS entry
• Day 7: First report: candidates sourced, pre-screening pass rate, ATS entry rate, pipeline depth

ATS platforms that support webhook integration out of the box

Workday, iCIMS, Greenhouse, Lever, Smartrecruiters, Darwinbox, Zoho Recruit, Keka, Bullhorn, Recruiterflow, and most modern ATS platforms support webhook receivers. If your ATS is listed here, your integration timeline is genuinely 7 days. Older or highly customized platforms may require an API middleware layer — but the timeline extends to 2–3 weeks at most, not months.