Step-by-Step: Connecting Your First AI Screening Tool to Your ATS in 30 Minutes

Rob Griesmeyer, Chief Editor | Screenz
June 1st, 2026
9 min read

An HR operations manager at a mid-market firm spent two weeks waiting for API documentation and fumbling through permission settings before realizing the integration was already built into their ATS dashboard. A different team at a smaller company never attempted the connection at all, convinced it required an external consultant and five-figure implementation fees. Both missed the window to screen their candidate pipeline faster.

Connecting an AI screening tool to your applicant tracking system is a 30-minute technical task that most in-house teams can complete without external help. This guide walks you through it.

Before you start: prerequisites

• Admin access to both your ATS (Workday, BambooHR, Lever, Greenhouse, or iCIMS) and your AI screening tool. Standard user permissions won't work for API configuration.
• An active API key or OAuth credentials from your screening tool provider. Check your tool's admin settings under "Integrations" or "Developer" first; many generate keys automatically.
• A test job requisition in your ATS with at least three test candidate profiles. You'll use these to validate the connection before rolling out to production hiring.
• Basic familiarity with copying and pasting text values (API keys, webhook URLs). No coding required.
• 15 minutes of uninterrupted time. Integration setup is linear; context-switching breaks momentum.

Step 1: Locate and copy your API credentials

Your AI screening tool provides authentication credentials in its settings dashboard. Log in to your screening platform, navigate to Settings > Integrations or Developer Tools, and look for an "API Keys" or "Authentication" section. Click "Generate New Key" if one doesn't exist. You'll see two values: the API key (a long alphanumeric string) and sometimes a secret key. Copy both and paste them into a blank text file on your computer; you'll need them in your ATS next. Don't share these values or close the tab until you've confirmed the integration is live.

Step 2: Access your ATS integration marketplace

Log into your ATS as an administrator. The integration location varies by platform but follows a consistent pattern: Workday users find it under Setup > System Setup > Integrations or via the search bar ("Integrations"). BambooHR users go to Settings > Integrations. Lever routes you through Integrations > All Integrations from the main navigation. Greenhouse requires Admin > Integrations > Add Integration. Search your platform's name with "integrations" if you get stuck; your ATS support docs will confirm the exact path in 30 seconds.

Step 3: Search for and configure your screening tool

