Setting Up SeekOut With Your ATS: Common Problems, Sync Direction and Fixes (2026)

Most SeekOut ATS problems start before the first sync. It could be a missing permission, an IP address that was never whitelisted or two logins using different email addresses. Custom hiring stages never get mapped. The connection then looks finished, while candidate data stops short of where recruiters need it.

This guide covers what goes wrong with Workday, Greenhouse, iCIMS and the other ATS platforms SeekOut connects to. It explains which way candidate data moves in each integration mode, and how to fix the problems teams hit most often. It focuses on the reasons behind each step and the usual failure points. For click-by-click instructions, use SeekOut’s help center articles for each ATS. Those pages change when screens change, so treat them as the source of truth.

What goes wrong when teams set SeekOut up with their ATS in 2026?

Our recruiting tools all work with your ATS: SeekOut Sourcing (formerly SeekOut Recruit), SeekOut Applicant Evaluation and SeekOut AI Screening, and SeekOut Candidate Integrity. AI recommends with the reasoning shown; your recruiters set the bar and make the calls, and nobody is auto-rejected. None of that works well if the ATS connection is half-finished.

Watch for these five problems:

• Missing access. The integration user lacks a permission, or the credentials belong to a person who later changes roles.
• Blocked network traffic. iCIMS won’t accept SeekOut traffic until iCIMS whitelists SeekOut’s IP addresses.
• Mismatched identities. For Greenhouse, your Greenhouse login and your SeekOut login must use the same email address.
• Duplicate or unmatched candidates. Each ATS has its own rule for spotting the same person twice, and some have none.
• Unmapped stages. Custom stage names that aren’t mapped drop out of pipeline views and funnel reporting.

Each one is easy to prevent and slow to diagnose later. The sections below explain the cause of each problem and the fix.

Want to explore SeekOut Sourcing while your integration is set up? Start a 14-day free trial. No credit card is required.

What is a SeekOut ATS integration?

A SeekOut ATS integration connects SeekOut with your applicant tracking system (ATS) or recruiting CRM, allowing candidate and job data to move between the platforms. SeekOut offers two-way sync with major ATS platforms, including Workday, Greenhouse, iCIMS, and Lever. The help center covers many more, and SeekOut also builds custom integrations on request.

The connection matters because your ATS already holds a large share of your best talent. SeekOut data shows 44% of great hires were already in the company’s ATS, as published on SeekOut’s talent rediscovery page. Rediscovery can only reach those people when the integration is live and complete.

It also changes what recruiters see. In SeekOut Workspaces, the Candidates tab and the Pipeline tab only appear when SeekOut is connected to your ATS. Candidates who reply to your outreach are added to the Candidates tab and linked to the open role in your ATS.

The Pipeline tab needs one more step: the Workspace must be linked to an ATS role during setup. If the tab is missing, check that link before you assume the integration failed.

Which direction does SeekOut sync candidate data with your ATS?

The direction depends on the integration mode, not on the ATS. Each mode moves different data, and many teams run more than one.

Export only sends data into your ATS. Rediscovery mirrors your ATS data into SeekOut every day and adds social links, work history and education. Applicant Review imports jobs and applicants, then sends stage changes back. Knowing which mode you’re running is the first step in any troubleshooting.

SeekOut’s 3 ATS Integration Modes Explained

SeekOut supports three ATS integration modes, each serving a different part of the recruiting workflow. Here’s how they work and what recruiters can do with each one.

Export: from SeekOut into your ATS

Export sends candidate data from SeekOut to your ATS or CRM, creating a profile with contact details, work history and education. You can export candidates as prospects or attach them to a specific job.

By default, SeekOut won’t export a candidate it has already exported successfully, helping prevent duplicates. Exported profiles show a confirmation icon and the ATS name, making it easy to identify completed exports. To send someone again, select “Include previously exported candidates” in the export pop-up. Use this option with care, as it can create duplicate records.

Syncing times vary. For Greenhouse Export, the help center notes that syncing can take up to four hours during peak hours (8 a.m. to 10 p.m. ET). So, a candidate who doesn’t appear immediately isn’t necessarily the result of a failed export.

Talent Rediscovery: your ATS, searchable inside SeekOut

Talent Rediscovery connects applicant and prospect records in your ATS with SeekOut’s data, letting recruiters search both using keywords, Boolean queries and filters. SeekOut mirrors ATS data daily and enriches it.

