How to Automate Internal Mobility with Make.com: A Strategic HR Workflow Guide

Internal mobility fails in most organizations for one reason: the data that would connect a ready employee to an open role exists in three different systems that never speak to each other. Your strategic HR automation blueprint starts with solving that routing problem — not with AI, not with a new platform, but with a structured workflow that moves the right data to the right place at the right time. This guide shows you how to build it.

McKinsey research consistently identifies internal talent mobility as one of the highest-leverage levers for organizational performance — yet most companies still rely on manual processes that guarantee the match never gets made fast enough to matter. Gartner has found that employees who feel they have limited internal growth opportunities are significantly more likely to exit within twelve months. The cost of that exit is measurable: SHRM estimates average replacement costs at roughly one-half to two times an employee’s annual salary when recruiting, onboarding, and productivity ramp-up are included.

Automation doesn’t fix a broken mobility culture. It removes the operational friction that prevents a working mobility culture from producing results.

Before You Start

Before building a single workflow, confirm these prerequisites are in place. Skipping this step is the most common reason internal mobility automation projects stall after launch.

• Data hygiene in source systems. Your HRIS must have accurate job titles, grade bands, and tenure dates. Your LMS must have consistent skill and certification taxonomy — if the same skill is labeled three different ways across courses, your matching logic will fail silently. Audit both systems before connecting them.
• API or webhook access confirmed. Verify that your HRIS, LMS, and ATS each expose the data fields you need via API, webhook, or scheduled export. Engage your IT or vendor support contacts before build week, not during it.
• Defined matching criteria. HR leadership and legal must agree on the logic before it is encoded. Minimum tenure in role, required skill completions, grade-band eligibility, and manager endorsement requirements are common criteria. Document the decision in writing.
• A sandbox environment. Never build and test employee-facing notification workflows directly in production. Use a test environment with dummy employee records to validate every branch before go-live.
• Time budget. Block two to four weeks for a foundational skill-to-role matching workflow. Block six to eight weeks if you are adding multi-stage approvals or AI-assisted scoring. Data readiness is usually the longest dependency — not the build itself.

Step 1 — Map Every Manual Handoff in Your Current Mobility Process

Before automating, document what is actually happening today. Interview the HR team members who manage internal postings, skills tracking, and mentorship programs. Ask one question for each task: “What triggers this, and what do you do next?” Every answer that contains the word “I manually” or “I check the spreadsheet” is a candidate for automation.

Common manual handoffs found in internal mobility processes include:

• Pulling LMS completion reports and cross-referencing with open ATS requisitions
• Emailing employees about roles that match their stated interest areas
• Notifying managers when a direct report completes a development milestone
• Scheduling introductory conversations between internal candidates and hiring managers
• Sending mentorship check-in reminders at 30-, 60-, and 90-day intervals
• Updating the HRIS record when an internal transfer is confirmed

Rank each handoff by frequency and time cost. The highest-frequency, highest-time tasks are your first build targets. Based on our OpsMap™ process work with HR teams, the LMS-to-ATS skill matching step consistently tops this list — it is performed weekly, takes hours, and is entirely rule-based, making it the clearest automation opportunity in the entire mobility workflow chain.

Asana’s Anatomy of Work research found that knowledge workers spend a significant share of their working hours on work about work — status updates, data transfer, and coordination tasks rather than the strategic decisions those tasks are supposed to inform. Internal mobility coordination is a textbook example of this pattern.

Step 2 — Connect Your HRIS, LMS, and ATS as Data Sources

The automation platform acts as middleware between systems that were never designed to communicate. Your first build task is establishing reliable, authenticated connections to each source system — not building matching logic yet. Get the data flowing before you try to route it.

For each system, configure the trigger or polling mechanism:

