- Blog
- Recruiting operations
Recruiting operations
ATS integration: how to choose, map and test your connection
Ed Godshaw, Co-founder and CTO, Alfa AI ·

What is ATS integration?
ATS integration is a connection between your applicant tracking system and another recruiting tool that moves agreed data automatically instead of requiring manual copying. The connection can read information from your ATS, write information back, or do both, depending on the object and permissions. For a hiring team, the aim is to let recruiters work in one place, avoid retyping candidate details, and keep reporting in the ATS.
How an ATS integration works
Most ATS integrations use the applicant tracking system's API, the access route through which another tool reads or writes data. Your admin grants permission for specific actions. Reading open jobs is different from creating candidates, attaching resumes or adding notes.
Ask to see the requested permissions against the workflow you intend to run. Access should match the task: if the tool needs job details for screening, establish which details it reads and why. Have the admin review any permission the vendor cannot explain.
Separate the initial send from later updates. A candidate arriving in the right stage does not establish whether subsequent edits, stage changes or deletions travel between systems. Ask about each operation explicitly.
Name a recruiting owner for the workflow and an admin for access problems. If you are establishing an internal hiring function, include those responsibilities in your in-house recruitment plan. Decide who investigates a missing application before recruiters depend on the connection.
What moves between your ATS and another tool
Use this table as a starting point for the vendor discussion. These are usual directions to investigate, not a specification for every integration. Have the supplier confirm what your exact connection supports, including anything it cannot transfer.
| Object | Usual direction | What to ask the vendor |
|---|---|---|
| Jobs | ATS to tool | Which jobs and job fields can it read? What happens when a job closes? |
| Pipeline stages | ATS to tool | Does it read the stages for the linked job? What happens if a stage changes? |
| Candidates | Tool to ATS; ATS to tool where import is supported | Which profile fields move? How does it match an existing person? |
| Applications | Tool to ATS; ATS to tool where import is supported | How does it attach the person to the correct job, including someone considered for another role? |
| Resumes and attachments | Tool to ATS; ATS to tool where import is supported | Which files are accepted? How are rejected or missing attachments shown? |
| Notes and scores | Tool to ATS | Can recruiters read the score, screening evidence and profile link? Who can see those notes? |
| Stage moves after the first send | Varies; later updates may be unsupported | Do later moves transfer, in which direction, and which system wins if stages conflict? |
| Past candidates for search | ATS to tool, if enabled | Can we search existing candidates? Which records and resumes are copied, and can we limit the scope? |
Keep candidates and applications separate in your requirements. Test both an existing person's profile and their application to the linked job. A successful profile transfer is insufficient evidence that the application reached the correct vacancy.
ATS stage mapping: a worked example
Stage mapping assigns a destination in the ATS pipeline to a status in the recruiting tool. I'd start by separating an assessment from a process milestone: a suitable applicant has not necessarily been invited to interview.
Here is an illustrative mapping for a screening and sourcing tool. Replace the destination names with your own ATS stages.
| Tool status | ATS destination | Reason |
|---|---|---|
| Shortlisted | Hiring team review | Put the shortlist where a person can choose the next step. |
| Suitable | Screening review | Keep applicants who meet the rules available for review without implying an interview happened. |
| Not suitable | Don't sync | Keep this assessment in the tool for review before deciding on further action. |
| Sourced | Sourced prospects | Separate people found through research from people who applied. |
If sourced records are still a research list, choose Don't sync for that status too. Agree when a prospect is ready to enter the ATS as part of your candidate sourcing process.
Set the mapping with the recruiter who owns the job:
- Link the tool's job to the intended ATS job, checking more than the title.
- Choose an ATS destination or Don't sync for every tool status.
- Ask whether the destination stages have emails or other actions attached.
- Test later status changes separately from the initial transfer.
Unmapped statuses should stay out of the ATS by default. That makes adding a new status a deliberate workflow decision and prevents an unreviewed category from entering a reporting stage. If you want a fallback talent pool, approve it explicitly and include it in testing.
Questions to ask before you buy
Copy this into your purchasing brief. Ask the vendor to answer for your ATS edition and account configuration, and demonstrate the workflow with representative records.
[ ] Does this support our exact ATS, edition and account configuration?
[ ] Which objects does it read, which does it write, and which are unsupported?
[ ] Can it write resumes, attachments, notes and scores in a usable form?
[ ] How does it handle someone already in the ATS and prevent duplicates?
[ ] How often does it sync, and where do we see failures and retries?
[ ] Who can connect it, and what permissions must our admin grant?
[ ] What happens when access expires, and who gets the alert?
[ ] Can we send everyone or only chosen statuses, with a Don't sync option?
[ ] How do we link each tool job to its ATS job and change that link safely?
[ ] Do stage moves and other edits transfer after the initial send?
[ ] Can we search past ATS candidates, and can we limit what is imported?
[ ] Where is candidate data held, and what processor guarantees can you show?
[ ] Can we review the processor contract and retention and deletion arrangements?
[ ] How do we disconnect, and what data remains in each system afterward?
Distinguish features available now from work the supplier proposes to deliver. Record dependencies such as permissions or destination fields in the buying decision, so the person configuring the connection can reproduce what was demonstrated.
Candidate data in two systems: UK GDPR duties
For UK employers, assess the processing in both systems alongside the connection itself. This is general information, not legal advice.
Under UK GDPR Article 28(1), a controller must use only processors providing sufficient guarantees that appropriate measures will meet the Regulation's requirements and protect people's rights. Ask the supplier for evidence supporting those guarantees before approving candidate data access.
The processor contract required by Article 28(3) must set out the subject matter and duration of processing, its nature and purpose, the types of personal data and categories of people, and the controller's rights and obligations. Check that it describes the actual workflow, including any copying of past applicants for search.
Article 5(1)(c) requires personal data to be adequate, relevant and limited to what is necessary for the purpose. Apply that to the import scope, attachments and notes. Ask why each category needs to leave the ATS before enabling it.
Accuracy and storage limitation under Article 5(1)(d) and (e) require accurate records, kept up to date where necessary, reasonable steps to correct or erase inaccurate data without delay, and identifiable data to be kept no longer than necessary for its purpose. Build a correction and retention process covering both copies.
Assign someone to verify corrections and carry out the agreed deletion process in each system. Ask what remains after disconnection; do not treat a disconnected status as evidence that candidate records have been erased.
Test the integration in the first week
Run a live job through the agreed workflow using designated test records. Tell the recruiting team which records belong to the test, write down the expected destinations, and record evidence against these pass criteria.
| Check | How to run it | Passes when |
|---|---|---|
| Connection and permissions | Have the approved admin connect, then exercise the required reads and writes. | Required actions succeed, and requested access matches the approved scope. |
| Job linking | Link the test job and inspect the resulting application in the ATS. | The application reaches the intended job, including where titles are similar. |
| Stage mapping for each status | Send a representative record through every configured status. | Each synced status reaches its mapped stage; later changes follow the agreed rules. |
| Resume and notes arrive | Send a resume and screening output, then inspect them as a recruiter. | Supported files open and notes are readable, with the expected results attached to the correct person. |
| Duplicates | Test an existing candidate, an existing application and a repeated send. | Matching follows the agreed rules without creating unwanted duplicate profiles or applications. |
| Statuses you chose not to sync | Create records in excluded and unmapped statuses. | They stay out of the ATS, except for any fallback destination you explicitly approved. |
| Expiry and reconnection alerts | Ask the vendor to demonstrate access loss and restoration. | The named owner sees the problem, and pending transfers recover without missing or duplicate applications. |
| Reporting in the ATS still matches | Reconcile the test applications, jobs and stages with the ATS report recruiters use. | The report reflects the expected applications and stages, including excluded records staying out. |
For attachments or notes the integration does not support, decide whether the remaining record is sufficient for a recruiter to work from. Document that limitation before sign-off. An unexplained missing resume should fail the check.
Alongside the transfer tests, correct a test record and run the agreed deletion process. Verify the result in both systems. Hold wider use until failed checks have an owner, a fix and a successful retest.
What an AI recruiting tool adds to the integration
Screening, scoring and first-round interviews happen in the AI recruiting tool. The integration carries supported results into the ATS so it remains the hiring record. Specify what the reviewer needs there: an assessment, supporting evidence and access to the fuller record where available.
Define the rules before deciding where scores should land. The AI candidate screening guide includes a screening rule template. Use the guide to AI recruitment tools to decide which sourcing, screening and interview tasks belong in your trial.
Keep every hiring decision with a person on the hiring team. Map results to a review stage that makes the next human action clear.
How Alfa fits
In Alfa AI, Lisa screens applicants against the job's rules and runs first-round AI Interviews. A human on the hiring team always reviews each AI Interview and decides the next step; Lisa never rejects anyone.
An Owner or Admin connects the ATS in Settings under ATS integrations by signing in and approving access. Only one ATS can be connected at a time. The team links each job to its matching ATS job and maps Shortlisted, Suitable, Not suitable and Sourced potential candidates to ATS stages.
Every status starts as Don't sync. An optional fallback ATS job can receive applicants whose status is not synced, so include that choice in your checks.
After screening, each candidate is sent to a job once, with their resume where the ATS accepts it. Where notes are supported, the send includes the score, screening results and a profile link. Copying past ATS candidates, applications and resumes for search is optional. Connecting the ATS does not email anyone, and syncing sourced candidates does not start outreach.
The settings show connection status, the last sync time and recent sync history. Owners and Admins receive an email if access expires or a missing permission causes applications to be refused. Waiting applications are sent once the permission is granted.
What each integration supports differs by system. The ATS integrations page lists what each connection reads and writes, how to connect it, its limits and when it was last verified. Use the entry for your ATS to complete the checklist before configuring your mappings.
Frequently asked questions
- What is ATS integration?
- ATS integration is a connection between your applicant tracking system and another tool, such as a job board, sourcing, screening, interview or HR system, so that jobs, candidates, stages and documents move between them automatically instead of being copied by hand. Put the agreed purpose in your purchasing brief so stakeholders can judge the same outcome.
- How does an ATS integration work?
- Most ATS integrations use the applicant tracking system's API: the other tool signs in with permission your admin grants, reads what it needs, such as open jobs and pipeline stages, and writes back what it is allowed to, such as new candidates, resumes and notes. Give the admin your intended workflow so they can assess the requested access in context.
- What data does an ATS integration sync?
- It depends on the integration, but the usual objects are jobs, pipeline stages, candidates, applications, resumes and other attachments, and notes, and each one can flow in one direction, both directions or not at all. For a custom field you depend on, request a demonstration using its actual name and values; a general claim about candidate profiles is insufficient.
- Is ATS integration one-way or two-way?
- Many are a mix: a tool may only read jobs and stages from your ATS but write candidates back to it, so ask which direction each object moves before you assume the two systems stay in step. If you only need completed screening results sent across, specify that handoff explicitly instead of requesting updates to every field.
- Who owns candidate data when two systems are connected?
- Under UK GDPR your company is usually the controller of the candidate data in both systems, and a vendor processing it on your behalf must work under a written contract that sets out what it processes, why and for how long. For an agency handling data for clients, ask your data protection adviser to confirm the roles for the actual arrangement before adopting that assumption.
- What should I test before switching an ATS integration on?
- Run one live job end to end and check that the job links correctly, each status lands in the stage you mapped, the resume arrives, nobody is duplicated and nothing reaches your ATS that you chose not to sync. Include the recruiter who will use the output in the sign-off, and ask them to complete their next hiring task from the resulting ATS record.