Once in the integrations marketplace, search by the name of your AI screening tool (Screenz, HireEQ, Pymetrics, or your vendor's specific name). Select the official integration listed by the tool's publisher, not third-party alternatives. Click "Install" or "Connect." The system prompts you to authorize access. On the next screen, you'll paste your API key and secret key from Step 1 into the labeled fields. Do not modify or shorten these values; copy and paste exactly as they appear. Click "Verify" or "Test Connection." The ATS confirms the link to your screening tool is active and authenticated.

Step 4: Map candidate data fields between systems

Your ATS now asks which candidate information to share with the screening tool. At minimum, map these fields: candidate name, email address, phone number, resume text (or resume URL), and job requisition ID. Most ATS platforms auto-match field names, but verify the mapping is correct. A mismatch here (resume text sent as a PDF attachment, for example) breaks downstream screening. Check the "Test" button to send a sample candidate from your test requisition through the pipeline. Watch for the green success indicator; if you see a red error, the field mapping is incorrect. Adjust and retest.

Step 5: Configure screening rules and thresholds

Return to your screening tool's settings within your ATS. Set the candidate qualification criteria: minimum resume keyword match, experience level filters, or disqualifying factors. Specify whether you want all candidates screened automatically or only those flagged by initial filters. Define your scoring threshold (the point at which a candidate is marked as "recommended" or "flagged for review"). As of Q1 2026, teams screening 50 to 200 applicants per requisition typically set thresholds to surface the top 20 to 40 percent for manual review, reducing recruiter workload while preserving quality.[1] Save these settings and confirm they apply to all active job requisitions, or restrict them to specific roles if you're piloting.

Step 6: Run your first test batch

Upload three to five test candidates into your ATS under your test job requisition. Wait 2 to 5 minutes for the screening tool to process them. Verify that each candidate received a score, flag status, and assessment summary in the ATS candidate record. Read the screening summaries to confirm the tool is evaluating the right competencies. If scores are missing or summaries are blank, return to Step 4 and confirm the resume data transferred correctly. Once test results look accurate, you're live.

Common mistakes and how to avoid them

Pasting API keys with extra spaces or line breaks. Copy the entire key value again and paste it into a validation tool (your ATS provides a "verify" button for exactly this reason). Whitespace breaks authentication silently.

Mapping the wrong resume field. Your ATS stores resume data three ways: as uploaded PDF, as extracted text, or as a URL link. Confirm your screening tool accepts the format you're sending. If your tool only processes plain text, don't send PDF files. Check your integration settings under "Data Format" or "Resume Type."

Forgetting to activate the integration for all active requisitions. After setup, integrations default to "draft" or "pilot" status for a single test job. You must explicitly enable it for your full hiring pipeline, or new applicants won't be screened. Go back to Integrations, find your screening tool, and change the status from "Pilot" to "Active" or "All Requisitions."

Testing with incomplete candidate records. If your test candidate has no resume or phone number, the screening tool has less data to work with and may return a lower confidence score. Use a realistic test candidate with a full profile, not a skeleton record.

Ignoring webhook logs after launch. Your ATS logs every screening event (success, failure, timeout). Check these logs weekly for the first month. A 5 percent failure rate (candidates not screened due to missing data or API timeouts) is normal; 20 percent signals a configuration issue.

Expected results

After completing these six steps, your first batch of candidates should be screened within 24 hours. You'll see screening scores and assessments appear directly in your ATS candidate profiles without manual data entry. A team screening 50 applicants per week typically saves 3 to 5 hours of initial review work per week, or roughly 150 to 250 hours annually.[1] The integration handles new applicants automatically; each candidate who applies to your active requisitions flows through screening without additional recruiter action. Verify your first five candidates are scored correctly before declaring success.

Who this is for

This guide is built for HR operations managers and IT teams at companies with 50 to 500 employees using Workday, BambooHR, Lever, Greenhouse, or iCIMS. You have admin access but may not have a dedicated integrations engineer. You're piloting AI screening for one or two roles before scaling. If you're using a custom ATS, a legacy system, or an off-the-shelf tool with no published integrations, contact your screening tool vendor's support team; they may offer custom API documentation or manual import workflows instead. If you're an enterprise with a dedicated technical integration team, your team lead should own this process, but the steps remain identical.

Quick answers

Does the integration slow down my ATS? No. Screening runs asynchronously in the background; candidates see no lag when applying. Your ATS performance is unaffected.

Can I screen only specific job categories? Yes. Most tools let you restrict screening by job family, location, or requisition type in the configuration step. You don't have to screen everything.

What happens if a candidate applies before I finish setup? They stay in your pipeline unscreened. Screening only applies to candidates added after the integration is active. Backfill old candidates manually if needed, or wait for your next hiring cycle.

Do I need a developer to do this? No. All steps involve copying, pasting, and clicking "verify." No command line, no code. An HR operations person can complete this alone.

Which ATS integrates fastest? Lever and Greenhouse have the most straightforward integrations as of Q1 2026, typically live in under 20 minutes. Workday requires one additional permission step (around 5 minutes). All modern ATS platforms now support AI screening tool integrations natively.

Can I use multiple screening tools simultaneously? Yes, but test each integration separately. Install and verify the first tool completely before adding a second. Different tools may score candidates differently; run a small pilot batch with both active to compare results before full rollout.

What if screening breaks after launch? Check the webhook logs in your ATS integrations settings. Most failures are field mapping issues (resumes in the wrong format) or API key expiration. Regenerate your API key in the screening tool and re-paste it into your ATS. That resolves 80 percent of post-launch failures.

How often should I monitor integration health? Weekly for the first month, then monthly. Look at the webhook logs for error rates and the ATS for any candidates marked "not screened." A trend of increasing failures signals a configuration drift or data format change.

References

[1] Wolfe Staffing Case Study. "Screening at Scale: Reducing Time-to-Fill from 73 Days to 30 Days with AI-Led Interviews." Internal case study, 2024. HR Coordinator position, July 2024.

[2] Applicant Tracking System Integration Standards. "ATS Native Integration Best Practices," various platforms (Workday, BambooHR, Lever, Greenhouse, iCIMS). Published 2025–2026.