How to Automate Exit Interviews with Make.com™ Mailhooks: A Step-by-Step HR Guide

Exit interview feedback is one of the highest-value, lowest-captured datasets in HR. Departing employees answer your questions once, the responses land in someone’s inbox, and the strategic insight expires before anyone reads it. The fix is not a better survey tool — it is an automated capture layer that intercepts every response the moment it arrives and routes structured data to the people who need to act on it.

This guide walks you through building that layer using a Make.com™ mailhook scenario. If you are new to the trigger-type decision, start with the parent pillar on the webhooks vs. mailhooks infrastructure decision before proceeding — it frames why a mailhook is the right trigger for an email-based offboarding process.

Before You Start

Completing this build requires the following before you open Make.com™:

  • A Make.com™ account with at least one active scenario slot (any paid plan or active trial).
  • A designated exit survey delivery method: either an email-based survey tool (such as a form builder that sends result notification emails) or a process where employees reply directly to a dedicated HR address.
  • A destination system where parsed data will land — a Google Sheet, Airtable base, or HRIS with an accessible API or native Make.com™ module.
  • A sample exit response email you can paste into Make.com™ during scenario testing. If you have not yet run exit surveys, create a realistic mock response now.
  • Time budget: Allow 90 minutes to two hours for a baseline build and 30 minutes for initial testing.
  • Access decision: Confirm with your IT or compliance team whether parsed employee feedback data may be stored in Make.com™’s data store or must flow directly to an on-premises system.

Risks to know before you build: Mailhooks process emails in the order they arrive, not in chronological order of the underlying event. If your survey platform batches notification emails, you may see a processing delay. Plan filters carefully — a loose filter will pull unrelated emails into the workflow and pollute your dataset.

Step 1 — Create a New Scenario and Add the Email Trigger Module

Open Make.com™, navigate to Scenarios, and click Create a new scenario. When prompted to select a trigger, search for Email and select the Watch Emails module (or the equivalent inbox-monitoring trigger in the current interface). Make.com™ will generate a unique mailhook email address — copy this address immediately and store it somewhere accessible.

This mailhook address is your capture point. Any email sent to this address will trigger the scenario. Configure the following settings inside the trigger module:

  • Folder/Label: Leave as inbox unless your mail setup routes exit responses to a subfolder.
  • Maximum number of emails per cycle: Set to 1 for initial testing. Increase to 5-10 once the scenario is stable.
  • Mark as read after processing: Enable this to prevent reprocessing.

Test the trigger by sending the sample exit response email you prepared to the mailhook address. Confirm Make.com™ captures the email and displays the raw fields (subject, sender, body text, and any attachments) in the output panel before proceeding to the next step.

Step 2 — Add a Filter to Block Unintended Triggers

A filter placed immediately after the Email trigger module is the single most important guard against data contamination. Without it, any email that reaches the mailhook address — including auto-replies, bounce notifications, and forwarded threads — will advance through the scenario and insert garbage rows into your destination.

Click the small filter icon on the path between the trigger and your next module. Configure at minimum two conditions joined by AND logic:

  • Sender domain equals your survey platform’s notification domain (e.g., yoursurveyplatform.com) or your internal company domain if employees reply directly.
  • Subject line contains a keyword unique to exit survey notifications, such as “Exit Survey Response” or whatever prefix your survey tool appends.

Optionally add a third condition: Body text contains a phrase present in every legitimate exit response, such as a question label unique to your form (“Reason for Leaving:” or “Overall Experience Rating:”). This three-condition filter eliminates the vast majority of noise.

For a deeper treatment of resilience patterns that go beyond basic filters, see the guide on mailhook error handling for resilient HR automations.

Step 3 — Parse the Email Body into Structured Fields

The email body arrives as a single block of text. Your HRIS or tracking sheet needs individual fields — departure reason, tenure band, department, manager rating, and so on. This step converts unstructured text into structured data using Make.com™’s built-in text parsing tools.

Add a Tools > Set Multiple Variables module after your filter. For each data field you need, create a variable using one of the following approaches:

  • String extraction with delimiters: If your survey platform formats responses as “Question Label: Answer” on separate lines, use the substring and indexOf functions to extract the text between the label and the next line break. Example pattern: {{substring(1.textContent; indexOf(1.textContent; "Reason for Leaving: ") + 20; indexOf(1.textContent; newline; indexOf(1.textContent; "Reason for Leaving: ")))}}
  • Regular expressions: For more complex patterns, Make.com™’s regex function extracts matching groups. Use this when field values span multiple lines or contain special characters.
  • Fixed-position extraction: If your survey notification always places a rating on the third line of the body, use split and array indexing to pull that line directly.

