Capture sourced candidates into your talent database instantly
Automate referral tracking for recruiters
Automate referral tracking for recruiters
Aggregate employee referrals, verify recruiters in your ATS, and post curated Slack threads grouped by recruiter for daily follow-up.
Overview
Employee referrals come in from forms, ATS submissions, and ad hoc messages -- but recruiters still have to manually track what's new, who owns it, and whether anyone followed up. This template connects your referral tracking table to Slack and Ashby (or your ATS) so each recruiter gets a personalized daily thread with their referrals, verified and ready for action. No more missed referrals, no more manual routing.
How it works
- Search your Zapier Tables referral tracker for recent submissions. 2. Verify the current assigned recruiter for each role in Ashby (or your ATS) so referrals always go to the right person. 3. Group referrals by recruiter. 4. Post a personalized Slack thread for each recruiter with candidate details, LinkedIn profiles, and confidence ratings. 5. Mark each referral as posted to prevent duplicates.
Who this is for
Recruiting teams, talent acquisition leads, and HR operations managers who receive employee referrals through forms or their ATS and want to make sure every referral gets routed to the right recruiter without manual tracking or follow-up gaps.
Suggested prompt
Help me set up a daily referral aggregator that posts curated Slack threads to my recruiting channel, grouped by recruiter. Here's what I need:
Step 1: Create the tracking table Help me create a Zapier Table called "Referral Tracker" with these fields: candidate name, candidate email, LinkedIn URL, date of referral (datetime), referrer name, referrer email, referrer Slack ID, role referred for, confidence level (dropdown: "Top 10% candidate" / "Not confident they're top 10%"), referral details/notes, resume link, candidate profile link (ATS candidate page URL), job link (ATS job posting URL), already applied (Yes/No), primary recruiter name, primary recruiter email, primary recruiter Slack ID, posted to Slack (checkbox, default unchecked), and Slack post URL.
Step 2: Daily aggregation workflow Each weekday, I want to:
- Search the Referral Tracker for new referrals since the previous business day (Monday should catch Friday through Sunday)
- Skip any referrals already marked "Posted to Slack"
- For each referral, look up the current recruiter for that role in Ashby (or my ATS) to make sure it goes to the right person -- recruiter assignments change, so always verify against the live job posting
- Group the remaining referrals by primary recruiter
- For each recruiter, post a parent message to the recruiting Slack channel greeting them and noting their referrals are threaded below
- Post each referral as a separate thread reply including: who referred them, candidate name and email, LinkedIn profile, the role, whether they've applied, and the referrer's confidence level and notes
- After posting each referral thread reply, get the Slack permalink and update the table record -- set "Posted to Slack" to true and save the permalink
The "Posted to Slack" checkbox is the source of truth for deduplication. Even if the same referral appears in multiple date searches, it should never get posted twice.
Frequently asked questions
What kind of referral tracking table do I need?
The template works best with a Zapier Table that includes fields for candidate info (name, email, LinkedIn), referral metadata (referrer name, email, Slack ID, confidence level, notes), role details (job title, ATS job link, ATS candidate link), recruiter assignment (name, email, Slack ID), and posting status (a Posted to Slack checkbox and a Slack post URL field). The suggested prompt walks you through creating this table step by step.
Does this only work with Ashby, or can I use a different ATS?
The template includes Ashby actions for verifying which recruiter is assigned to each role, but the workflow pattern works with any ATS that has a Zapier integration. If you use Greenhouse, Lever, Workday, or another ATS, swap the Ashby action for your ATS equivalent to look up the hiring team for a given job. The rest of the workflow (table tracking, Slack posting, deduplication) stays the same.
How does it prevent the same referral from being posted twice?
Each referral record in the tracking table has a Posted to Slack checkbox. After a referral is posted to Slack, the workflow marks that checkbox and saves the Slack permalink. On the next run, any record with that box already checked gets skipped. This means you can safely run the aggregator daily without worrying about duplicate posts, even if date ranges overlap.
Why does it verify recruiters against the ATS instead of just using the table data?
Recruiter assignments change. A role might get reassigned to a different recruiter between when the referral was submitted and when the daily aggregator runs. By looking up the current hiring team in Ashby (or your ATS) at post time, each referral always gets routed to the right person instead of someone who may no longer own that req.
