Make.com automates reference checks end-to-end: collecting referee contacts, dispatching personalized requests, sending timed follow-up sequences, routing survey responses into your ATS, and alerting hiring managers on completion. The nine workflows below eliminate every manual step in the reference stage and cut three to seven days from a standard hiring cycle.

Reference checks are the last manual bottleneck in most recruiting pipelines. Sourcing, screening, scheduling, and offer generation all have automation solutions—yet most recruiting teams still rely on a recruiter dialing a phone or sending individual emails, then logging responses by hand. Every day that process takes is a day a candidate waits, and waiting candidates accept competing offers.

This post goes deep on one stage of the broader broken hiring process fix: reference checks from initial request through final ATS update. These nine workflows are ranked by the time they save, starting with the highest-impact builds. Every workflow uses Make.com as the orchestration layer.

1. ATS-Stage Trigger: Automatic Referee Request Dispatch

This is the foundation workflow. Every subsequent automation on this list depends on it working correctly.

• Trigger: Candidate advances to your “Reference Check” stage in your ATS. Make.com watches for this event via webhook or polling module.
• Action 1: Make.com extracts candidate name, role, hiring manager, and referee contact fields from the ATS record.
• Action 2: A personalized email goes to each referee with candidate context and a link to a structured survey form.
• Action 3: A confirmation email goes to the candidate explaining that their referees have been contacted and setting timeline expectations.
• Action 4: The ATS record updates with a timestamp and status tag: “References Requested – Awaiting Responses.”

Knowledge workers spend nearly 60% of their time on work coordination rather than skilled tasks. Chasing referee responses is a textbook example. This workflow eliminates that coordination for the request phase entirely.

Build priority: First. Everything else in this list plugs into it.

2. Candidate-Facing Referee Collection Form

Most ATS systems store referee contact data inconsistently—notes fields, structured fields, or nowhere at all. This workflow standardizes collection before outreach begins.

• Trigger: Same ATS stage trigger as Workflow 1, firing a separate branch.
• Action 1: Make.com sends the candidate a branded form requesting referee name, title, company, email, phone, and relationship for each required reference (typically two to three).
• Action 2: Form submission fires Workflow 1 automatically—no recruiter involvement required once the candidate submits.
• Action 3: Referee contact data writes back into structured ATS fields, not freeform notes, making it reportable and searchable.

Build priority: Second. Eliminates the most common delay point—recruiters waiting for candidates to “send over their references” via informal email.

3. Multi-Touch Referee Reminder Sequence

Non-response is the primary reason reference checks run past 48 hours. A structured reminder sequence resolves this without recruiter involvement.

• Trigger: Referee request sent (from Workflow 1). No response received after 24 hours.
• Action 1: Make.com sends a polite follow-up to the referee at Hour 24.
• Action 2: If still no response, a second reminder fires at Hour 48 with a revised subject line.
• Action 3: At Hour 72, Make.com sends an internal alert to the recruiter with referee contact info for direct outreach escalation.
• Action 4: All reminder activity logs to the ATS record with timestamps.

The reminder sequence runs on Make.com’s native scheduling module—no third-party tool required. Each step checks ATS status before firing, so a completed survey automatically cancels all pending reminders.

Build priority: Third. Eliminates the majority of multi-day delays with a single build.

4. Structured Survey Response: ATS Data Push

A reference check is only useful if the data lands where the hiring team reviews candidates. This workflow routes every survey response directly into the ATS record—no copy-paste required.

• Trigger: Referee submits the reference survey form (webhook from your survey tool).
• Action 1: Make.com maps each survey field to the corresponding ATS field: relationship, rating, recommendation, open-text comments.
• Action 2: ATS record updates with referee name, submission timestamp, and all structured response data.
• Action 3: Status tag updates to “Reference Received – [Referee Name]” so the hiring team has real-time visibility without logging into the survey tool.

Make.com connects natively to Typeform, JotForm, Google Forms, and SurveyMonkey, and via HTTP module to any survey platform with a webhook endpoint.

Build priority: Fourth. Without this, every prior workflow creates data that lives in a tool the hiring team never checks.

5. Role-Specific Question Routing

A senior engineer reference and an entry-level sales rep reference require different questions. Static templates produce shallow responses. This workflow routes referees to role-appropriate question sets automatically.

