Post-interview feedback automation with Make.com™ eliminates the gap between interview end and hiring decision. These seven workflows—calendar triggers, structured scoring forms, ATS write-backs, escalation reminders, decision routing, completion analytics, and candidate status notifications—remove every manual handoff between the interview closing and the next step in the process.

Post-interview feedback is the step where most recruiting processes quietly fall apart. Interviewers mean to submit their assessments. Recruiters mean to follow up. Somehow, 48 hours later, the hiring manager is still waiting on two scorecards while a competing offer is already on the candidate’s desk. This is the bottleneck that Make.com automation for HR teams was built to eliminate—not by replacing human judgment, but by removing every manual handoff that sits between the interview ending and the decision being made.

The seven workflows below are ranked by impact. The ones that deliver the fastest, most measurable improvement in feedback completion rates and decision speed come first. Each one is buildable without a developer using Make.com’s visual scenario builder.

1. Calendar End-Time Trigger → Instant Feedback Form Delivery

This is the single highest-impact post-interview automation available. The moment an interview block closes on the calendar, Make.com™ fires—no manual step required.

• Trigger: Google Calendar or Outlook event end time, matched by event title keyword or attendee list.
• Action: Make.com™ extracts interviewer name, candidate name, and role from the event metadata, then sends a personalized Slack message or email with a direct link to a pre-populated feedback form.
• Form pre-population: Candidate name, role, interview date, and competency dimensions are pre-filled—the interviewer only scores and submits.
• Timing advantage: Delivery within 60 seconds of interview end captures recall at peak quality. SHRM research links structured, timely feedback to more defensible hiring decisions.
• Tools: Google Calendar or Outlook 365 module → Typeform, Google Forms, or Jotform → Slack or Gmail.

Build this first. Every other workflow in this list depends on the feedback being submitted—and this trigger is what makes submission happen consistently.

2. Structured Competency Scoring Form With Conditional Logic

Automation delivers a bad form faster if the form itself isn’t structured. The second workflow is about what the form captures, not just when it arrives.

• Form architecture: 4–6 competency dimensions scored on a defined scale (1–5), one overall hire/no-hire recommendation, and a single optional open-text field for context. No more, no less.
• Conditional logic: If the interviewer selects “Strong Hire,” the form surfaces a prompt for a top strength to include in the candidate summary. If they select “Do Not Proceed,” it surfaces a specific disqualifying reason field.
• Why it matters: Harvard Business Review research on structured interviewing shows that standardized scoring dimensions reduce in-group bias and improve predictive validity compared to open-ended assessments.
• Make.com™ role: Routes completed form data based on conditional field values—strong hires trigger one downstream action, passes trigger another (see Workflow 5).
• Data output: Every submission produces a consistent record: comparable scores, documented reasoning, and a timestamp—the foundation for the analytics workflows later in this list.

Standardize this form before you automate anything else. The form design determines the quality of every downstream workflow.

3. ATS Write-Back: Zero-Touch Candidate Record Updates

Manual ATS data entry is where feedback scores go to die. This workflow closes the loop automatically the moment a form is submitted.

• Trigger: Form submission webhook from Typeform, Jotform, or Google Forms.
• Action: Make.com™ maps each scored competency field to the corresponding ATS candidate record field and writes the data without human touch.
• ATS compatibility: Make.com™ has native modules for Greenhouse, Lever, Workable, and BambooHR. For ATS platforms without a native connector, the HTTP module handles REST API write-backs using the platform’s documented API.
• Timestamp logging: Every write-back includes a submission timestamp and interviewer ID—giving recruiting leaders an audit trail for every feedback record.
• Error handling: If the ATS write-back fails, Make.com™ routes to an error handler that notifies the recruiting coordinator via Slack with the candidate name and failure reason.

Without this workflow, ATS data integrity depends on manual entry. Manual entry is inconsistent by definition—this automation makes the record accurate before the next person needs it.

4. Escalation Reminders: Auto-Follow-Up for Overdue Scorecards

Not every interviewer submits on the first prompt. This workflow handles the follow-up without a recruiter chasing it.

• Trigger: Make.com™ checks the feedback tracking sheet or ATS at a defined interval (e.g., 4 hours after interview end). If no submission record exists for that interviewer and candidate, the escalation chain fires.
• Sequence:
  • 4 hours post-interview: Slack DM reminder with form link
  • 24 hours: Email reminder from the recruiting coordinator’s address
  • 48 hours: Slack message to the hiring manager flagging the overdue scorecard
• Deduplication: Once the scorecard is submitted, Make.com™ marks the record complete and stops the escalation chain—no one receives a reminder after they’ve already submitted.
• Personalization: Each reminder message includes candidate name, role, and interview date—not a generic “please submit your feedback” blast.