• LMS: Set up a webhook or scheduled API poll that fires whenever an employee completes a course, earns a certification, or reaches a skill milestone. The payload should include employee ID, skill name (normalized to your taxonomy), completion date, and certification expiry date if applicable.
• HRIS: Pull or receive employee profile data including current role, grade band, tenure in current role, manager ID, and any career interest fields the employee has self-reported. Establish a recurring sync — daily is sufficient for most organizations — so the automation platform always has a current snapshot.
• ATS: Configure a trigger that fires when a new internal requisition is posted or when an existing role is flagged as open for internal candidates. The payload should include role title, required skills (normalized to the same taxonomy as the LMS), grade band, hiring manager ID, and application deadline.

Once all three connections return clean data in a test run, you are ready to build matching logic. Do not skip this validation step. Parseur’s Manual Data Entry Report found that manually re-entered data carries an error rate that compounds across every downstream process — automating a dirty data source does not clean the data, it scales the error.

For organizations exploring how these connections compare to building similar routing in other platforms, the automation tool comparison for HR use cases covers the key integration depth differences in detail.

Step 3 — Build the Skill-to-Role Matching Workflow

This is the core workflow. It runs whenever a qualifying event occurs in either the LMS (new skill completion) or the ATS (new internal role posted) and produces a single output: a structured match record that pairs an eligible employee with a relevant open role.

Build the matching logic in this sequence:

1. Normalize skill labels. Map LMS skill names to ATS required-skill fields using a lookup table. This is the most tedious step and the most important. A mismatch at the label level means qualified employees are never surfaced.
2. Apply eligibility filters. Before any notification fires, run the candidate record through your agreed filter criteria: minimum tenure in current role, grade-band eligibility, required completion status, and manager endorsement flag. Records that fail any filter are routed to a log — not discarded. Log entries allow HR to audit the logic and identify filter criteria that are too restrictive.
3. Score the match (optional at this stage). A simple percentage-match score — number of role’s required skills the employee holds, divided by total required skills — is sufficient for most programs. Reserve AI-assisted scoring for ambiguous cases where multiple candidates have identical scores or where soft-skill alignment is a documented factor. For guidance on layering AI into HR workflows without over-engineering the foundation, build the rule-based score first.
4. Create the match record. Write a structured record to a shared data store — a Google Sheet, Airtable base, or your HRIS — containing employee ID, role ID, match score, filter pass/fail detail, and timestamp. This record is the input for Step 4.

Harvard Business Review research on internal talent markets emphasizes that the quality of the match signal — how accurately the system identifies genuinely qualified candidates — determines whether employees trust the program. A workflow that surfaces irrelevant matches trains employees to ignore notifications. Build the filter logic conservatively and loosen criteria only when data confirms the matches are landing well.

Step 4 — Automate Employee Notifications and Application Routing

A match record that sits in a database produces no value. Step 4 turns the match into action by routing the right notification to the right employee through the right channel, and then capturing their response to initiate the application process.

Configure the notification workflow as follows:

• Trigger: New match record written to the data store with a score above your defined threshold.
• Channel logic: Route notifications through the employee’s primary communication channel — email for most organizations, Slack or Teams if your workforce is chat-native. Do not send to both simultaneously on first contact; choose one and be consistent.
• Notification content: Include role title, hiring manager name, application deadline, a one-sentence summary of why the employee was matched (e.g., “You recently completed Project Management Professional certification, which is listed as a required skill for this role”), and a single call-to-action link.
• Response capture: The call-to-action link should open a lightweight form — not the full ATS application — that asks three questions: Are you interested? Do you have your manager’s awareness? What is your earliest available start date? This removes the cold-start friction of a full application for exploratory candidates.
• Routing on response: A “Yes, interested” response triggers an automated calendar invite for an introductory call with the hiring manager and a task assignment to the HR business partner. A “Not now” response logs a timestamp and suppresses further notifications for that role — but does not remove the employee from future matching cycles.

This same notification architecture applies to automated candidate communication workflows on the external recruiting side — the routing logic is nearly identical, which means organizations building both can reuse significant workflow infrastructure.