The initial download takes the longest. For Greenhouse and Workday, the help center says the first import can take several days, depending on the number of candidates and jobs. After that, SeekOut periodically checks the ATS and pulls only changed data. These updates take minutes to hours, while the Workday candidate index updates every four hours.

ATS-specific filters appear in purple in SeekOut search. They only show when you search your ATS candidates, and they depend on the data SeekOut receives. If no candidate in your ATS sits in a given stage, that stage filter won’t appear at all. Missing filters usually mean missing data, not a broken connection.

Applicant Review: ATS jobs and applicants inside SeekOut

Applicant Review pulls open jobs and their applicants from your ATS. SeekOut then displays, filters, enriches and ranks them for each requisition. The help center documents Applicant Review for Greenhouse, iCIMS Stream and SmartRecruiters.

Stage changes also flow back. When a recruiter uses the Move to Stage button on an applicant’s profile, the change reaches your ATS within 15 minutes. The stages listed come from your ATS, so stage names in SeekOut should match what recruiters already know.

SeekOut Applicant Evaluation connects to your ATS in a similar way. It evaluates every applicant against your criteria as they apply, with a plain-language explanation for each score. To see the candidate side of SeekOut AI Screening, take a sample AI screening interview.

How do the three modes work together?

Many teams run all three, and each covers a different part of the funnel. A recruiter might search rediscovered applicants for a new role first, since those people already know your company.

Next, the recruiter sources new candidates in SeekOut and exports the strongest ones to the job in your ATS. Applicants who come in through your careers page show up in Applicant Review, ranked for that requisition. When a recruiter moves one of them forward, the stage change lands back in the ATS.

Each mode has its own setup and its own failure points. Export depends on matching rules and email. Rediscovery depends on a complete first import and on clean stage data. And the review mode depends on your ATS being one of the documented platforms.

Set up one mode at a time, test it on a real role, and add the next only when the first one works. That order makes any later problem much easier to trace.

What should TA teams look for in a SeekOut ATS setup?

Look for five things before you call the integration done. Each one matches a common failure point in the help center’s setup guides, and each is quick to confirm up front.

1. Access that doesn’t depend on one person. Integrations can stop working when they’re tied to the credentials of someone who leaves the company or changes roles. Greenhouse recommends creating Harvest v3 API credentials with an integration system user instead of using a personal account. This keeps the integration running even if that person’s account is deactivated. Greenhouse offers these credentials on its Core, Plus and Pro tiers. Workday uses a dedicated Integration System User (ISU) for the same reason. On the SeekOut side, the Integrations menu must be enabled for your organization. If an admin can’t see it, your Customer Success Manager (CSM) or SeekOut support can enable it.

2. Network rules cleared in advance. iCIMS requires SeekOut’s IP addresses to be whitelisted for both Export and Talent Rediscovery. Your team asks iCIMS to do this. For Workday Rediscovery, whitelisting is optional. For Greenhouse, it only matters if your organization restricts API access by IP address, in which case SeekOut support can share its list.

3. Matching rules you understand. Each ATS decides what counts as the same person, and the rules differ a lot. Some match on email address alone. Workday’s API doesn’t match at all. SeekOut’s own default helps, because it skips candidates it has already exported. Learn your ATS’s rule before anyone overrides that default with “Include previously exported candidates.”

4. Stage mapping that mirrors your funnel. SeekOut translates custom ATS stage names into eight standard categories. Unmapped stages vanish from pipeline views and skew reporting. An Org Admin should review the mapping before the first full sync.

5. Security and data handling your IT team can sign off on. ATS data includes personal information, so IT will ask how it’s protected. SeekOut is SOC 2 Type II certified and GDPR compliant, supports DPAs, encrypts customer data with AES-256, and runs on Microsoft Azure with annual third-party penetration testing. Its AI undergoes regular third-party bias audits, and its evaluations use no protected-class signals.

SeekOut supports bias audits and explainable scoring but does not guarantee compliance; confirm your obligations with counsel.

How can TA teams set SeekOut up with Workday, Greenhouse and iCIMS?

Follow these six steps in order and you’ll avoid most rework. Each step covers what to do, the ATS-specific detail that matters, and the mistake teams make most often. The per-ATS help articles hold the full instructions.

Step 1: Confirm the Integrations menu and choose a mode first

