Employee referral software with ATS integration: Greenhouse, Workday, Personio and more

A referral program connects to your ATS in four places: it imports open jobs, creates each referral as an application tagged with its source and the referring employee, mirrors the application status back so the referrer sees progress, and triggers the bonus when the ATS records a hire. Greenhouse, Workday, Personio, SAP SuccessFactors, SmartRecruiters and others all expose some of this through an API, but the scope differs a lot per system. Sprad is connected to Ashby, d.vinci and Personio today; other systems with an API can be connected, and the scope per system is clarified in a conversation (as of 5 November 2026).

What a referral tool has to exchange with your ATS

Most referral programs do not fail because the ATS cannot store a referrer field. They fail because one of these five flows is manual, and someone in HR ends up retyping data or answering "what is the status of my candidate?" by email.

1. Jobs in: open roles come from the ATS, so employees only see positions that are actually open and recruiters maintain a role once.
2. Referral out: the referred person arrives in the ATS as an application, with the channel "employee referral" and the referring employee attached.
3. Status back: stage changes in the ATS are mirrored to the referrer ("interview scheduled", "not moving forward"), in neutral wording.
4. Bonus trigger: the hire (and, if you want, the end of the probation period) is read from the ATS; the tool tracks points and bonus, your payroll pays them.
5. Reporting: hires, time to hire and cost per hire by source, taken from the ATS record, not from a second spreadsheet.

If your ATS cannot do one of them, the honest fallback is a scheduled export or import. That works, but it needs an owner and a clear rule for duplicates.

What each ATS offers, and where Sprad stands

The table shows what the vendors state in their own developer documentation (as of 5 November 2026) and how Sprad is connected today. "Not documented" means we found nothing reliable, not that the feature does not exist. For systems that are not connected yet, the same applies: connectable through the system's interface, scope per system to be clarified in a conversation.

Two practical readings. First, an API is not the same as "write the referral and read the status": Personio's webhooks, for example, currently cover the person entity only, so status changes on applications are read by query rather than pushed. Second, in some systems the API user needs special rights or a specific plan, so ask your ATS administrator early, not in the week before go-live.

Jobs: import, do not maintain twice

Import jobs from the ATS on a schedule and let a closed role disappear from the referral view automatically. Decide upfront which roles are eligible: internal moves, confidential searches and executive roles are usually excluded. Sprad imports jobs from the ATS, so recruiters keep one place to maintain roles.

Referral as an application with a source

The referral should land in the ATS like any other application, with a fixed source value and the referrer's name or employee ID. Three details matter. Duplicates: match on email first, then name and profile URL, and agree who wins if the person already applied. Attribution: the first valid referral counts; write that into the program rules. Consent trail: store when the referred person was informed (see the legal section below).

Status back to the referrer

Referrers want to know whether something is happening, not every detail. A good setup mirrors a handful of stages and uses neutral wording; it never shows interview notes, scores or reasons for a rejection. Sprad mirrors the status from the ATS, so the referrer's view and the recruiter's view cannot drift apart. This is also where a works council looks first, because it shows employees' behaviour (see below). For what has to flow back into the ATS from AI tools in general, see ATS integration for screening results.

Bonus trigger: hire, probation, payout

Define the trigger as an event in the ATS: "hired" or "start date reached", optionally "probation passed". The tool reads it and releases the points or bonus; Sprad does not pay out, the company defines and pays rewards itself. Bonuses are typically wages in Germany, so involve payroll before the first payout, and agree the rules for part-time hires, employees who leave before the payout date and referrals by HR or hiring managers.

Rough calculation: what manual work costs

Assumptions, not measurements: 300 employees, 120 referrals per year. Without a connection someone retypes each referral (8 minutes) and answers two status questions per referral (5 minutes each), so 18 minutes per referral, about 36 hours a year. At an internal rate of 45 € per hour that is roughly 1,620 €. This alone does not justify a tool; Sprad Referral starts at 299 € per month for up to 300 employees, including 10+ ATS integrations (as of 5 November 2026). The integration is a hygiene factor: it protects data quality and recruiter time, while participation and hires pay for the program.

