Nine Make.com workflows cover every gap between a signed offer and a productive 90-day employee. Each one eliminates a manual handoff your HR team runs right now — IT provisioning requests, welcome sequences, compliance document collection, payroll setup, and the escalations nobody sends until something breaks. Build them in order or drop in whichever fills your biggest gap.

The moment a candidate signs an offer letter, a clock starts. Every hour your team spends chasing IT tickets, drafting welcome emails, and copying data between systems is an hour the new hire sits in uncertainty — second-guessing whether they made the right choice. That doubt costs real money: SHRM ties poor onboarding to elevated 90-day turnover, and replacing a single employee runs an average of $4,129 in direct recruiting costs before you account for lost productivity.

Onboarding automation solves a process problem, not a paperwork problem. The goal is not to remove human connection — it is to remove the manual handoffs that delay connection. These nine workflows build directly on the broader hiring process repair framework by extending the automated candidate journey past the offer and into the employee’s first 90 days.

The workflows are ranked by impact — specifically, how directly each one affects day-one readiness, early retention, and time-to-productivity. Build them in order if you are starting from scratch, or drop in whichever fills your biggest current gap.

1. Offer-Acceptance Trigger: The Master Onboarding Kickoff

Every other workflow on this list depends on one scenario firing correctly: the moment an offer is accepted, your entire onboarding stack activates. This is the master trigger — and it is the first one to build.

• Trigger: Candidate status changes to “Offer Accepted” in your ATS, or an e-signature webhook fires when a signed offer document is received.
• Immediate actions: Create new employee record in HRIS, notify HR coordinator and hiring manager, log start date and role details to a centralized onboarding tracker (Airtable or Google Sheets), and queue all downstream workflows.
• Branching logic: Route remote vs. in-office hires, full-time vs. part-time, and domestic vs. international through separate paths from the start. Clean branching at the trigger level prevents messy conditional logic in every subsequent scenario.
• Error handling: Build an alert to your HR inbox if the HRIS record creation fails. A silent failure here means no other workflow fires correctly.

This is the non-negotiable foundation. Every other workflow below is downstream of this trigger. Test it with 10 synthetic records before going live and treat it as your most protected scenario.

2. IT Provisioning Checklist Automation

Day-one system access is the single most operationally measurable onboarding outcome. A new hire without a working email, laptop login, or Slack access on their first day is an immediate trust failure — and 100% preventable with automation.

• Trigger: New employee record creation in HRIS (fired by Workflow 1).
• Actions: Send a structured IT provisioning request to your IT team or ticketing system (Jira, Freshservice, or similar) with all required fields pre-populated from the HRIS record — name, department, role, start date, required software, hardware type, and remote vs. in-office status.
• Automated follow-up: If the IT ticket is not marked complete 48 hours before the start date, fire an escalation notification to the IT manager and HR. The new hire doesn’t care why access is late. They just know it is.
• Completion logging: When the ticket closes, send an automated confirmation to the HR coordinator and update the onboarding tracker.

Pair this scenario with a simple Airtable view showing all pending IT tickets and their due dates. Your IT team gets structure. Your HR team gets visibility. Neither has to chase the other.

3. Pre-Boarding Welcome Sequence

The gap between offer acceptance and day one is the highest-anxiety stretch for new hires. Most companies do nothing during this window. The ones that automate it see measurable differences in first-week engagement.

• Trigger: New employee record creation (Workflow 1), delayed 30 minutes to confirm record integrity.
• Day 0 — acceptance day: Send a personalized welcome email from the hiring manager — not HR — with a first-day logistics summary: time, location or video link, parking, dress code, and who to ask for at the front desk.
• Day −7 — one week before start: Send a “what to expect your first week” email with team introductions, a calendar preview, and any reading the new hire should complete in advance.
• Day −1 — the day before start: Send a reminder with the direct Slack or Teams handle for their manager, the morning agenda, and any access credentials that are ready.

All three emails draft automatically from a Make.com scenario using data already in the HRIS record. The hiring manager reviews and approves — or sends as-is once you’ve tested the templates enough to trust them. See how this kind of workflow compressed a 45-minute manual process to under four minutes in the Sarah onboarding case study.

4. Compliance Document Collection and I-9 Coordination

Compliance paperwork has a hard deadline — I-9 verification must happen by end of day three, not whenever your inbox clears. Manual tracking across multiple concurrent new hires creates real legal exposure.

• Trigger: New employee record with start date confirmed (Workflow 1).
• Actions: Send a document checklist to the new hire via email — W-4, direct deposit authorization, emergency contact form, and any state-specific required disclosures. Include deadline dates for each document. Log expected vs. received status to the onboarding tracker.
• I-9 coordination: Send a separate automated reminder to the HR coordinator with the Section 2 deadline (day three). If the new hire hasn’t submitted Section 1 documents 24 hours before their start, fire an escalation.
• Confirmation loop: When each document is received and logged, send an automated acknowledgment to the new hire and update the tracker row.

This scenario does not replace your E-Verify process or legal review — it ensures nothing falls through the cracks on timing. HR reviews the substance. The workflow manages the calendar.

5. Payroll Setup and Direct Deposit Activation

The first paycheck is a trust signal. Late or incorrect first-pay events generate more new-hire complaints than almost any other onboarding failure. Automating the setup handoff closes the gap between HR collecting documents and payroll having what it needs to run.