Step 5 — Automate Mentorship Matching and Milestone Nudges

Mentorship programs fail operationally, not culturally. The intent is usually strong. The follow-through collapses because no one is responsible for sending the 60-day check-in email, scheduling the mid-program review, or notifying the program coordinator when a pair goes dark. Automation owns all of that.

Build the mentorship workflow in two parts:

Part A — Matching workflow:

• Pull mentor and mentee profiles from the HRIS, including career interest tags, functional area, skill strengths, and geographic location.
• Apply a weighted compatibility score: functional area alignment (40%), skill complementarity — mentor strong where mentee is developing (40%), and scheduling availability overlap (20%).
• Route the top two match options to the mentee for selection. Routing two options rather than one reduces the program coordinator’s involvement to edge cases only.
• On mentee confirmation, send a mutual introduction email to both parties and write the pair record to the HRIS with a program start date.

Part B — Milestone nudge workflow:

• From the program start date, schedule automated check-in prompts at 30, 60, and 90 days. Each prompt goes to both mentor and mentee with a two-question pulse: “Has your pair met in the last two weeks? (Yes/No)” and “Is there anything the program coordinator should know?”
• A “No” response on the meeting question triggers an alert to the program coordinator — not a punitive action, but a flag that the pair may need scheduling support.
• At 90 days, an automated program completion survey fires and the pair record is closed in the HRIS. Completion data feeds back into the employee’s skill profile for use in future mobility matching cycles.

This closed-loop design — where mentorship completion improves the employee’s mobility match score — is the mechanism that connects development investment to talent pipeline outcomes.

Step 6 — Automate Performance Review to Mobility Pipeline Routing

Performance reviews generate readiness signals that most organizations never act on systematically. A manager rates an employee as “ready for next level” in the performance system, and that signal sits in a database until someone manually pulls a report three months later. Automation eliminates the lag.

Configure this workflow to trigger on performance review submission:

• Readiness flag detection: When a submitted review contains a “ready for promotion” or “ready for lateral move” rating above your threshold, the workflow extracts the employee ID, current grade band, and manager comments summary.
• Simultaneous routing: Three actions fire in parallel. First, the HRIS employee record is tagged with a readiness flag and timestamp. Second, the employee’s profile is pushed into the active mobility matching pool — they will now appear in match results for appropriate open roles without any additional HR action. Third, the HR business partner receives an automated briefing: employee name, current role, readiness rating, and a link to the employee’s skills profile.
• Manager confirmation gate: For organizations where manager endorsement is a required filter criterion, insert an approval step before the employee’s profile enters the active pool. The manager receives a single-question confirmation: “Do you support [Name] being considered for internal opportunities?” A yes response clears the filter. A no response logs the decision and routes an alert to HR for follow-up — it does not suppress the employee’s eligibility permanently.

This workflow connects directly to the full employee lifecycle automation framework, where performance data, development records, and mobility history live in a single structured record rather than scattered across disconnected systems.

Step 7 — Build the Internal Transfer Confirmation Workflow

When an internal candidate accepts an offer, the downstream HR tasks are predictable and time-sensitive: HRIS record update, benefits adjustment review, new manager notification, access provisioning for the new team’s systems, and off-boarding from the current team’s workflows. Manual coordination of these tasks is where internal transfers break down — not the hiring decision, but the execution.

Automate the transfer confirmation chain in this sequence:

1. Offer acceptance trigger: ATS marks internal candidate as accepted. This fires the transfer workflow.
2. HRIS update: New job title, grade band, department, manager ID, and effective date are written automatically to the HRIS record. No manual data entry.
3. Notification cascade: Current manager receives a transfer confirmation with the effective date. New manager receives an onboarding checklist and a link to the employee’s skills profile. IT receives an access change request specifying systems to add and systems to remove.
4. Payroll handoff: Updated compensation details (if applicable) are routed to the payroll system with an effective date flag. This step is where data entry errors cause the most damage — the kind of error that turned a $103K offer into a $130K payroll entry, costing David’s organization $27K and the employee’s trust. Automated field mapping eliminates the transcription risk entirely.
5. Transition onboarding trigger: Thirty days before the effective date, a lightweight transition onboarding workflow fires — the same architecture used for customized onboarding workflows, adapted for internal moves where the employee already knows the company culture and systems.