Questions for your ATS team and every vendor

• Data flow: which fields go in which direction, how often, and what happens on a failed sync?
• Rights: which API user and which permissions are needed, and can they be limited to jobs and referral applications?
• Deletion: how are referred candidates deleted after a rejection, in both systems, and after what period?
• Controller and processor: who is the controller, is a data processing agreement in place, where is the data hosted?
• Works council: is the status view or any employee dashboard covered by a works agreement?
• Duplicates and attribution: who wins when a person is referred twice or has already applied?
• Exit: can you export referral data and sources if you leave the tool?

In our conversations, data protection is usually a checkpoint rather than a blocker, as long as hosting, retention period and deletion are answered concretely.

Data protection and co-determination in DACH

• Referred person: the company receives the data from the employee, not from the person. GDPR Article 14 requires an information notice within one month at the latest, and at first contact if you contact them. Legal basis for processing the application data is typically Article 6(1)(b) or (f).
• Employee's contacts: if employees upload contacts, they must decide themselves what is shared; do not import address books wholesale.
• Processor: the referral vendor processes data on your behalf, so Article 28 requires a data processing agreement. A data protection impact assessment under Article 35 is needed only if the processing is likely to carry a high risk; check it for matching features.
• Works council: technical systems that can monitor behaviour or performance are subject to co-determination under section 87(1) no. 6 BetrVG; selection guidelines fall under section 95 BetrVG. A referral dashboard with per-employee figures is a typical case.
• Equal treatment: if referrals dominate, the workforce can become more homogeneous; the General Equal Treatment Act (AGG) applies to the selection regardless of the source.
• EU AI Act: AI that filters or ranks applicants is high-risk under Annex III; those obligations apply from 2 December 2027 under Regulation (EU) 2026/1744. Pure referral tracking is usually not affected, matching and ranking features need a check.

How Sprad Referral connects to your ATS

Sprad Referral connects to your ATS in both directions and replaces nothing. Jobs come from the ATS, the status of each referred candidate is mirrored from it, and employees refer through WhatsApp, SMS, Teams, Slack or email without installing an app. Connected today: Ashby, d.vinci and Personio. Any other system with an API can be connected; which fields and stages are used is clarified per system in a conversation. We do not promise a field mapping before we have seen your setup.

FAQ

Does Greenhouse need a separate referral tool?

Greenhouse has its own referral features. A separate tool helps if participation is the problem, for example for employees without a desk, and when the ATS stays the system of record. Check which API version your Greenhouse tenant uses.

Can a referral tool write the status into Workday?

Vendor documentation describes SOAP web services for candidates and requisitions, but we found no reliable public detail on writing stages. Clarify scope with your Workday team and the vendor before you plan on it.

Which ATS does Sprad Referral work with?

Connected today: Ashby, d.vinci and Personio. Other systems with an API can be connected; scope per system is clarified in a conversation. The Start plan includes 10+ ATS integrations.

What does the integration cost?

Sprad Referral starts at 299 € per month for up to 300 employees, including 10+ ATS integrations. Larger plans are on request (as of 5 November 2026, see pricing).

Who pays the referral bonus?

Your company, through payroll. The tool tracks points and releases the trigger, it does not pay out.

Do we need the works council?

In most DACH companies with a works council, yes, as soon as a dashboard shows employee-level behaviour. See section 87(1) no. 6 BetrVG.

Is the referred candidate's data covered by GDPR?

Yes. The person must be informed under Article 14, at the latest within one month.

What if the ATS has no API?

Use a scheduled export and import with a clear duplicate rule, or ask the vendor for an interface. Clarify early, because it changes the effort.

Where to go next

For the product, see employee referral software. For how to compare providers, read the best employee referral software; for program design, the ultimate guide to employee referral programs.

Sprad Referral lets employees refer through WhatsApp, SMS, Teams, Slack or email, while your ATS stays the system of record: jobs are imported, status is mirrored, and rewards are tracked. Plans start at 299 € per month for up to 300 employees, with 10+ ATS integrations included. See employee referral or ask us which scope your ATS supports.