AI active sourcing with your ATS: how shortlists get into Greenhouse, Personio, Lever and more

Sourced candidates get into Greenhouse, Personio, Lever or SmartRecruiters in one of three ways: through the system's API, through a webhook-driven sync, or through an import file. The technical route is the easy part. What decides whether your ATS stays clean is how you record the person (as a prospect, not an applicant), how you match duplicates, and when you send the GDPR Article 14 notice. Sprad's active sourcing is connected to Ashby, d.vinci and Personio today; any other system with an API can be connected, and the scope per system is something we clarify in a conversation rather than promise on a page.

Three routes from a sourcing tool into your ATS

Every integration, whoever builds it, uses one of these:

• API push. The sourcing tool creates the person in the ATS through its REST interface. This is the route for shortlists that arrive continuously.
• Webhook plus API (two-way). The ATS tells the sourcing tool when something changes (stage moved, person rejected), and the tool updates its own side. Without this, you contact people your ATS has already closed.
• Export and import. A spreadsheet or ATS export goes in, a file comes out. Slow, but it works with any system and is a sensible way to start or to load an existing pool once.

Sprad connects in both directions with the ATS or CRM you already run; nothing has to be replaced. There is also an open API with webhooks, and importing Excel and ATS exports is free. In our conversations with recruiting teams, the pool is usually a spreadsheet plus a folder of CVs.

What your ATS offers, and where Sprad stands

The table lists what each vendor documents publicly (according to the developer documentation of each vendor, as of 5 November 2026) next to the state of the Sprad connection. "Not documented" means we found nothing reliable, not that the feature does not exist. The vendors' own pages are not linked here.

Where a vendor documents webhooks, a two-way flow is realistic. Where only a read interface or a closed partner programme exists, expect an export or a vendor release.

Prospect or candidate: how sourced people should land