Check that the Integrations menu appears in SeekOut. If it doesn’t, ask your CSM or SeekOut support to enable it.

Then decide which modes you need: Export, Talent Rediscovery, Applicant Review, or a mix. Your own admin can connect Export from the Integrations settings. For Rediscovery on Workday, Greenhouse and iCIMS, the help center asks you to contact your CSM or SeekOut support so they can coordinate the setup. Start that conversation now to keep go-live dates realistic.

Step 2: Complete the ATS-side prerequisites

Workday setup centers on an Integration System User (ISU). For Export, you run Create Integration System User, clear “Require New Password at Next Sign In,” and set Session Timeout Minutes to 0. Next, you add the ISU to an Integration System Security Group (Unconstrained), and give it access to the Put_Candidate and Get Job Postings APIs. The Workday article lists five permissions to add. Then run Activate Pending Security Policy Changes, or nothing takes effect.

Two details are easy to get wrong. First, the service endpoint must be copied from the Recruiting (Public) WSDL exactly, including the trailing slash. Second, the tenant name is the text between the two slashes after “workday.com” in your Workday URL, without the slashes. The setup guide also has you add the ISU to the “System User exempt from password expiration” list through the Maintain Password Rules task. Don’t skip it, or the integration’s password can expire.

Keep one limit in mind. Workday offers no duplicate check through its API, so a second export of the same person produces a second Workday profile.

Step 3: Connect Export and verify it

Workday. Enter two values exactly as shown:

• Service endpoint: copy it from the Recruiting (Public) WSDL, including the trailing slash.
• Tenant name: the text between the two slashes after “workday.com” in your Workday URL, without the slashes.

Greenhouse. In the Dev Center, create Harvest v3 (OAuth) credentials and enable the scopes SeekOut needs, such as Candidates, Jobs and Prospect pools. Copy the client secret before you close the window, because Greenhouse shows it only once.

iCIMS. Select the Export capability, enter your iCIMS credentials and job portal URLs, and connect. SeekOut sends a test candidate to verify the link. Confirm it appears in iCIMS before you export real people.

Step 4: Set up Rediscovery (and Applicant Review) with your CSM

Rediscovery setup is coordinated by your CSM or SeekOut support. Here’s what each ATS needs from your side.

Workday. Rediscovery uses a Core Connector: Candidate Outbound integration that delivers files to SFTP hosted by SeekOut.

The connector needs the Delivery Service and Sequence Generator Service, plus Get and Put access to the Integration Build domain. The security group needs Get permission on five web services: Get_Candidates, Get_Candidate_Attachments, Get_Job_Requisitions, Get_Job_Postings and Get_References. IP whitelisting is optional here.

Greenhouse. Rediscovery uses a Harvest API key plus ten webhooks. Your CSM or SeekOut support provides the webhook endpoint URL, secret key and error email. On a large instance, plan for the first import to take several days. After that, only changed records sync. Greenhouse is also documented for Applicant Review, so inbound applicants can be ranked in SeekOut, with stage changes written back.

iCIMS. For iCIMS Stream Rediscovery, iCIMS support supplies a longer credential list: Client ID, Client Secret, Stream ID and Subscription ID. Your CSM coordinates the rest. The iCIMS help article covers both Export and Rediscovery.

Step 5: Plan for duplicates and email handling

Each ATS handles duplicates differently, and the differences decide whether you end up with clean records or manual merges.

Workday: There is no duplicate check through its API, so a second export of the same person creates a second Workday profile.

iCIMS: Duplicates are checked by email address only, and a candidate needs an email to export. Recruiters can use Get Email on a profile, or Get Email for All in a project, before exporting. A “Generate dummy email addresses for candidates” option exists for profiles without one, but use it carefully: a later export under a different or dummy email creates a separate profile. When the same email is exported twice, iCIMS updates the profile but not its work experience or education.

Beamery: SeekOut strongly recommends getting a candidate’s email before exporting. Beamery only checks duplicates when an email was exported, so without one it can create several records for the same person until someone merges them by hand.

Other platforms: The help center also documents Rediscovery for Ashby, Jobvite, Lever, SAP SuccessFactors and SmartRecruiters. Each has its own article, with its own credentials and filters. For example, Jobvite data is imported every day, and its filters include application type, candidate status, requisition, source, recruiter and last-updated date. The overall pattern is the same, but the credentials differ, so read the article for your ATS before you start.