How to Know It Worked

Measure four numbers before go-live and at 90-day intervals after:

• Internal application rate: Of employees who received a match notification, what share submitted the initial interest form? A rate below 15% suggests the match quality or notification channel needs adjustment. A rate above 40% suggests filter criteria may be too broad.
• Internal fill rate: What share of open roles were filled by an internal candidate? Track this separately for roles where the workflow was active versus roles that predated the workflow — the comparison is your clearest ROI signal.
• Time-to-match: Days from role posting to first qualified internal candidate identified. Baseline this from your manual process records. Automated matching should reduce this to hours in most cases.
• Employee mobility satisfaction: A two-question pulse survey sent to all employees who interacted with the system — applied, declined, or were matched — within 30 days of interaction. Ask: “Was the opportunity relevant to your skills and goals?” and “How easy was it to express interest?” Scores below 3 out of 5 on either question indicate a workflow design problem, not a technology problem.

APQC research on talent management maturity consistently shows that organizations with documented, measurable internal mobility processes outperform peers on both time-to-fill and cost-per-hire for mid-level roles. The workflow you build in these seven steps is the operational foundation that makes those metrics achievable.

Common Mistakes and Troubleshooting

Mistake: Building the AI scoring layer before basic routing works. Teams spend weeks evaluating AI matching vendors while the HRIS-to-ATS connection is still manual. Build the data spine first. Get completions flowing, triggers firing, and notifications reaching employees. Then add intelligence on top of a working foundation.

Mistake: Using inconsistent skill taxonomy across systems. If the LMS calls a skill “Data Analysis” and the ATS calls it “Analytical Skills,” your matching logic will never connect them. Taxonomy normalization is unglamorous and essential. Budget time for it before build week.

Mistake: Sending notifications through too many channels simultaneously. Employees who receive the same match notification via email, Slack, and a push notification learn to ignore all three. Choose one channel, be consistent, and optimize based on response rate data.

Mistake: Forgetting the “not now” path. Workflows that only handle “yes” responses create dead ends for employees who are interested but not ready. The “not now” path — logged, suppressed for this role, kept active for future cycles — is as important as the acceptance path.

Mistake: Treating automation as a replacement for HR judgment. Automation surfaces the match and removes the friction. The conversation between an HR business partner and a high-potential employee about their career goals is not automatable — and it shouldn’t be. The workflow’s job is to make sure that conversation happens sooner and with better data, not to replace it. For a broader view of how to reduce costly HR data errors across the function, the automation accuracy framework applies directly to the data quality requirements in this guide.

Next Steps

The seven steps in this guide produce a functioning internal mobility automation spine. From here, two extensions deliver the highest incremental value: integrating a career pathing tool that maps multi-step development trajectories beyond the immediate next role, and connecting your engagement survey platform so that employees who score low on “growth opportunity” questions are automatically flagged for an HR business partner outreach — before they start looking externally.

Both extensions build on the same workflow infrastructure you have already established. The data connections, matching logic, and notification routing you built in Steps 1 through 7 are the foundation for everything that follows.

To see how internal mobility automation fits inside a complete HR operations architecture — from automated candidate screening at the front of the talent lifecycle to transfer confirmation workflows at the back — return to the strategic HR automation blueprint that anchors this entire framework. That pillar covers the sequencing decisions that determine whether your automation investment produces sustained ROI or an expensive pilot that never scales.

If you want an expert assessment of where internal mobility fits inside your current HR automation maturity, our OpsMap™ process identifies the highest-leverage workflow gaps in a structured discovery session — without requiring you to build anything first.