You can build your first onboarding automation in Make.com in one afternoon. Start with one trigger and one action — a new hire row in a spreadsheet or ATS creates accounts, sends a welcome email, and assigns onboarding tasks automatically. No code. Test it with one fake record before you touch a real new hire. This guide walks through the exact steps: pick the trigger, map the fields, add the actions, test, then turn it on. For the full framework behind this approach, see automating employee onboarding the right way.

Most HR teams never build their first automation because they think it requires a developer. It doesn’t. Make.com is a visual, drag-and-drop platform built for exactly this kind of work, and a single onboarding scenario is one of the easiest builds you’ll ever do. If you’ve read about the onboarding tasks you should never do manually, this is the guide that turns that list into a working scenario.

Before You Start: What You Need

You need three things before you open Make.com: a trigger source, a target list of actions, and 15 minutes of uninterrupted focus. That’s it.

Your trigger source is whatever tells the system a new hire exists — a Google Sheet row, a Typeform submission, or an applicant tracking system (ATS) status change. If you don’t have any of these set up yet, start with a Google Sheet. It’s free, it’s fast, and it’s the same trigger logic you’ll use later with a real ATS.

Your action list is the manual checklist you already run for every new hire: create email account, send welcome packet, add to Slack, assign IT equipment ticket, notify the manager. Pick two or three of these for your first build — not all of them. If you haven’t mapped your full system list yet, review the 8 systems to connect before automating onboarding first, so you know what’s actually connectable.

Last thing: don’t build this against a live new hire. Build it, test it with fake data, and only then let it touch a real person’s onboarding.

Step 1: Pick Your Trigger and Connect It

Open Make.com, click Create a new scenario, and search for your trigger app first — Google Sheets, Typeform, BambooHR, or whatever holds your new-hire data today. Add the module and choose the trigger event. For Google Sheets, that’s “Watch Rows.” For an ATS, it’s usually “Watch Records” or “New Candidate — Status Changed.”

Connect your account when prompted. Make.com will ask for OAuth access or an API key depending on the app. Once connected, point the trigger at the exact sheet, tab, or pipeline stage where a confirmed new hire shows up — not your full applicant list. If your trigger fires on every applicant instead of just hires, you’ll flood your systems with false starts.

Run the trigger once with a test row so Make.com pulls a sample data structure. You’ll need this sample in every step that follows.

Step 2: Map the New Hire Fields

Every action downstream needs data: name, personal email, start date, manager, department, role. Before you add a single action module, confirm your trigger source actually captures all of it. This is the step teams skip, and it’s why so many first builds stall out at 60%.

If a field is missing — say, department isn’t a column in your sheet — add it now, not after the scenario is built. Missing structured data is the single biggest reason onboarding automations get abandoned. This is also the exact failure pattern behind the David case: an HR manager entered a number by hand between an ATS and an HRIS, a typo turned $103K into $130K, and the resulting $27K overpayment cost a good employee who quit over the mess. That’s not a warning about carelessness — it’s a warning about unstructured hand-offs. Automate the field mapping and the error stops being possible.

Step 3: Add Your First Action Module

With the trigger data mapped, click the plus icon after your trigger and add your first action app — most teams start with email, since it’s universal and low-risk. Choose Gmail, Outlook, or your email platform’s “Send an Email” action.

Map the fields using the sample data from Step 1: recipient email, first name, start date, manager name. Write the welcome email template directly in the module, using the mapped variables in place of hardcoded text. Test-send it to yourself first.

Add a second action for account creation if your directory tool (Google Workspace, Microsoft 365) has a Make.com integration — most do. This single step is one of the tasks HR teams most commonly still do by hand, and it’s covered in more depth in 9 employee onboarding tasks you should never do manually in 2026.

Step 4: Add a Router if Roles Diverge

Not every new hire needs the same onboarding path. A remote sales rep and an in-office warehouse lead need different equipment, different Slack channels, different training assignments. This is where a Router module earns its place.

Add a Router right after your trigger, then create a filter on each branch — for example, “Department = Sales” on one path and “Department = Operations” on another. Each branch runs its own set of actions from there. This keeps one scenario handling every hire type instead of building five separate scenarios that quietly drift out of sync with each other.