Step 6: Map stages before the first full sync

Every ATS names stages its own way. SeekOut reads each stage name and places it in one of eight standard categories: Applied, Screen, Hiring Manager, Interview, Offer, Hired, Rejected and Ignore. “HM Review Completed” belongs under Hiring Manager. “Phone Screen Passed” maps to Screen. Test or system entries, such as “System Log Entry,” go to Ignore.

Gaps here are costly. Unmapped or mismapped stages can leave candidate data incomplete, put people in the wrong stage, or keep them out of the Candidates and Pipeline tabs. Stage mapping also drives funnel analytics and ROI reporting, including the hiring metrics your CSM reviews in Quarterly Business Reviews.

Only Org Admins can change the mapping. Open the profile menu in the lower-left corner, select Stage Mapping, and use the “Map To” dropdown to reassign a stage. Changes apply right away to new candidate activity, so earlier activity keeps its old category. That’s why mapping before the first full sync saves cleanup later.

How should TA teams evaluate a SeekOut ATS integration before go-live?

Start with one live requisition and test every mode you plan to run on it. If the connection handles one real role cleanly, rolling it out to the rest carries far less risk. A short pilot covers the essentials:

• Export a few candidates and confirm they arrive with the right job attached. For iCIMS, check the test candidate SeekOut sends during setup.
• Export one test candidate twice, using “Include previously exported candidates,” to see how your ATS handles duplicates.
• Search your rediscovered applicants and confirm the purple filters match the stages in your ATS.
• If you use Applicant Review, move one applicant with Move to Stage and confirm the change reaches your ATS within 15 minutes.
• Open the Pipeline tab and compare it with the ATS itself.
• Tell recruiters what delays to expect, such as the first Rediscovery import taking several days.

Keep a short record of what you tested so the next admin can repeat it after an ATS upgrade.

Who should own the integration after go-live?

Name one owner on each side. On your team, that’s usually the ATS admin plus a SeekOut Org Admin, sometimes the same person. On SeekOut’s side, it’s your CSM, with SeekOut support behind them. Write down who holds the API credentials, who can edit Stage Mapping, and which modes are live. That short record turns most future issues into a quick check instead of an investigation.

How do you troubleshoot a SeekOut ATS integration after go-live?

Problems after launch are rarely loud. The integration still looks connected, but data stops short somewhere. Start with the symptom, then check the most likely cause.

For Greenhouse, the purple filters include Application Type, Stage, Status, Job, Requisition, Rejection Reason, Source, Recruiter and Last Updated. A filter for a field nobody fills in stays empty, so check the data in Greenhouse before you assume the sync broke. If a fix needs SeekOut’s side, contact your CSM or SeekOut support. Tell them the mode, the ATS, the symptom and when it started. That shortens the back-and-forth.

What should you check after an ATS upgrade or an admin change?

Integrations tend to break at handoffs, not on ordinary days. Three moments deserve a quick review:

• An ATS upgrade or a change to your ATS security model. Permissions, domains and API scopes can shift. Recheck the permissions listed in the help center article for your ATS, then run one test export.
• An admin change on either side. When the person who owned the integration leaves, confirm who holds the credentials now, and that someone still has Org Admin rights for Stage Mapping.
• A new stage in your hiring process. Each new stage name needs a mapping, or it drops out of pipeline views. Add stage mapping to your checklist whenever your hiring process changes.

When should TA teams choose SeekOut for ATS-connected recruiting?

Choose SeekOut when you want your ATS to be a source of candidates, not just a system of record. SeekOut searches your past applicants alongside new talent, scores applicants as they apply, and writes stage changes back to your ATS.

Once the connection is solid, it carries into the AI tools your company already uses. SeekOut MCP brings SeekOut into Microsoft 365 Copilot, ChatGPT, Claude, Gemini, and Amazon Quick. ATS actions there work only when your organization has a supported ATS integration set up, and the recruiter can access the destination requisition. By default, nothing writes to your ATS without asking first.

For teams that want more of the legwork handled, the SeekOut AI Coworker is in early access. It reads the req, your notes and the hiring manager’s feedback, builds the sourcing plan, and drafts outreach in each recruiter’s voice. The AI recommends; recruiters decide.

Want help with your ATS setup? Book a demo. To explore sourcing on its own, start a 14-day free trial of SeekOut Sourcing.