You do not have to replace your applicant tracking system to use AI agents in hiring. The right setup keeps your ATS as the system of record and has the AI tool read from it and write its results back, which is what two-way (bidirectional) sync means. This guide covers what to ask of any vendor, and how the 100Networks Workspace connects to Greenhouse and Zoho Recruit.
A quick note on what 100Networks is, because this post used to blur it: 100Networks is not an ATS. It is a recruiter marketplace for hard roles, where specialist recruiters work your search and you pay only when the person joins, plus the 100Networks Workspace, an AI hiring team for the roles your team fills itself. Both are designed to work next to the ATS you already have.
Why the ATS should stay the system of record
Teams stall on AI hiring tools for one recurring reason: the fear of a second source of truth. Two systems that each hold part of the candidate history drift apart within weeks, and then nobody trusts either of them.
The fix is a clear division of labour:
- The ATS holds the record. Every candidate, every stage, every decision, the audit trail your compliance and reporting depend on.
- The AI tool does work and reports back. Sourcing, screening, interviews, scheduling, notes. Its output lands on the candidate record your team already uses.
If you switched the AI tool off tomorrow, your ATS should still have every candidate and every verdict it wrote. If it would not, you have bought a migration, not an integration.
What "two-way" should actually mean
Plenty of tools call a one-way export an "integration". Two-way means:
- In: jobs and candidates come in from the ATS, so nobody retypes them.
- Mapping: your ATS stages map to the tool's stages, so a candidate who is at "Phone screen" in your ATS lands in the right place, and custom stages are not silently dropped.
- Out: the tool's results are written back onto the same candidate record, in a field or note your recruiters will actually see.
The questions to ask any vendor
- What exactly flows in, and what flows out? Jobs and candidates in; which results out, and where on the record do they land?
- Can it write without anyone choosing to? For most teams, writing back should be a deliberate action, at least until you trust it.
- What does a sync change in my ATS? It should be clear which actions only read and which also write, and what they write.
- How are stages mapped, and can we edit the mapping? Default mappings rarely survive contact with a real pipeline.
- How are live updates authenticated? Web hooks should be signed and verified, so the tool only accepts updates that genuinely come from your ATS.
- Who can connect, sync or disconnect it? This should be limited to owners and admins.
- What happens on disconnect? You should keep everything already synced, and the tool should simply stop pulling and writing.
How the 100Networks Workspace does it
The Workspace connects to Greenhouse and Zoho Recruit from its settings. Only owners and admins can change the connection, and syncing, sending verdicts and disconnecting each ask for confirmation and say what they touch.
| Greenhouse | Zoho Recruit | |
|---|---|---|
| How you connect | Paste a Harvest API key | Sign in to Zoho |
| What a sync brings in | Jobs and candidates | Jobs and candidates |
| What a sync writes back | Latest verdicts on candidates already synced | Latest verdicts on candidates already synced; adds three 100Networks fields on first sync |
| Stage mapping | Greenhouse stages to Workspace stages, editable | Zoho statuses to Workspace stages, editable |
| Where verdicts land | A note on the candidate | Verdict, score and report-link fields on the candidate |
| Live updates | Optional signed web hook you add in Greenhouse | A web hook the sync subscribes for you, checked against a shared token |
The verdicts are the Workspace's latest fit and interview results for each synced candidate. They go back as part of every sync, and you can also send them on their own. Either way they update records in your ATS and never contact a candidate. Disconnecting keeps everything already in the Workspace and stops new pulls and write-backs.
This sits inside the Workspace's wider rule: nothing reaches a candidate until your team approves it. The ATS connection only ever touches records, never people.
Where the marketplace fits
A managed search with 100Networks does not need an ATS connection at all. You send us a role, specialist recruiters who have placed that role before work it with our in-house sourcing desk, and a shortlist arrives with a written case for each person and compensation, notice period and location confirmed. Those candidates then go through your own process and your own ATS. You pay 8.33% of first-year salary on the day the person joins, with a 90-day replacement guarantee.
The short version: hand us the hardest roles, run the rest yourself in the Workspace, and keep your ATS as the record of both. For the wider comparison, see 100Networks vs Greenhouse, and for how the agents do their work, what an AI recruiting agent is and how AI interviews work.