Step 5: Assign Onboarding Tasks Automatically

Add an action module for your project or task tool — Teamwork, Asana, ClickUp, Monday. Use the “Create Task” or “Create Multiple Records” action, and template a standard first-week task list: paperwork, system access requests, first 1:1 scheduling, training modules.

Assign each task to the correct owner using the manager field you mapped in Step 2. This is where automation compounds — instead of one welcome email, you’re now generating a full task list, correctly assigned, with zero manual entry. Recruiters who’ve made this switch report getting real time back: Nick, a recruiter at a small firm, reclaimed 15 hours a week personally and freed up more than 150 hours a month across his three-person team once these hand-offs stopped being manual.

Step 6: Test With a Fake Record

Before this scenario ever touches a real employee, run it against a test row with a fake name, your own email address, and a fictional start date. Watch every module execute in Make.com’s run history. Check that the email arrived correctly, the task list populated with the right assignee, and no field came through blank or mismatched.

Run it three times with three different fake role types if you built the Router in Step 4. Confirm each branch fires its correct action set. Skipping this step is how broken onboarding automations become a new hire’s first impression of your company — the opposite of the goal.

Step 7: Turn It On and Monitor the First Real Run

Set the scenario to run on a schedule (every 15 minutes is standard) or on an instant trigger if your source app supports webhooks. Activate it, then wait for your next real new hire to flow through.

Watch that first live run closely. Check Make.com’s execution history the same day the new hire’s row shows up. Confirm the email sent, the account exists, and the task list assigned correctly. Don’t walk away from the first live execution — treat it the way you’d shadow a new employee’s first shift.

How to Know It Worked

You’ll know this scenario is working when three things are true: the new hire’s accounts and tasks exist without anyone touching a keyboard, the manager gets notified without HR sending a reminder email, and your team stops asking whether the new hire got set up. This is the same shift regional healthcare HR director Sarah made — automating the repetitive setup work gave her back 12 hours a week and cut total hiring time by 60%, time she reinvested in the parts of onboarding that need a human: the first conversation, the culture fit, the questions a new hire is too nervous to ask in week one.

If your process still has gaps after this build, run through the 7 signs your onboarding process is costing you new hires to see what else needs fixing before you scale this further.

Common Mistakes to Avoid

The most common first-build mistake is trying to automate everything in one scenario. Start with two or three actions. Add more once the first version has run cleanly for two full weeks.

The second mistake is skipping the fake-record test and going straight to a live new hire. Every unmapped field or bad filter shows up as a real person’s broken first day.

The third mistake is treating this as a one-and-done build. Onboarding needs change — new departments, new tools, new compliance steps. Revisit the scenario every quarter. The systems you connect before automating onboarding today will not be the same ones you’re running in six months.

Expert Take

The thesis behind this build is automation first, then AI. A lot of HR software vendors want you to believe you need an AI onboarding assistant before you’ve fixed the basics. You don’t. Standardize the process first — one trigger, clean field mapping, a tested action sequence — and you’ll find AI has almost nothing left to clean up, because the mess it would have solved never got created. TalentEdge proved this at scale: after standardizing their onboarding workflow in Make.com, they documented $312K in annual savings and a 207% return on investment. That’s not an AI story. That’s a structure story.

Adoption is the other half of this. Build the automation to run inside tools your team already uses — the same spreadsheet, the same task manager, the same Slack. Nobody has to learn a new system for onboarding to get easier. That’s the whole point.

What This Sets Up Next

Once your first scenario is live and stable, the next moves are paperwork automation and closing the gaps most teams miss on the first pass. Start with how to automate new hire paperwork, then review 10 onboarding automation wins HR teams miss to see what to build next. If questions come up along the way, the onboarding automation FAQ covers the ones we hear most.

According to Make.com’s HR automation resources, connecting core HR systems is consistently the first step organizations take toward broader workflow automation. SHRM’s research on onboarding points to structured, consistent first-week experiences as the strongest predictor of new hire retention — see SHRM’s onboarding guidance. McKinsey’s work on process automation backs the sequencing in this guide: fix the process, then layer in intelligence — read more at McKinsey’s automation and future of work research.

Jeff Arnold is Founder and CEO of 4Spot Consulting and a Make.com Certified Partner.