Build a Key Contact Left → Relationship Save + New Intro Request Workflow with n8n

Your biggest deal doesn't die when the contract ends. It dies the day your champion updates their LinkedIn to a new company logo — and nobody on your team notices for three weeks. By then the renewal conversation is happening with a stranger who has no memory of why they bought you, and the person who actually loved your product is now a warm lead at a brand-new account you're not even tracking. This workflow closes both gaps automatically.

The problem: churn hides inside a job change

Every B2B account has a single point of failure — the internal champion who runs your tool, defends the budget line, and forwards your emails to procurement. When that person leaves, three things happen at once, and all of them are invisible to your CRM by default:

• The account goes cold. Their replacement inherits a tool they didn't choose and often has a mandate to cut costs. Renewal risk spikes, but your health score still shows green because usage data lags.
• Your best reference walks out the door. The person who just left was your strongest advocate. At their new company they have budget authority, an unsolved problem you already fixed once, and warm memory of your product — and you do nothing with it.
• Nobody gets assigned. The AE who owns the account is buried in their pipeline. The CS manager assumes someone flagged it. The signal evaporates.

Sales teams treat champion departure as an occasional surprise. It isn't — it's a predictable, high-frequency event. Average B2B tenure in a role is under two years, so a book of 200 accounts throws off a champion change roughly every few days. You just aren't catching them in time.

The solution: detect the departure, fire two motions at once

The Key Contact Left → Relationship Save + New Intro Request workflow turns a job change into two automated plays running in parallel:

1. Relationship Save — the account is flagged at-risk, a task is created for the owning AE/CSM, and a re-engagement sequence targets whoever inherited the seat before the renewal clock forces a bad conversation.
2. New Intro Request — the departed champion becomes a fresh opportunity. Because they already trust you, you reach out at their new company and ask for the warm intro to whoever owns your category there.

The trigger is a change-of-employment signal. You can source it from a data provider (Clearbit/People Data Labs enrichment webhooks, LinkedIn Sales Navigator alerts exported via a connector, or a job-change API like Champify or UserGems). n8n is the glue that listens for the signal, decides which account it belongs to, and orchestrates both motions without a human babysitting a spreadsheet of contacts.

Step-by-step: building it in n8n

Here's the node-by-node structure. Assume a CRM (HubSpot or Pipedrive) as the system of record and a job-change signal arriving by webhook.

1. Capture the departure signal

Start with a Webhook node (HTTP POST) as the entry point for your enrichment provider, or a Schedule Trigger node running every 6 hours if you poll an API instead. If polling, follow it with an HTTP Request node calling your provider's "contact updates" endpoint, passing your API key in the header credentials. Set the response format to JSON so downstream nodes can address fields directly.

2. Confirm it's a real job change

Add an IF node. Test that {{ $json.event_type }} equals job_change and that the new company domain differs from the old one — enrichment providers sometimes fire on title changes within the same company, which you don't want. Route only true departures downstream; dead-end the rest with a NoOp node so the execution log stays clean.

3. Match the contact back to an account

Use the HubSpot node (operation: Search Contact) or an HTTP Request to your CRM's search API, querying by the contact's email or LinkedIn URL. This tells you which account they were the champion for and whether that account is a paying customer. Add a Set node right after to normalize the fields you'll reuse — account_id, account_owner, old_company, new_company, contact_name, renewal_date — so later nodes don't dig through nested JSON.

4. Split into two branches

Drop a Switch or simply wire two paths off the Set node so both motions run in parallel.

Branch A — Relationship Save:

• HubSpot / Pipedrive node (operation: Update Deal or Update Company) — set a custom property risk_flag = champion_departed and drop the health score.
• HubSpot Create Task node — assign to {{ $json.account_owner }} with due date today and body: "Champion {{contact_name}} left {{old_company}}. Re-engage successor before {{renewal_date}}."
• Slack node — post to the account team channel with the same context so the human sees it in real time, not at the next QBR.

Branch B — New Intro Request:

• HubSpot Create Contact / Create Deal node — create a new opportunity at {{ new_company }}, source = "champion_moved", pre-populated with the relationship history.
• Gmail / Send Email node (or your sales-engagement tool's API via HTTP Request) — send a personalized note to the champion at their new address: congratulate the move, then ask for the intro to whoever now owns your category.

5. Add a human checkpoint and logging

Route Branch B's outreach through a Wait node or a Slack approval step if you want an AE to eyeball the email before it sends — warm intros are too valuable to automate blindly. Finish both branches with a Google Sheets or Airtable Append node so every departure event is logged with timestamp, account, and action taken. That log is your audit trail and your source of truth for measuring the workflow's impact.

Benefits: two revenue motions from one signal

Once this runs, the math changes fast:

• Renewal risk caught weeks earlier. Instead of discovering the champion left during the renewal call, your CSM is re-engaging the successor while there's still time to rebuild the relationship. Even a 5-point improvement in at-risk retention pays for the entire automation many times over.
• A warm pipeline you were throwing away. Champions who move take their trust with them. Firing an intro request the week they land turns your existing customer base into a self-replenishing lead source — the highest-converting kind, because there's no cold-start.
• Zero manual monitoring. Nobody has to watch LinkedIn or scrub contact lists. The signal arrives, the plays fire, the humans get a task and a Slack ping with full context.
• A closed-loop dataset. Your logging sheet tells you exactly how many saves and intros the workflow generated, so you can prove ROI instead of guessing.

Common pitfalls (and how to avoid them)

Firing on false positives. Enrichment feeds are noisy. Without the domain-comparison check in your IF node, you'll spam AEs with tasks every time someone gets promoted. Always validate that the company changed, not just the title.

No dedupe. Providers can send the same job-change event multiple times. Add a lookup against your logging sheet — a Google Sheets read + IF node — before creating tasks, so one departure doesn't spawn five duplicate opportunities. Alternatively, store a processed-contacts key and skip anything already handled.

Automating the intro email fully. A robotic "congrats on the new role, buy from us" note burns the relationship you're trying to bank. Keep a human approval step on Branch B, and template the email with genuine personalization tokens rather than a mass-blast tone.

Rate limits and credentials. HubSpot and Gmail both throttle. Configure the batching option on your CRM nodes and store API keys in n8n's credential manager — never hardcode them in an HTTP Request node's header field where they'll leak into execution logs.

Ignoring the renewal date. The whole point is timing. Pull renewal_date into the task body and, if it's inside 60 days, escalate the Slack alert with an @-mention. A save attempt that lands after the renewal already lapsed is just a post-mortem.

Build it once and it runs quietly in the background, converting your single most predictable churn event into two shots at revenue — one defensive, one offensive — every single time a champion moves.

PRONTO PARA USAR

Ja construimos isso pra voce

Nao comece do zero. O Key Contact Left → Relationship Save + New Intro Request e um workflow n8n pronto para instalar — conecta suas ferramentas em minutos, sem codigo.

Instalar por $79 →