Internal talent leaves because employees never see the open role until it’s gone. Nine Make.com workflows fix the visibility gap—from multi-channel broadcast the moment a requisition opens to automated follow-up after an internal hire lands. This post covers each one in build order so you can deploy them as a stack.

External recruiting automation gets all the press. Internal mobility automation gets ignored—and that’s where companies bleed talent. McKinsey research shows employees who see real career development pathways stay longer and perform at higher levels. Most organizations still rely on departmental emails and manager word-of-mouth to surface internal roles. That’s not a mobility strategy; it’s a lottery.

The nine workflows below are part of the broader Recruiting Automation with Make.com: 10 Campaigns for Strategic Talent Acquisition framework, pulled out and expanded here because the internal mobility problem is distinct enough to warrant its own treatment. Build these in sequence. Each one feeds the next.

Why Internal Job Posting Automation Is a Separate Problem

External candidates don’t know your company. Internal candidates know it too well—they know the informal hierarchy, they worry about confidentiality, and they aren’t sure whether applying will damage their relationship with their current manager. Automation that just replicates external job board logic inside the firewall fails because it doesn’t address those dynamics.

The operational case is also clear. SHRM data shows internal hires ramp to full productivity significantly faster than external hires and cost less to onboard. Parseur’s Manual Data Entry Report puts manual HR data processes at an average of $28,500 per employee annually in lost productivity. Internal posting workflows that require manual copy-paste across systems are a direct contributor to that number.

The nine workflows below address the process, not just the plumbing.

Workflow 1: ATS New-Role Trigger → Instant Multi-Channel Internal Broadcast

This is the foundation. Everything else builds on it.

• Trigger: New requisition created in your ATS with the “Internal” or “Internal First” flag set
• Actions: Post a formatted job card to your internal Slack channel, Microsoft Teams channel, and intranet or careers page simultaneously
• Data pulled: Role title, department, hiring manager name, salary band if disclosed, application deadline, direct application link
• Filter logic: Only fires on internal-flagged roles—external postings bypass this scenario entirely

Without this workflow, every other internal mobility effort stays manual. This one scenario eliminates the three-to-five day lag between a role opening and employees seeing it. That lag is the exact window where top internal candidates start exploring outside options.

Build this first. It’s the highest-leverage workflow in the stack and the prerequisite for every workflow below.

Workflow 2: HRIS Skills-Profile Matching → Targeted Employee Notification

Mass email blasts to all employees for every internal role generate noise, not candidates. Skills-profile matching generates signal.

• Trigger: Same ATS new-role event from Workflow 1
• Logic: Pull required skills tags from the job requisition → query HRIS employee records for matching skills, certifications, or job title history → build a filtered list of eligible employees
• Notification: Personalized direct message (Slack DM or email) to each matched employee, referencing the specific skills that make them a fit
• Exclusion filter: Skip the employee’s current manager and any employees already in an active separation workflow

The personalization is the point. “We think you’d be a strong fit for this role based on your background in X” converts at a higher rate than a generic all-hands announcement. Make.com handles the filtering and message assembly—you’re not doing it by hand.

This workflow works best when your HRIS has structured skills data. If it doesn’t, start with job title matching as a proxy and add skills tagging as a parallel project.

Workflow 3: Internal Application Submission → Instant Confirmation + Hiring Manager Alert

The moment an employee submits an internal application, two things need to happen simultaneously: they need confirmation, and the hiring manager needs to know.

• Trigger: Application submitted through your internal careers portal or ATS with source tagged as “Internal”
• Applicant action: Automated email confirming receipt, estimated timeline, and a note that their current manager will not be notified until a specific stage (address the confidentiality concern directly)
• Hiring manager action: Slack DM or email with the applicant’s name, current role, tenure, and a link to their application in the ATS
• HRIS pull: Make.com queries the HRIS at submission time to append current performance data or tenure length to the hiring manager notification, based on what your system exposes via API

The confidentiality message in the applicant confirmation reduces drop-off. Employees who aren’t sure when their manager gets notified apply at a lower rate. Removing that ambiguity up front increases your internal applicant pool.

Workflow 4: Automated Interview Scheduling for Internal Candidates

Internal candidates are already in your systems. That means scheduling automation can pull from known calendars rather than relying on back-and-forth coordination.

• Trigger: ATS status change to “Phone Screen Scheduled” or “Interview Stage” for an internal candidate
• Actions: Make.com pulls availability from hiring manager’s Google Calendar or Outlook → generates a scheduling link with pre-populated time slots → sends to the internal candidate via email or Slack DM
• Calendar block: On confirmation, creates calendar events for both parties with the interview format, video link, and any prep materials attached
• Reminder sequence: 24-hour and 1-hour reminders fire automatically

This workflow removes recruiter coordination entirely for internal candidates. The scheduling link does the work. Recruiters spend time on conversations, not calendar logistics.

Workflow 5: Status Update Notifications Throughout the Process

Internal candidates who don’t hear back after applying assume rejection and start looking outside. Status update automation closes that loop without requiring recruiter bandwidth.

• Trigger: ATS status change on any internal application—any stage
• Actions: Templated notification to the applicant with their current stage, next steps, and estimated timeline
• Tone differentiation: Use separate message templates for “advancing” vs. “not advancing” vs. “role on hold”—the language matters, and Make.com routes to the right template based on the status code
• Manager hold: Notification to current manager fires only at a defined stage (typically after an offer is extended), not at every status change