This workflow eliminates the recruiter’s least favorite task: manually tracking who hasn’t submitted and sending individual follow-ups. The system handles it, and the recruiter sees a notification only when escalation reaches the hiring manager level.

5. Decision Routing: Move Candidates Forward Without a Meeting

When all scorecards are in, the next decision—advance, hold, or decline—shouldn’t require a scheduling round to execute. This workflow makes the data available the moment the last scorecard lands.

• Trigger: Make.com™ detects when the final required scorecard for a candidate is submitted, matched against an expected interviewer count.
• Aggregate view: Make.com™ compiles all scores into a summary document—average competency ratings, individual hire/no-hire votes, and any flagged disqualifiers—and delivers it to the hiring manager via Slack or email.
• Conditional routing:
  • All interviewers marked “Strong Hire” → Make.com™ sends a draft offer request to the recruiting coordinator and updates the ATS stage.
  • Mixed signals → Make.com™ sends the aggregate summary to the hiring manager with a decision request prompt.
  • Any “Do Not Proceed” with a documented reason → Make.com™ moves the candidate to the declined stage in the ATS and queues a candidate notification (see Workflow 7).
• Speed impact: Teams using structured hiring process automation report decisions in hours rather than days when all scorecard data arrives in one compiled view.

The goal is to compress the gap between “last scorecard in” and “decision made.” Manual compiling creates that gap—this workflow removes it.

6. Feedback Completion Analytics Dashboard

The previous five workflows produce a measurable feedback loop only if someone tracks the data. This workflow surfaces the metrics that tell recruiting leaders what’s working.

• Data logged per hiring cycle: Feedback submission rate by interviewer, average time from interview end to scorecard submission, escalation trigger rate, and decision-to-offer timeline.
• Make.com™ role: Appends a structured row to a Google Sheet or Airtable table after each scorecard submission and each decision event. The sheet becomes the live data source for the dashboard.
• Dashboard layer: A connected Looker Studio or Airtable view displays rolling metrics by role, department, and interviewer—no manual reporting required.
• What it reveals:
  • Which interviewers consistently submit late (training or accountability opportunity)
  • Which roles have the longest feedback-to-decision gaps (process bottleneck)
  • Whether escalation rate is trending up or down after automation launch

You can’t improve what you don’t measure. This workflow turns the feedback process from a black box into a visible, improvable system—one where recruiting leaders see exactly where time is being lost and act on it.

7. Candidate Status Notification on Decision Close

The final workflow closes the loop on the candidate side. When a decision is made, the candidate notification fires automatically—not from a recruiter’s draft queue two days later.

• Trigger: ATS stage change (advance to offer stage, or move to declined).
• Advance path: Make.com™ sends the recruiting coordinator a pre-drafted next-steps email template with candidate name, role, and a scheduling link pre-populated. One click to send—no composition required.
• Decline path: Make.com™ generates a personalized decline email from the documented disqualifying reason captured in Workflow 2 and queues it for review before send. The reason is specific to the role and interview—not a templated generic rejection.
• Audit trail: Every notification—sent or queued—is logged with a timestamp and the coordinator who actioned it.
• Compliance benefit: Consistent, timely candidate communication reduces legal exposure from delayed or missing rejection notices.

Candidate experience is recruiting brand. Slow, inconsistent post-interview communication damages future candidate pipelines. This workflow ensures every candidate gets a response within a defined window regardless of recruiter workload.

Frequently Asked Questions: Post-Interview Feedback Automation With Make.com

How does Make.com connect to Google Calendar for post-interview triggers?

Make.com’s Google Calendar module monitors for event end times. You configure the trigger to watch a specific calendar and filter by event title keyword or attendee email. When the event ends, Make.com fires automatically—no polling delay, no manual step required.

What ATS platforms does Make.com integrate with for feedback write-back?

Make.com has native modules for Greenhouse, Lever, Workable, BambooHR, and dozens of other ATS platforms. For systems without a native module, Make.com’s HTTP module handles REST API write-backs using the platform’s documented API.

How long does it take to build a post-interview feedback automation in Make.com?

Workflow 1 (calendar trigger to form delivery) takes 2–3 hours for a first build. Workflows 3 through 7 each add 1–2 hours depending on ATS and form complexity. A complete seven-workflow feedback system takes one to two focused build days.

Does the interviewer need a Make.com account to submit feedback?

No. Interviewers interact only with the form link delivered via Slack or email. Make.com operates in the background—receiving submissions, routing data, updating the ATS, and triggering follow-up actions. No interviewer login or account is required.