HR inboxes receive hundreds of routine messages weekly — benefits questions, PTO requests, policy inquiries — that follow predictable patterns. Make.com automates the triage and routing layer by connecting Gmail labels to your full HR tech stack, ensuring each message reaches the right destination instantly while your team handles non-routine work.

Key Takeaways

• 60–70% of HR inbox volume is addressable by automated routing without human touch
• Make.com connects Gmail to your full HR tech stack for intelligent, rule-based routing
• Build routing rules on subject line keywords and sender domain — no AI required for basic triage
• Always preserve a human escalation path for messages that do not match any rule
• Log every automated action for audit and continuous improvement

An HR team that manually processes every email is an HR team that cannot scale. Non-technical HR teams are already building these automations with Make + AI — and the inbox is always the first place to start. Before you build your first scenario, it helps to understand what a Make scenario is and how it works. If you are migrating from Zapier, the Make.com FAQ for Zapier users answers the most common transition questions before you touch a single module.

Before You Build: Map Your Inbox First

Spend one week logging every email type that arrives in your HR inbox. Categorize each by request type, standard response time, required action, and whether a human must be involved. You will find that most volume falls into 5–10 repeating categories. These categories become your routing rules — and the foundation of every automation you build next.

This discovery step is not optional. Building automation on an unmapped inbox produces a system that routes noise at scale. Ask these seven questions before you automate anything to confirm your inbox categories are the right starting point.

Step 1: Set Up Gmail Labels as Routing Flags

Create Gmail labels for each email category you identified in the audit: Benefits-Question, PTO-Request, Policy-Inquiry, New-Hire-Paperwork, General-Inquiry, Escalate-Human. Apply these labels automatically using Gmail’s native filter rules based on subject line keywords. Your team should not be manually labeling — the filters handle it before a human ever sees the message.

Label discipline is the foundation. Make.com reads labels, not raw email content, in the basic triage build. Clean labels produce clean routing. Inconsistent labels produce routing errors.

Step 2: Build the Make.com Triage Scenario

Create a Make.com scenario triggered by the Gmail “Watch Emails” module, filtered to your HR inbox. The scenario reads the incoming email, checks the label applied by Gmail filters, and routes to the correct path via a Router module. Each Router path handles one email category with the appropriate automated action.

The Router module is the core of this build. Each branch is a separate rule: if label equals Benefits-Question, execute benefits path; if label equals PTO-Request, execute PTO path; and so on. Building this scenario with Claude cuts setup time significantly — you describe each routing rule in plain English and Claude generates the module configuration.

Step 3: Automate Standard Responses for Each Category

With the routing structure in place, configure the action for each branch:

• Benefits-Question: Make.com searches a benefits FAQ Google Sheet for a keyword match in the email subject and body, then sends the matched answer via Gmail. No coordinator involved.
• PTO-Request: Make.com creates a task for the relevant manager in your project management tool and sends a confirmation to the employee acknowledging receipt.
• Policy-Inquiry: Make.com searches a policy index document and replies with the relevant document link.
• New-Hire-Paperwork: Make.com triggers the onboarding sequence — sending the paperwork packet and logging the new hire in the tracking sheet.

The FAQ and policy index need to be maintained. Stale answers routed automatically are worse than no automation at all. Assign one person to own the source documents and review them monthly.

Step 4: Build the Escalation Path

Any email that does not match a routing rule receives the Escalate-Human label and triggers a separate Make.com path. That path creates a coordinator task with the full email content pasted in, assigns it to the appropriate HR team member, and sends the employee an acknowledgment that their message was received and is being reviewed.

The coordinator sees only non-routine work. Everything routine has been handled automatically before it reaches their queue. This is the design principle that makes the system scalable — your team’s attention is reserved for the 10–30% of messages that actually require human judgment.

Step 5: Add the Logging Layer

Every routed email gets a row in a Google Sheet: timestamp, sender, subject, category assigned, action taken, and response sent. This log serves three functions:

1. Audit trail: HR compliance requires documentation of communications. The log provides it automatically.
2. Accuracy review: Weekly review of the log reveals miscategorized emails — cases where Gmail filtered something into the wrong label and Make.com acted on a bad signal.
3. Continuous improvement: Over time, the log shows which categories are growing, which FAQ answers are being sent most often, and where the routing rules need refinement.

The logging step is where most teams cut corners and where the system quietly degrades. Schedule a 30-minute weekly review of the log for the first 90 days. After that, monthly reviews are sufficient for a stable system.

Step 6: Test Before Going Live

Send test emails into your HR inbox for every category in your routing rules. Verify the correct label is applied, the correct Make.com path fires, the correct response is sent, and the log row is written. Then send an intentionally unclear email and confirm it lands in the escalation path — not in a random routing branch.

Evaluate every Make scenario before it goes to production using a structured checklist. For this build specifically, test edge cases: emails with no subject line, emails from external domains, and emails that contain keywords matching multiple categories simultaneously.

How to Know It Worked

Measure these three indicators at the 30-day mark:

• Routing accuracy rate: What percentage of emails landed in the correct category? Target is 90%+ in week one, 95%+ by day 30 after rule refinement.
• Coordinator email queue volume: The total emails requiring human action should drop by 60–70% within the first two weeks. If it does not, your inbox categories are not well-defined enough.
• Response time on routine requests: Benefits questions and policy inquiries should receive automated responses within minutes of arrival, not hours or days.

Nick, a recruiter at a small firm, reclaimed 15 hours per week across a team of three once routine intake messages were routed automatically — over 150 hours per month returned to higher-value work. HR inbox triage follows the same pattern: the volume is there, the time savings are real, and the build is straightforward once the categories are defined.

Common Mistakes to Avoid

• Building before mapping: Automating an inbox you have not audited produces a system that confidently routes the wrong messages.
• Over-engineering the first version: Start with three routing categories, not ten. Prove the system works, then expand.
• Skipping the escalation path: If every email must match a rule, unmatched emails disappear. They do not escalate themselves.
• Ignoring the log: A routing system without a review process drifts. Stale FAQ answers and outdated policy links erode trust in the automation.
• Auto-replying to sensitive messages: Employee relations concerns, complaints, and anything touching legal or medical information must never be handled by automated response. Build explicit keyword blocks that force escalation for these topics.

If you want to understand where email triage fits within a broader HR automation strategy, running an OpsMap™ audit before automating gives you the full picture of which processes to sequence first.

Additional Reading

• How a Non-Technical HR Team Started Building Their Own Automations With Make + AI
• What Is a Make Scenario? The Plain-English Guide for Zapier Users
• Make.com FAQ: Everything Zapier Users Ask Before Switching
• 7 Questions to Ask Before You Automate Anything (The OpsMap Checklist)
• How to Build a Make Scenario With Claude: A Step-by-Step Walkthrough
• How to Evaluate a Make Scenario Built by AI Before It Goes to Production
• How to Run an OpsMap Audit Before Automating Anything
• 6 Ways the Make MCP Changes Automation Work for HR Teams
• How Sarah Compressed a 45-Minute Onboarding Process to Under 4 Minutes
• 10 Automations That Are Finally Easy to Build With Make + AI — No Developer Needed
• What Is Automation-First? Why You Should Automate Before You Add AI
• DIY Automation vs. Hiring a Make Partner in 2026: When to Do Each
• How to Set Up Routed Error Handling in Make With AI Assistance
• How One Ops Team Recovered $103K in Annual Labor Hours With Make Automation
• How Nick Cut 6 Manual Handoffs From Proposal Generation With One Make Workflow