Automate New Decision-Maker at Account → Re-engagement Sequence in n8n — Step by Step
Your CRM is full of accounts marked "closed-lost." A deal died 14 months ago because the VP of Sales who championed it left, and the new decision-maker inherited a stack they didn't choose. Nobody on
Your CRM is full of accounts marked "closed-lost." A deal died 14 months ago because the VP of Sales who championed it left, and the new decision-maker inherited a stack they didn't choose. Nobody on your team is watching for that. The account sits frozen while a warmer buyer than you'll ever cold-source walks into the building. This workflow watches for exactly that moment — a new executive landing at a dead account — and fires a fresh, context-aware outreach sequence automatically.
The problem: closed-lost accounts go dark forever
Most sales motions treat "closed-lost" as terminal. The record gets a reason code, drops out of active pipeline, and never resurfaces unless a rep manually revisits it. But losses are rarely permanent — they're timing. The most common reasons a deal dies (no budget this cycle, an incumbent contract, an internal champion who couldn't get buy-in) all expire when the org chart changes.
New decision-makers are the single strongest re-engagement trigger in B2B. A new VP of Sales, Head of Ops, or CRO arrives with a mandate to change things, a fresh budget, and zero loyalty to the vendor your prospect rejected. The window is short — the first 90 days, before they've re-signed the incumbent or standardized their new stack. Manually monitoring hundreds of closed-lost accounts for personnel changes is impossible, so it never happens. The intent signal is real; the detection is the bottleneck.
The solution: detect the change, trigger the sequence
The workflow does three things on a loop. First, it pulls your closed-lost accounts from the CRM. Second, it checks each account's key roles against a data source that surfaces new hires and role changes — LinkedIn-derived enrichment, a signals API like Clay or Apollo, or job-change alerts. Third, when it finds a new person in a target role, it enriches their contact details and drops them into a personalized re-engagement sequence that references the account's history without being creepy about it.
The messaging matters. A new decision-maker doesn't know the old deal existed, so the angle isn't "we spoke before" — it's "congrats on the role, here's how teams like yours solve X." The workflow's job is to catch the timing; the copy's job is to feel like a well-timed intro, not a resurrected dead lead.
Step-by-step: building it in n8n
Here's the node-by-node structure. Adapt the CRM and enrichment nodes to your stack, but the skeleton holds regardless.
1. Schedule Trigger
Start with a Schedule Trigger node set to run daily (a Cron expression of 0 8 * * * for 8 a.m.). Personnel changes don't need real-time detection — a daily sweep catches new hires well within the useful window and keeps API costs down.
2. Pull closed-lost accounts
Add your CRM node — HubSpot, Salesforce, or Pipedrive. Use the "Get Many" operation with a filter on deal stage equal to closed-lost. In HubSpot, filter deals by dealstage; in Pipedrive, query deals with status = lost. Return the associated company and the primary contact's title so you know which role to monitor. Add a filter so you only pull losses from the last 24 months — older accounts have too much drift to be worth the enrichment spend.
3. Loop and enrich for role changes
Feed the accounts into a Loop Over Items (Split in Batches) node to process them one at a time and respect rate limits. Inside the loop, add an HTTP Request node calling your enrichment provider (Apollo, Clay, People Data Labs, or a LinkedIn signals API). Query the company for current people in your target roles — VP Sales, Head of RevOps, whatever persona bought your product. Return name, title, start date, and LinkedIn URL.
4. Compare against known contacts
Add a Code node (JavaScript) or an IF node that compares the enriched person against the contact already on the CRM record. The logic: if the current role-holder's name differs from the stored contact and their start date is within the last 120 days, flag it as a new decision-maker. Storing a "last checked" timestamp and previous role-holder on the CRM record — or in an n8n Data Store / external table — prevents you from re-triggering on someone you already caught.
5. Get contact details
For flagged accounts, add another HTTP Request node to your email-finding service (Apollo, Hunter, Dropcontact) to resolve a verified work email. Route unverified emails to a separate branch so you never burn sender reputation on guessed addresses.
6. Enroll in the sequence
Push the new contact into your outreach tool. Use the native node for Smartlead, Instantly, or Lemlist, or an HTTP Request to your sequencer's API. Pass merge fields — first name, company, role, and a variable for the original loss reason so the copy can adapt. Simultaneously write back to the CRM with a CRM update node: create a new contact, re-open a lightweight opportunity, and log a note ("New DM detected — auto re-engaged") so reps see the context the moment they open the record.
7. Notify the owner
End with a Slack or Email node that pings the original account owner: "New VP at [Account] — re-engagement sequence started." This keeps a human in the loop for the accounts that warrant a personal touch on top of the automated cadence.
The benefits: compounding pipeline from dead data
The economics are hard to beat. The accounts are already in your CRM — no prospecting cost. The intent signal (new leadership, new budget, new mandate) is stronger than anything you'll find cold. And because it runs on a schedule, the value compounds: every closed-lost account you accumulate becomes a monitored asset that can wake up at any time. A 500-account closed-lost pile that used to be a graveyard becomes a passive lead source generating a handful of qualified re-engagements every month.
It also fixes an attribution blind spot. Most teams can't tell you how much revenue they leave in closed-lost. Once this runs, you have a clean number: DMs detected, sequences fired, meetings booked, revenue recovered — a dashboard line item that used to be zero.
Common pitfalls to avoid
Referencing the dead deal too directly. The new decision-maker has no relationship with your brand. "Following up on our conversation" is a lie to them. Write the sequence as a fresh, role-relevant intro that happens to be well-timed.
Skipping email verification. Enrichment guesses are wrong often enough to hurt your domain reputation. Always route through a verification step and drop anything below a confidence threshold. Warm your sending domain before scaling volume.
No deduplication state. Without storing who you've already flagged, the workflow re-triggers on the same person every day. Persist a "last processed contact" field and a timestamp on each account, and gate the sequence on genuine change.
Ignoring rate limits. Enrichment and email-finder APIs throttle hard. Use Split in Batches with a Wait node between calls, and wrap HTTP nodes with n8n's retry-on-fail so a single 429 doesn't kill the run.
Monitoring the wrong role. A new office manager isn't a buying signal. Scope your enrichment query tightly to the persona who actually owns the purchase decision for your product, or you'll drown the sequence in noise and train reps to ignore the alerts.
Start narrow — one CRM, one target role, a daily sweep of your last 12 months of losses. Watch the first week of flags, tune the role filter and the copy, then widen the window. The infrastructure is the same whether you're monitoring 50 accounts or 5,000; only the enrichment bill scales.
Ja construimos isso pra voce
Nao comece do zero. O New Decision-Maker at Account → Re-engagement Sequence e um workflow n8n pronto para instalar — conecta suas ferramentas em minutos, sem codigo.
Instalar por $79 →