• Trigger: Direct deposit authorization and W-4 marked as received in the onboarding tracker.
• Actions: Send a structured notification to your payroll administrator with all required setup fields from the HRIS record. Log the notification timestamp to the tracker. Queue a confirmation request at 72 hours — if payroll setup isn’t confirmed by then, escalate.
• First-pay confirmation: After the first payroll run, send an automated confirmation to the new hire: “Your first paycheck is scheduled for [date] via direct deposit to the account ending in [last four].” One sentence. Significant trust signal.

This workflow delivers the most value for small HR teams processing multiple starts simultaneously. The automation handles routing. Payroll handles the review.

6. Benefits Enrollment Window Automation

Benefits enrollment windows close whether or not the new hire knew they existed. HR teams that manage this manually send reminders when they remember — which is not a system. Make.com turns the enrollment window into a managed sequence.

• Trigger: Start date confirmed in HRIS.
• Day 1 email: Benefits enrollment introduction — what’s available, what the window is, and where to enroll.
• Day 15 reminder: If enrollment is not yet confirmed in the HRIS, send a reminder with the deadline highlighted.
• Day 27 — three days before window closes: Final escalation to the new hire and a copy to their manager. At this point, someone human needs to make a phone call if there’s still no action.
• Confirmation: When enrollment logs as complete, send an acknowledgment with a summary of elected coverage and contact info for the benefits administrator.

The sequence runs without manual intervention. HR’s job shifts from “did I remember to follow up with Marcus?” to reviewing the exception report of anyone who didn’t enroll.

7. Manager and Buddy Assignment Notification

Most onboarding plans name a buddy or a point of contact but never automate the notification — the person finds out through a Slack message or a hallway conversation. That breaks the experience before it starts.

• Trigger: Manager and buddy fields populated in the HRIS record (either manually or from the ATS during Workflow 1).
• Manager notification: Automated email to the hiring manager with the new hire’s name, start date, role, and a pre-built first-week agenda template. Include a link to the onboarding tracker row for that employee.
• Buddy notification: Separate email to the assigned buddy — lighter in tone, with the new hire’s LinkedIn profile, start date, and a three-point guide on what a buddy does in the first two weeks.
• Calendar automation: Create a 30-minute “first day check-in” event on both the manager’s and buddy’s calendars, scheduled for 10 AM on the start date.

Hiring managers get what they need to be ready. Buddies know exactly what’s expected. The new hire walks in on day one with two people already prepared to engage with them.

8. 30/60/90-Day Check-In Sequence

Onboarding doesn’t end at day one — it ends when the employee is fully productive and connected. Most companies stop automated support after the first week. That’s when early-tenure churn risk actually peaks.

• Trigger: Start date confirmed in HRIS. All subsequent steps run on date-relative delays from the start date.
• Day 30: Automated survey link to the new hire — five questions on system access, manager clarity, team integration, and what’s still unclear. Results log to the onboarding tracker and notify HR if any score falls below threshold.
• Day 60: Survey focused on role clarity, workload calibration, and whether expectations set during hiring match reality. Same logging and alert logic.
• Day 90: Final check-in survey plus an automated notification to HR and the manager that the formal onboarding window is closing. Flag for performance review scheduling if applicable.

The survey takes the new hire three minutes to complete. The scenario takes your team zero minutes to manage. HR only intervenes when a score triggers an alert. This is exactly the shift that stops small HR teams from burning out — moving from reactive intervention to system-driven monitoring.

9. Onboarding Completion Audit and HRIS Data Validation

The final workflow closes the loop. After 90 days, your onboarding tracker should show a complete record — every document received, every system provisioned, every check-in logged. Without an audit scenario, you won’t know which records are incomplete until a formal audit surfaces them.

• Trigger: 90 days after start date (date-relative trigger from HRIS).
• Actions: Pull all onboarding checklist fields for that employee from the tracker. Identify any required items marked incomplete or missing. Generate a summary report and send it to the HR coordinator.
• HRIS validation: Cross-reference key fields — emergency contact, direct deposit, benefits election, I-9 status — against required fields in the HRIS. Flag any null values that should have been populated during onboarding.
• Archival: Log the completion audit timestamp to the employee record and move the onboarding tracker row to an archive view.

This workflow catches what slipped. Direct deposit forms that never got submitted. Benefits elections still showing as pending. I-9 records missing Section 2 dates. Catching these at 90 days is far better than catching them at an audit.

Where to Start If You Are Building These for the First Time

Build Workflow 1 first. Without the master trigger, none of the others fire reliably. Once that scenario is tested and stable, add IT provisioning and the pre-boarding welcome sequence — those two have the most visible impact on day-one experience and are the easiest to demonstrate value quickly.

If your team is non-technical and you’re not sure how to get these running, the guide on how non-technical HR teams build their own Make automations with AI walks through the actual process. And if you want to understand how the Make MCP server expands what’s possible for HR teams specifically, read through six ways the Make MCP changes automation work for HR teams.

If you’re not sure which of these workflows applies to your stack first, the OpsMap™ discovery process maps the handoffs before any build starts — identifying which automations close the most expensive gaps for your specific setup. Here’s what OpsMap looks like in practice.

Nine workflows. Most HR teams that build all of them report the same outcome: onboarding stops being something they manage and starts being something that runs. Their job becomes reviewing exceptions. That’s a better use of an HR professional’s time than chasing IT tickets and drafting welcome emails at 9 PM.