The manager notification timing is a configuration decision your HR team makes once. After that, Make.com enforces it consistently. No more situations where a manager learns about an internal move through the grapevine before HR has a conversation with them.

Workflow 6: Internal Referral Capture and Tracking

Employees refer the best candidates—internal and external. Most organizations have no structured way to capture those referrals for internal roles or track whether they resulted in a placement.

• Trigger: Employee submits a referral form (embedded in your intranet, Slack, or a simple Make.com-connected form)
• Actions: Create a referral record in your ATS tagged to the referring employee → notify the referred employee that a colleague flagged them for the role → route a summary to the recruiter
• Tracking: Make.com logs each referral, ties it to the final hiring outcome, and can push summary data to a Google Sheet or Airtable dashboard for reporting
• Recognition trigger: If the referral converts to a hire, an automated message fires to the referring employee acknowledging the outcome

The recognition trigger at the end of the workflow is what drives referral volume. Employees refer more when they know the referral landed. Closing the loop takes one additional step in Make.com and costs nothing in recruiter time.

Workflow 7: Internal Offer Letter Generation and Delivery

Offer letter generation for internal moves involves different variables than external hires—start date coordination, backfill timing, transition planning. Manual processes here create delays that frustrate both the candidate and the receiving manager.

• Trigger: ATS status change to “Offer Approved” for an internal candidate
• Actions: Make.com pulls offer data from ATS → populates an offer letter template in Google Docs or your document generation tool → routes to the approver for signature via your e-signature platform → delivers the signed document to the candidate
• Parallel action: Notify current manager and HR business partner simultaneously that an offer is out, with the proposed transition date, so backfill planning starts immediately
• Deadline reminder: If the candidate hasn’t responded within 48 hours, an automated reminder fires

The parallel notification to the current manager and HRBP is the operational win here. Backfill timelines start the day the offer goes out, not the day the candidate accepts. That’s weeks of planning time recovered on every internal placement.

Workflow 8: Transition Coordination Between Departing and Receiving Managers

The handoff between an employee’s current manager and their new manager is where internal moves fall apart. No one owns it, nothing is structured, and the employee gets pulled in two directions.

• Trigger: Internal offer accepted—ATS status changes to “Accepted” for an internal candidate
• Actions: Make.com creates a shared transition task list in your project management tool (Teamwork, Asana, or equivalent) with assigned owners for each step
• Automated notifications: Both managers receive a transition timeline with defined milestones—knowledge transfer window, last day in current role, first day in new role, system access changes
• HR touchpoint reminders: Automated reminders to the HR team at each milestone to check in and unblock issues
• IT/systems trigger: Make.com can fire a webhook to your IT ticketing system to queue access changes on the correct date, not after someone remembers to submit the ticket

The IT webhook at the end of this workflow alone prevents a category of recurring delays. Access provisioning on the wrong timeline is one of the most common friction points in internal moves. Automating the trigger removes the dependency on someone remembering to file the ticket.

Workflow 9: Post-Placement 30-Day Check-In and Talent Pool Update

The workflow most organizations skip entirely. Thirty days after an internal hire lands in their new role, you have a window to assess fit, capture feedback, and update your internal talent database before the moment passes.

• Trigger: 30 days after the internal start date recorded in HRIS
• Actions: Automated check-in survey sent to the placed employee and the receiving manager (separate surveys, separate questions)
• Data routing: Survey responses feed into Airtable or Google Sheets for aggregate reporting → flag any low-score responses for HR follow-up
• Talent pool update: Make.com writes back to the HRIS or internal talent database—the employee’s profile now reflects their new role, skills applied, and mobility history
• Pipeline close-out: ATS record is closed with outcome data logged; the internal referrer (if applicable) gets a final notification

The talent pool update is the long-game payoff. Every internal placement that gets properly logged makes Workflow 2’s skills-matching more accurate on the next cycle. The system compounds over time because each placement improves the data behind the next one.

How These Workflows Connect to a Broader Automation Strategy

None of these nine workflows are complicated in isolation. The operational leverage comes from running them as a connected stack. Workflow 1 broadcasts. Workflow 2 targets. Workflows 3 through 5 keep candidates informed. Workflows 6 through 9 close the loop on referrals, offers, transitions, and placement quality.

The team that builds this stack does so inside a broader OpsMesh™ architecture—a structured approach to connecting systems so automation decisions in one workflow don’t break something downstream in another. If you’re starting from scratch on your internal mobility automation, an OpsMap™ discovery session is where that work begins: mapping what you have, identifying where data lives, and sequencing builds in the right order so you’re not reworking the foundation six months in.

For HR teams running lean, the starting point is almost always Workflow 1 and Workflow 5. Broadcast and status updates. Get those two running and you’ve eliminated the most damaging failure modes—employees who never saw the role and employees who applied and heard nothing. Everything else layers on top of that foundation.

The Make MCP has changed how fast these builds happen. What used to take a consultant a week to wire up now takes a fraction of that time when AI handles the module configuration and routing logic. That speed difference matters most for HR teams that need the workflow running before the next open requisition hits—not three months from now.

Internal talent mobility isn’t a benefits program. It’s an operational system. Build it like one.