TL;DR
- How to Build a Job Change Trigger Workflow for B2B Outbound (2026) breaks down the key infrastructure needed to scale outbound revenue effectively.
- A purely signal-based approach prevents burning total addressable market (TAM) bandwidth.
- Modern systems rely on dynamic workflows and smart orchestration over raw volume.
Contents
- Why Job Changes Are the Highest-Converting Outbound Signal
- The Job Change Trigger Workflow: Architecture
- Step-by-Step: Building the Job Change Trigger in n8n + Clay
- Two Plays from One Signal: New Company + Replacement at Old Company
- Expected Results from Job Change Outbound
- FAQ: Job Change Trigger Workflow for B2B Outbound
When a warm contact changes jobs, two things happen: they bring your brand to a new company, and their replacement at the old company needs to rebuild the stack. One signal. Two pipeline opportunities.
Job change trigger outbound is the practice of detecting when contacts in your database move to new companies and automatically routing them into outbound sequences — at their new company, and at their old one. In our campaign data, job change signals produce the highest reply rates of any trigger: 6–10%.
The reason is simple: these aren't cold contacts. They've already engaged with you. They know your product. And their new company — or their replacement — probably doesn't. That's a warm conversation in a new account, triggered automatically.
Here's how to build the workflow.
Why Job Changes Are the Highest-Converting Outbound Signal
Every outbound signal has a logic. Website visits mean someone is researching. Funding rounds mean budget is available. Hiring signals mean headcount is growing.
Job changes mean something stronger: a person who already knows you is now in a position to buy at a company that doesn't have your solution.
What makes this signal different:
Warm relationship. You've already interacted. They opened your emails, replied to your outreach, took a meeting, or at least knew your brand. Cold approach isn't needed.
New decision-making authority. Someone who was a VP Sales at Company A and moves to Company B as CRO now has budget and authority at an account you've never touched.
Urgency. New hires in leadership roles have a 90-day window where they're actively building their stack, evaluating vendors, and making purchase decisions. After that window closes, inertia sets in.
Double opportunity. The person left. Their replacement probably needs to re-evaluate the tools and partners the departing person used. That's a second entry point from the same signal.
The Job Change Trigger Workflow: Architecture
The workflow has five stages:
1. DETECT → Apollo/LinkedIn surfaces job change
2. ROUTE → n8n receives signal, checks criteria
3. ENRICH → Clay enriches new contact data
4. SPLIT → Two sequences: new company + replacement
5. SEQUENCE → Smartlead sends appropriate cadence
Detection layer: Apollo has a job change detection feature that flags contacts in your saved lists who change roles. LinkedIn Sales Navigator also surfaces job changes in its alerts feed. Both can push data to n8n via webhook or scheduled API call.
Routing layer: n8n receives the job change data and checks: Does the contact's new company match our ICP? Was this a meaningful role change (not a lateral move at the same company)? Is the contact already in an active sequence?
Enrichment layer: Clay enriches the contact at their new company — new email, new company data, new personalisation context. The old company data is also enriched to identify the replacement contact.
Split logic: Two workflow branches fire simultaneously. Branch A targets the warm contact at their new company. Branch B targets the replacement at the old company.
Sequence layer: Each branch enters a distinct Smartlead sequence — warm reactivation for the known contact, cold-with-context for the replacement.
Step-by-Step: Building the Job Change Trigger in n8n + Clay
Step 1: Set up job change monitoring in Apollo
Create a saved list in Apollo containing your key contacts — people who've engaged with your outbound, taken meetings, or exist in your CRM as warm contacts. Apollo monitors this list and flags job changes weekly.
Set up an Apollo webhook that fires when a job change is detected.
Step 2: Create the n8n workflow
Webhook trigger: n8n receives the Apollo webhook payload containing the contact name, old company, old title, new company, new title.
ICP check (Set/IF node): Does the new company match your ICP criteria? Check headcount, industry, and funding stage against your parameters. If no match, log it and stop. Not every job change is a pipeline opportunity.
Deduplication check (HTTP/CRM node): Is this contact already in an active Smartlead sequence? Query your CRM or Smartlead to check. If they're already in sequence, skip.
Step 3: Enrich the new contact in Clay
Branch A — Known contact at new company: n8n sends the contact to a Clay table. Clay enriches: new work email (via waterfall), new company data, recent LinkedIn activity at the new company. Claygent generates a personalised first line referencing the job change and your previous interaction.
Branch B — Replacement at old company: n8n sends the old company name and old job title to a different Clay table. Clay identifies probable replacements — people who recently joined the old company in the same or similar role. Enrichment and email verification run on the replacement contact.
Step 4: Push to Smartlead sequences
Sequence A (warm reactivation): 3–4 emails over 14 days. Tone: personal, referencing the job change and your previous relationship. Not a hard sell — a re-engagement.
Example first email hook: "Saw you moved to [New Company] as [New Title] — [previous interaction reference]. Curious whether [problem we solve] is on your radar at the new place."
Sequence B (replacement outreach): 4–5 emails over 21 days. Tone: contextual cold — you're not starting from zero because you know the company's history with you. But the contact is new.
Example first email hook: "Your predecessor [Name] was evaluating [solution area] when they moved on. Figured [Old Company] is probably re-evaluating that now."
Two Plays from One Signal: New Company + Replacement at Old Company
This is the part most teams miss. They see a job change and reach out to the contact at their new company. Good. But they forget the old company entirely.
The new company play: Warm relationship + new budget + 90-day decision window = high conversion. The contact already trusts you. The new company doesn't have your solution. This is as close to inbound as outbound gets.
The replacement play: Less warm, but highly contextual. The replacement is inheriting a function. They need to evaluate existing vendors and tools. If you can reference the previous person's engagement ("We were working with your team on X") you have instant credibility.
Both plays run automatically from a single signal. One n8n workflow. Two Clay tables. Two Smartlead sequences. Zero manual prospecting.
Expected Results from Job Change Outbound
| Metric | New company play | Replacement play |
|---|---|---|
| Reply rate | 6–10% | 3–5% |
| Meeting conversion | 40–60% of replies | 20–35% of replies |
| Average sequence length | 3–4 touches | 4–5 touches |
| Time from signal to first email | 4–24 hours | 24–48 hours (replacement takes longer to identify) |
Volume expectations: If you have 1,000 contacts in your monitoring list, expect 3–5% job changes per quarter (30–50 signals). That's 30–50 warm reactivation opportunities plus 30–50 replacement opportunities per quarter — from contacts you've already invested in acquiring.
These aren't vanity numbers. Job change signals consistently produce the highest-quality meetings in our pipeline because the relationship already exists.
Signal-Based Prospecting Triggers Playbook — Download Free
The full playbook covering all 12 trigger types, including the job change workflow, with n8n architecture diagrams and Clay table templates.
Download the Triggers Playbook →
FAQ: Job Change Trigger Workflow for B2B Outbound
How do I detect job changes for B2B outbound?
Apollo monitors your saved contact lists and flags job changes. LinkedIn Sales Navigator also alerts you to job changes in your saved leads. Both can push notifications to n8n via webhook. The detection runs automatically on a weekly schedule — no manual LinkedIn checking required.
What reply rate should I expect from job change outbound?
Warm contacts at new companies produce 6–10% reply rates in our data. Replacement contacts at old companies produce 3–5%. Both outperform cold list sends (1–2%) because the signal indicates timing advantage and, for the warm contact, an existing relationship.
Do I need separate sequences for job change outreach?
Yes. The warm reactivation sequence (known contact, new company) is shorter, more personal, and references your previous interaction. The replacement sequence (new contact, old company) is more contextual cold — it references the previous engagement but introduces your value proposition from scratch. Using the same sequence for both wastes the relationship advantage on the warm contact.
How many job changes should I expect in my database?
Roughly 3–5% of your contact database changes jobs per quarter. For a database of 1,000 contacts, that's 30–50 signals per quarter. This grows as your database grows. The key is monitoring contacts you've already invested in acquiring — warm contacts, past meeting attendees, and CRM contacts.
Yananai A. Chiwuta
Author
Yananai Chiwuta is a Go-To-Market Architect and founder of Forma Nôrden. He builds signal-based outbound systems for B2B SaaS companies scaling from $500K to $20M ARR, and authors The GTM Moat. Previously founded and exited FunnelVision.
Celine Sky
Reviewer
Celine ensures technical accuracy and strategic alignment across all Forma Nôrden playbooks and resources.