Build one variable per field. Test each expression against your sample email in the output panel before adding the destination module. Parsing errors at this stage are easier to debug than after data has flowed into your spreadsheet. For an advanced treatment of parsing patterns, review the reference on advanced mailhook parsing for HR data extraction.

Step 4 — Route Parsed Data to Your Destination System

With structured variables in hand, add the module for your destination. The most common options and their configuration notes:

Google Sheets

Add a Google Sheets > Add a Row module. Map each parsed variable to the corresponding column. Ensure your sheet has a header row with column names that match your variable names exactly — this eliminates mapping confusion during future edits.

Airtable

Add an Airtable > Create a Record module. Map variables to Airtable field names. Airtable’s field-type enforcement will flag mismatches (e.g., sending a text string to a numeric field) at test time rather than silently corrupting the record.

HRIS via HTTP Module

If your HRIS exposes a REST API, add an HTTP > Make a Request module. Set method to POST, configure the endpoint URL and authentication headers, and construct the JSON body by mapping your parsed variables into the required payload structure. Confirm your HRIS API documentation for the exact endpoint and field names.

After adding the destination module, run a full test by sending another copy of your sample email to the mailhook address. Verify the row or record appears in your destination with all fields correctly populated before moving to Step 5.

Step 5 — Add Conditional Routing for High-Priority Flags

Not all exit responses carry the same urgency. A departing employee who rates their manager a one out of five and cites a hostile work environment requires a different response than someone leaving for a higher salary offer. Conditional routing lets a single scenario handle both without manual triage.

After your destination module, add a Router module with two or more paths:

  • Path A — Standard processing: The default path. No additional action beyond the destination write completed in Step 4.
  • Path B — Escalation: Triggered when a parsed variable meets a threshold condition (e.g., Manager Rating is less than 2, or Departure Reason variable contains “harassment” or “hostile”). Add a Slack, Teams, or email notification module on this path to alert HR leadership immediately. Include only the fields necessary for context — avoid routing full PII into a group channel.
  • Path C — Retention flag: Optional. If the parsed reason indicates the employee would consider returning or cited a remediable issue (compensation, flexibility), route an alert to the talent acquisition team for future pipeline consideration.

Set each Router path’s filter condition to match your escalation logic. Test each path explicitly by modifying your sample email to produce a match, then confirm the correct downstream module fires.

The broader strategy for automating employee feedback with mailhooks covers how this conditional routing pattern extends across other HR feedback loops beyond offboarding.

Step 6 — Configure Error Handling

A scenario that silently fails is worse than one that fails loudly. Exit interview data is time-sensitive — a missed capture during a high-turnover quarter corrupts your analysis. Add error handling to ensure every failure is visible and recoverable.

In Make.com™, right-click any module and select Add error handler. Configure the following:

  • Ignore errors on the notification modules (Slack, Teams) — a failed Slack message should not prevent the data from writing to the destination.
  • Rollback or Resume on destination write errors — if the Google Sheets or HRIS write fails, log the failure to a separate error-tracking sheet with the raw email body so you can reprocess manually.
  • Email alert to scenario owner: Add a fallback email module that fires when any critical module fails, sending the error message and the triggering email subject to the HR ops inbox.

Schedule a weekly review of Make.com™’s execution history for this scenario during the first 60 days. After the scenario stabilizes, monthly reviews are sufficient.

Step 7 — Activate the Scenario and Connect Your Survey Delivery Process

With the scenario built and tested, activate it by toggling the scenario status to On. Make.com™ will now monitor the mailhook address continuously.

Complete the operational connection by updating your exit survey delivery process to route response notifications to the mailhook address:

  • If your survey platform sends admin notifications, update the notification recipient email to the Make.com™ mailhook address.
  • If employees reply directly to an HR inbox, set up an email forwarding rule from that inbox to the mailhook address (most email platforms support auto-forwarding by subject line or sender criteria).
  • If your HRIS triggers an offboarding email to the exiting employee, ensure the Reply-To address on that email is the mailhook address.

