ATS Integrations: What Syncs One Way, What Syncs Both, and How Often
Integration pages are usually a wall of logos with no information behind them. A buyer needs three things per connection: what data moves, which direction, and how often.
Most ATS integrations pages show you logos. What actually determines whether your team works in one system or four is the direction of each connection. Job portals, assessments, interview tools and calendars generally flow one way into the ATS. Messaging, email and collaboration tools flow both ways. That single distinction predicts more about your daily experience than any feature list.
Key takeaways
- Direction matters more than presence. A one-way sync into your ATS still leaves your team working in two systems for anything that involves writing.
- One-way is often correct. Job portals, assessments and interview platforms are the system of record for their own data, so pulling in is the right design.
- Frequency determines trust. A nightly sync means the record is wrong for most of the working day, and a record that is sometimes wrong gets treated as always unreliable.
- The long tail needs an API. No vendor will have built the integration you need most, because it will be to something specific to your desks.
The five categories of ATS integration
Job portals. Naukri, LinkedIn, Indeed, Handshake. Where candidates enter, and therefore where duplicates enter with them.
Messaging and email. WhatsApp, Gmail, Outlook, and voice providers. Where the conversation actually happens.
Scheduling. Google Calendar, Meet, Zoom, Teams. Where interviews get booked and where the coordination cost sits.
Assessment and interviewing. Skills platforms and interview tools that feed evidence back onto the candidate record.
Collaboration and productivity. Slack, Notion, Sheets, and meeting intelligence tools. Where the team coordinates around the work.
Which ATS integrations are one-way and which are two-way
The pattern is consistent and it follows from where the system of record sits.
| Category | Direction | Why |
|---|---|---|
| Job portals | One way, in | The portal owns its listings and applications. You are consuming, not publishing back. |
| Interview tools | One way, in | The recording and outcome are generated there and land on your record. |
| Assessments | One way, in | Results flow to the candidate record. Nothing needs to flow back. |
| Calendar | One way, in | Availability and bookings read into the ATS. |
| Email and messaging | Two way | Recruiters send and receive from both sides, so both must stay current. |
| Collaboration tools | Two way | Updates and actions move in both directions during a working day. |
One-way is not a limitation in these cases. It is the correct architecture. The mistake buyers make is assuming two-way is universally better and treating a one-way portal integration as a shortfall, when the alternative would mean writing candidate data back into a job board you do not control.
Where one-way is a genuine problem is messaging. If your email or WhatsApp integration only reads in, then every reply a recruiter sends from their own inbox is invisible to the record, and the history is incomplete by design.
What to check on a job portal integration specifically
This is the connection that carries the most operational weight in India, and the one most likely to be described vaguely.
Does it bring the full profile or just the application?
An integration that delivers a name, an email and a CV attachment is not the same as one that brings the structured profile. The first leaves your team retyping fields, which is exactly the admin cost you were trying to remove.
What happens when the person already exists?
The single most important question, and it is almost never asked in a demo. A portal integration with no matching at the point of entry is a duplicate generator running on a schedule.
Does it pull historical applications or only new ones?
Some connections start from the day you switch them on. If you have two years of applications sitting in a portal account, find out whether they come across before you assume they will.
What is the rate limit?
Portals throttle. On a high-volume day this determines whether applications appear in minutes or in hours, and hours means recruiters go back to checking the portal directly.
Integration count is a vanity metric
Vendors compete on the number of logos, and the number tells you almost nothing.
What matters is whether the five tools your team opens every day are connected properly, and whether the connections are deep rather than nominal. A platform with 20 well-built integrations covering your actual stack beats one with 200 shallow ones covering everybody's.
The practical test: pick the tool your team uses most after email. Ask to see it working live, with a real record, moving real data in the direction they claim. One demonstration is worth the entire logo wall.
The three integrations most firms switch on first
Without it, the candidate record has no history, and every other integration is decoration on top of an incomplete record. This is the one that makes the rest worth having.
In India this is the primary candidate channel, and it is where the majority of replies arrive. A system that does not thread WhatsApp holds a partial conversation on every single candidate, and the missing part is usually the most recent.
Your main job portal
Usually Naukri. This is where new candidates enter, which means it is also where duplicates enter. Connecting it properly is a data quality decision as much as a sourcing one, and the question to ask is what happens at the moment a record arrives, not how many fields map.
Calendar is the natural fourth. Everything else can wait until those are being used daily, because an integration nobody uses is a support surface with no return.
Why sync frequency decides whether anyone trusts the data
This gets less attention than direction and causes more day-to-day friction.
A recruiter looks at a candidate record before a client call. If the last two messages have not synced yet, the recruiter says something slightly wrong to the client, and learns that the record cannot be relied on. From that point they check the source system anyway, which means the integration has added a step rather than removed one.
The rule that holds: anything a recruiter acts on during the day must be real time. Reporting and analytics feeds can be batched, because a few hours of lag changes no decision.
Ask what happens when a sync fails, too. Silent failure is common and worse than no integration, because nobody knows the record is stale.
The six questions to ask any vendor
- Is this integration one-way or two-way, specifically?
- What is the sync frequency, and what happens when it fails?
- Which fields map, and which do not?
- Does the integration cost extra, now or at renewal?
- Who maintains it when the other vendor changes their API?
- Is there an open API, and does it write as well as read?
Question four catches the most unpleasant surprises. Integrations displayed on a marketing page are frequently priced as add-ons, and the discovery usually happens at renewal rather than at purchase.
Question six matters more than it looks. An API that reads but cannot write is half an API, and it will not support the integration you actually need.
When to build instead of buy
No vendor will have built the integration you need most, because it will be to something specific to your desks: a client's VMS, a background check provider, a payroll system, or an internal tool nobody else uses.
That is what an open API is for. The question is not whether one exists but what it covers, how it is authenticated, whether it is rate limited in a way that breaks your use case, and whether it is documented well enough that a contractor can work from it without a support ticket per endpoint.
Before building anything, check the cost of the alternative honestly. A weekly CSV export that takes someone twenty minutes is often cheaper than a custom integration that needs maintaining forever.
Consolidation versus best of breed
Every integration you rely on is a decision to keep two systems instead of one. Worth making deliberately.
| Best of breed, integrated | Consolidated in one platform | |
|---|---|---|
| Feature depth | Deeper in each specialism | Good enough in most |
| Data consistency | Depends on sync direction and frequency | Single source, no reconciliation |
| Cost | Multiple subscriptions and seats | One line item |
| Failure mode | A vendor changes an API and something breaks | Contained, but you own the whole risk |
| Switching later | Replace one component | Replace everything at once |
The last row is the honest concession. Consolidation is genuinely better day to day and genuinely worse to reverse. A firm that consolidates and later regrets it faces a full migration rather than swapping a component, which is a real cost to weigh at the point of purchase rather than discover later.
The rule of thumb that holds: consolidate anything that touches the candidate record, and integrate anything that does not.
Where integrations create risk
Two things worth checking that rarely appear in a demo.
Data flowing out. Every connection is a place candidate data leaves your system. Under the GDPR and India's DPDP Act, you remain responsible for it. Know which integrations transmit personal data and on what basis.
Dependency on someone else's roadmap. When a platform changes its API or its terms, an integration you depend on can degrade without warning. Ask who monitors that and how quickly it gets fixed, because the honest answer determines how much of your workflow you should build on it.
Frequently asked questions
What is a two-way ATS integration?
One where data flows in both directions, so a change made in either system appears in the other. A one-way integration only pulls data in, which means your team still has to work in the source system for anything that involves writing back.
Which ATS integrations are usually one-way?
Job portals, assessment platforms, interview tools and calendars typically flow in one direction, because they are the system of record for their own data. Messaging, email and collaboration tools are where two-way sync matters and where you should expect it.
Does an ATS integrate with Naukri?
Some do and the depth varies considerably. Ask specifically whether applications, full profiles and CVs come across, whether it is one-way or two-way, and critically how duplicates against your existing database are handled at the point of entry.
Why does WhatsApp integration matter for recruitment in India?
Because it is the channel most candidates actually respond on. Without it threaded into the candidate record, the majority of the conversation history sits on individual recruiters' phones and leaves the firm when they do.
How often should an ATS sync with connected tools?
Real time for anything a recruiter acts on during the day, such as messages, email and calendar. Batch or scheduled sync is acceptable for reporting feeds and analytics, where a few hours of lag changes nothing.
What should you ask a vendor about integrations before signing?
Six things: is it one-way or two-way, what is the sync frequency, which specific fields map, does it cost extra now or at renewal, who maintains it when the other vendor changes their API, and what does the open API cover for everything not on the list.
A note on integrations and adoption
The integration nobody switches on is the most common failure, and it is not a technical one.
Teams adopt the connections that remove a step they consciously resent. Email and WhatsApp qualify immediately, because everyone knows they are retyping. A Notion or Sheets connection often does not, because the pain it removes is diffuse.
The practical approach is to switch on three integrations at go-live and nothing else. Let the team feel the benefit of those, then add the fourth when someone asks for it. A platform that arrives with twenty active connections teaches people that most of them do not matter.
How to evaluate this properly
List the five tools your team opens most often in a day. For each one, ask the vendor for direction and frequency in writing before you sign.
The gap between a logo on a page and a working two-way sync is where most post-purchase disappointment in this category comes from, and it is entirely avoidable with one email.
See the integrations that matter to your desks
Tell us the five tools your team lives in. We will show you exactly what moves, which way, and how often.
Book a demoFounder of Sortinghat, an AI-native ATS and CRM for staffing, search and RPO firms. Writes about recruiter capacity, sourcing economics and what actually changes when AI reaches a delivery desk. More about the author
Related reading
Duplicate Candidate Records: Why They Happen, What They Cost, and How to Prevent Them
WorkflowRecruiter Admin Time: Where the Hours Actually Go, and What Automatic Capture Removes
Talent PoolTalent Pool Software: How to Rank Your Own Database Before You Pay a Job Portal
Talent PoolLinkedIn Sourcing: What Our Chrome Extension Collects, and What It Does Not