A sourced person has not applied. Most ATS distinguish between a prospect (a person in a talent pool or CRM view, not tied to a job) and a candidate (a person in a job's pipeline). Greenhouse documents exactly this split in its help centre (checked 18 October 2026).

Our recommendation, whichever ATS you use:

1. Create sourced people as prospects in a pool with a clear name ("Data engineers DACH").
2. Set a source value at creation (for example "Sourcing - Sprad"). It cannot be reconstructed afterwards.
3. Move the person into the job pipeline only after a positive reply.
4. Close the record when the person declines or stays silent after your last follow-up, so nobody is contacted twice.

Otherwise the pipeline fills with people who never agreed to anything and stage conversion rates fall.

Duplicates: decide the matching rule before the first import

Duplicates come from three places: the same person applied earlier, a colleague sourced them last year, or two tools found the same profile. Agree one rule in writing:

• Primary key: email address. If none exists, match on name plus profile URL, and have a human confirm.
• If a match exists: do not create a second record. Add a note and the source to the existing one, and check whether a reply or objection is already on file.
• Before outreach: check the ATS first. A person who was rejected two weeks ago should not receive a cold message today.

In our conversations, double outreach is a real problem for firms with several recruiters, and it is exactly the case a shared ATS record prevents, provided the sourcing tool reads it before it writes.

GDPR: Article 14 starts when you hold the data

If you source someone from a public profile or a data provider, you did not collect the data from them. Article 14 GDPR then requires you to inform the person about who you are, why you process the data and where it came from. The deadline is a reasonable period, at the latest one month (Art. 14(3)(a)), or at the latest at first contact if you use the data to write to them (Art. 14(3)(b)). The exceptions in Art. 14(5) should not be your plan for individual outreach.

A common legal basis is legitimate interest under Art. 6(1)(f), which needs a documented balancing test, and the person can object (Art. 21). When you wire a sourcing tool to your ATS, settle these points:

• Who sends the notice and in which message: put the controller, the source and the objection route into the first message.
• Retention: set a deadline for prospects who never reply and let the ATS delete on schedule. In our conversations, teams that want an up-to-date pool fear "data corpses" more than anything else.
• Source on record: you must be able to name where you found the person.
• Objection: removing the profile must stop the outreach cadence in the same step.
• Talent pool opt-in: rejected candidates who agree can be invited into your talent pool (Art. 6(1)(a), documented consent). Do not move them there silently.

Our guide to GDPR in active sourcing goes deeper. This is general information, not legal advice; your data protection officer decides the details.

Works council and AI rules in DACH

If a works council exists, a sourcing or screening tool that can monitor behaviour or performance falls under co-determination (§ 87(1) no. 6 BetrVG). The employer must inform the council early about AI use (§ 90 BetrVG), and selection guidelines require its consent (§ 95 BetrVG). The AGG applies to sourcing as much as to applications. Decisions based solely on automated processing are restricted by Art. 22 GDPR, which is why a shortlist must be an input for a recruiter, not a verdict. Under the EU AI Act, the high-risk duties for recruiting AI (Annex III) apply from 2 December 2027 according to Regulation (EU) 2026/1744; the prohibitions of Art. 5 have applied since 2 February 2025.

ATS sourcing module or a separate tool?

Many ATS offer their own sourcing module or add-on. It keeps everything in one system and avoids an integration. It usually covers campaigns, contact lookup and tracking for people you already identified; finding and qualifying them is a different job. A separate sourcing tool searches and checks profiles, then writes results into the ATS. Which fits depends on where your bottleneck is. We compare both in sourcing tool vs. ATS module.

Questions for your ATS team and every vendor

1. Data flow: Which objects are written (person, note, tag, source, stage), and in which direction? Is anything read back, such as rejections?
2. Record type: Are people created as prospects or candidates, in which pool and stage?
3. Rights: Which API permissions are required, and can they be limited?
4. Duplicates: How is an existing email handled? Is a second record ever created?
5. Controller and processor: Who is controller, who is processor, and is a processing agreement (Art. 28 GDPR) in place for each tool?
6. Notice and deletion: Who sends the Art. 14 notice, when, and what is deleted if someone objects?
7. Impact assessment: Is a data protection impact assessment (Art. 35 GDPR) needed for your use?
8. Works council: Has it been informed and does it agree?
9. Exit: Can you export everything, including sources and notes, if you leave?

A worked example: 400 sourced profiles a month

Assumptions (replace them with your own): a team sources 400 profiles a month. Entering a profile by hand, with a duplicate check, takes 5 minutes; a recruiter costs 60 € per hour fully loaded. That is 400 × 5 min = 33 hours, or about 2,000 € a month spent on copying, before a single message is sent. Sprad prices an ATS connection at 100 credits per connection as a licence add-on (as of 29 October 2026); it is included in Atlas Base Pro and Max, and with Atlas Recruiter from three licences.

How Sprad fits

Sprad searches LinkedIn, XING, GitHub and your own pool, checks each profile with AI, and puts LinkedIn and email outreach into one inbox. The connection runs in both directions with your ATS. It is already built for Ashby, d.vinci and Personio; other systems with an API, such as Greenhouse, Lever or SmartRecruiters, can be connected over the system's interface, with the scope per system clarified in a conversation. Which results your ATS should receive back is covered in what to write back into your ATS.

sprad.io/product/people-search

Sprad Active Sourcing page, screenshot sprad.io, status November 2026.

FAQ

Can I add sourced candidates to my ATS automatically?

Yes, if the ATS has an API and the tool is connected to it. Create them as prospects with a source value and let a person decide on the next step.

Does Sprad work with Greenhouse, Lever and SmartRecruiters?

Sprad is connected to Ashby, d.vinci and Personio. Any other system with an API can be connected; we clarify the scope for Greenhouse, Lever or SmartRecruiters in a conversation. We do not promise specific fields or stages on this page.

How do I avoid duplicates?

Match on email first, then name and profile URL, check the ATS before outreach, and never create a second record for a match.

When must I inform sourced people under GDPR?

Under Art. 14, at first contact if you write to them, otherwise within one month. Name the controller, purpose and source.

Can I keep rejected candidates in a talent pool?

Only with a legal basis, typically their consent, and a deletion deadline. Invite them; do not move them silently.

Is an ATS sourcing module enough?

If your bottleneck is campaign execution for people you already found, often yes. If it is finding and qualifying them, add a search tool.

What does an ATS connection cost with Sprad?

100 credits per connection as a licence add-on; included in Atlas Base Pro and Max and with Atlas Recruiter from three licences (pricing, as of 29 October 2026).

Sprad is built so that your ATS stays your system of record. Sourcing across LinkedIn, XING, GitHub and your own pool, checked profile by profile, lands in your existing process instead of a second tool you have to feed by hand. The talent pool stays yours, so leaving any platform does not cost you your reach. You can start with the free account (100 credits a month), and Atlas Base at 450 € a year includes 5,000 credits; see pricing. To see the flow with your own ATS, start with active sourcing with Sprad.