Run one live test with a real or simulated offboarding event. Confirm the full chain fires: email arrives at mailhook → scenario executes → data lands in destination → escalation path fires if applicable.

How to Know It Worked

A functioning exit interview automation scenario produces three verifiable signals:

  1. Execution count matches offboarding headcount. Pull your HR system’s list of departures for any given week. The number of successful scenario executions in Make.com™’s history for that period should equal or closely approximate the number of exit surveys expected. Discrepancies indicate either a delivery gap (survey not sent) or a filter gap (email not captured).
  2. Destination rows are complete. Open your tracking sheet or HRIS view. Every row written by the scenario should have all required fields populated. Blank fields indicate a parsing expression that failed to match — check the parsing logic in Step 3 against the actual email format.
  3. Escalation alerts fire for high-priority responses. Submit a test response that meets your escalation criteria and confirm the alert arrives in the correct channel within the scenario’s processing window (typically under two minutes for active scenarios).

If any of these checks fail, review the execution detail in Make.com™ to identify which module produced the unexpected output or error.

Common Mistakes and Troubleshooting

The scenario fires but the destination row is empty

This almost always means the parsing expressions in Step 3 did not match the actual email format. Open the execution detail, inspect the raw email body captured by the trigger module, and compare it against the patterns your expressions expect. Survey platform notification formats can differ from what you anticipated based on the platform’s documentation — always parse from a real captured email, not a hypothetical template.

The scenario fires for emails it should ignore

Your filter conditions are too loose. Return to Step 2 and tighten the conditions. The subject line keyword and sender domain combination should be unique enough that no other email in normal HR operations would match both simultaneously.

The scenario does not fire at all

Confirm the scenario status is set to On. Confirm the mailhook email address in the trigger module matches the address you provided to your survey platform or forwarding rule. Send a test email directly from your personal email client to the mailhook address and check whether the scenario executes — this isolates whether the problem is in the Make.com™ trigger or in the upstream email routing.

High-priority escalations are not reaching the right channel

Test the Router path condition by temporarily lowering the threshold (e.g., set Manager Rating less than 5 instead of less than 2) and submitting a test response. If the path fires with the looser condition, your parsed variable values may differ from what you expect — inspect the Set Variables module output to see the exact value being evaluated against your condition.

Extending the Workflow

A working exit interview capture scenario is a foundation, not a ceiling. Once the baseline is stable, the same mailhook infrastructure supports:

  • Trend aggregation: Add a monthly scheduled scenario that queries your tracking sheet and produces a summary report — average ratings by department, most common departure reasons, manager risk flags — and delivers it to HR leadership automatically.
  • Longitudinal cohort analysis: Link the exit data row to the employee’s hire date and tenure from your HRIS to build attrition cohort data without manual joins.
  • Boomerang candidate tagging: If a departing employee’s response indicates openness to returning, automatically tag them in your ATS for future outreach.

For the approach to automating employee feedback across the full employee lifecycle — not just offboarding — the sibling guide covers the complete feedback automation pattern.

If you are evaluating whether mailhooks or webhooks are the right trigger layer for other HR workflows, the comparative analysis on strategic trigger selection for HR automation provides the decision framework. And once exit interview automation is running, the same principles apply directly to recruitment — see the guide on extending mailhook automation into recruitment workflows to close the talent lifecycle loop.

McKinsey research consistently finds that organizations with systematic feedback loops — including structured offboarding processes — make faster and more accurate workforce decisions than those relying on anecdotal data. APQC benchmarking confirms that high-performing HR functions spend proportionally less time on transactional administration. Automating exit interview capture is not a prestige project; it is the operational discipline that makes the data exist in a form that can be acted on. Harvard Business Review research on employee experience reinforces that the offboarding moment carries outsized influence on employer brand perception — consistency in the process signals organizational maturity regardless of why someone is leaving.

According to Parseur’s research on manual data entry costs, organizations spend an estimated $28,500 per employee per year on manual data entry tasks. Exit interview consolidation — copying responses from emails into spreadsheets, tagging themes manually, routing summaries by hand — is exactly the category of work that number represents. One scenario eliminates it permanently for this workflow.

The scenario you have built in this guide is a single-purpose, high-reliability automation that requires no ongoing manual intervention. Build it once, test it rigorously, and let it run. Your HR team’s attention belongs on the insights the data reveals — not on the process of collecting it.