• Trigger: Referee request dispatch (from Workflow 1), branching on the job role or department field in the ATS.
• Action 1: Make.com reads the job role field and routes to the corresponding survey URL for that role category.
• Action 2: The referee receives a link to the role-specific form, not a generic template.
• Action 3: Response data maps back to the ATS using the same field structure from Workflow 4—role-specific questions feed into standardized rating fields plus role-specific open-text fields.

Build priority: Fifth. Medium complexity, high signal improvement per build hour.

6. Red-Flag Detection and Recruiter Alert

Not all reference responses are positive. This workflow scans open-text responses for language patterns that warrant immediate recruiter review—before anyone manually checks the survey tool.

• Trigger: Survey response received (same trigger as Workflow 4).
• Action 1: Make.com passes open-text response fields to an AI text analysis module.
• Action 2: The module checks for defined flag patterns: vague non-answers (“I can only confirm dates of employment”), negative sentiment, refusal to recommend.
• Action 3: If a flag is detected, Make.com sends a real-time Slack or email alert to the recruiter with the flagged response text and candidate name.
• Action 4: The ATS record tags as “Reference Requires Review” so it surfaces in the recruiter’s dashboard.

This workflow catches the responses that would otherwise sit unread in a survey tool until someone manually reviews the full stack—sometimes days after receipt.

Build priority: Sixth. High value for roles where a single problematic reference should stop the process immediately.

7. Hiring Manager Notification on Reference Completion

Hiring managers are blocked from moving to offer while references are outstanding. They need to know the moment the last reference arrives—not when the recruiter gets around to telling them.

• Trigger: All required references received (Make.com checks ATS record for completion count matching required count).
• Action 1: Make.com generates a summary message with candidate name, role, reference count, and a direct link to the ATS record.
• Action 2: Notification routes via the hiring manager’s preferred channel—Slack, email, or Teams—based on their profile in the ATS or a lookup table in Make.com.
• Action 3: ATS record updates to “References Complete – Hiring Manager Notified.”

For teams that have done the work to fix broken hiring processes, this workflow removes the final communication handoff that causes offer delays.

Build priority: Seventh. Low complexity, high satisfaction for hiring managers.

8. Automated Reference Summary Report

Reference responses across two to three referees need synthesis before a hire decision. This workflow compiles all responses into a formatted summary the hiring team can read without reviewing raw survey data.

• Trigger: All references complete (same trigger as Workflow 7).
• Action 1: Make.com pulls all structured and open-text responses from the ATS for the candidate.
• Action 2: An AI module generates a three-section summary: overall ratings, key themes across responses, and any flagged items.
• Action 3: The formatted summary attaches to the ATS record as a PDF or note, visible to everyone reviewing the candidate.

The summary presents what the referees said. Final judgment stays with the hiring team. The AI module formats—it does not evaluate.

Build priority: Eighth. Highest perceived value by hiring managers of any workflow in this list.

9. Final ATS Stage Advancement

When references are complete and the summary is attached, the candidate advances automatically—no recruiter required to click “Move to Offer Stage.”

• Trigger: All references complete AND no “Requires Review” flag on the record.
• Action 1: Make.com advances the candidate to the next ATS stage—offer review, compensation discussion, or whatever your pipeline labels it.
• Action 2: Hiring manager receives a separate notification that the candidate is staged for offer discussion.
• Action 3: A full reference timeline—when each request was sent, when each response arrived, total elapsed time—logs to the record for pipeline analysis.

Teams that deploy all nine workflows consistently see the reference stage drop from three to seven days to 24 to 48 hours. The reduction does not come from faster referees—it comes from zero idle time between steps.

Frequently Asked Questions

What does Make.com need to automate reference checks?

Make.com needs three connections: your ATS (via webhook or native module), your survey tool (webhook on submission), and your communication platform (email or Slack). Most teams have all three in place and complete the foundation workflow in under four hours.

Which workflow delivers the fastest time savings?

Workflow 3—the multi-touch reminder sequence—delivers the single largest time reduction. Non-response accounts for most of the delay in the reference stage. Automated reminders at 24, 48, and 72 hours resolve the majority of unresponsive referees without recruiter involvement.

Can Make.com advance ATS stages automatically?

Yes. Make.com connects to all major ATS platforms—Greenhouse, Lever, Workday, BambooHR, and others—via native modules or HTTP. Stage advancement triggers from a status check: all required references received and no review flag present means the candidate moves to the next stage automatically.

Do all nine workflows need to be built at once?

No. Build in order. Workflows 1 through 3 deliver the bulk of the time savings and operate independently. Workflows 4 through 9 layer in data quality, analysis, and handoff improvements that compound over time.