Ops

Detect job and company changes with Lusha bulk enrichment

DT
Built by: Daniel Turgeman
Difficulty: Medium
Tools: HubSpot ▪ Lusha ▪ n8n ▪ Slack
Type: Template

This play monitors your existing HubSpot contacts to identify career changes—the moments when a key contact moves to a new company or earns a promotion. By comparing your current CRM data against Lusha’s real-time professional database, the workflow identifies discrepancies, updates the contact record, and alerts the sales team.

Instead of losing track of a “warm path” into a new account, your team is notified the moment a past customer or high-value prospect lands in a new role. It eliminates the manual work of LinkedIn auditing and prevents dead records from sitting in your CRM.

Why this works

Your best leads are the people who already know and trust your brand. The challenge is that people change jobs faster than sales teams can track them.

This play operationalizes relationship equity by:

  • Eliminating manual tracking: No more LinkedIn stalking.
  • Preventing database decay: Keeping your CRM data fresh and actionable.
  • Creating “warm path” opportunities: Alerting reps to follow champions to their new companies.
  • Automating the alert loop: Pushing notifications directly to the tools your team uses daily.

What you get

  • Automatic auditing of HubSpot contact records
  • Efficient bulk enrichment via Lusha API
  • Real-time detection of job title or company changes
  • Automated CRM updates with fresh contact data
  • Instant Slack alerts for assigned account owners

How to set it up

01

Install the Lusha community node

Ensure your n8n instance has the Lusha node installed to facilitate the bulk enrichment calls.

02

Connect your credentials

Link your active accounts in n8n for:

  • Lusha: API access for bulk data retrieval
  • HubSpot: Permissions to read and update contacts
  • Slack: Webhook or App access for notifications
03

Define your contact fetch limit

Set the workflow to pull a specific segment of contacts from HubSpot.

  • Tip: Start with “Closed Won” contacts or “Power Users” to prioritize your most valuable champions.
04

Configure the comparison logic

Use the built-in code node to compare:

  • Current HubSpot Company vs. New Lusha Company
  • Current HubSpot Title vs. New Lusha Title
    • If they don’t match, the workflow proceeds to the update stage.
05

Map the update and alert fields

Ensure the new Lusha data (new email, new title, new company) maps correctly back to HubSpot. Configure the Slack message to include:

  • Contact Name
  • Old Role/Company
  • New Role/Company
  • A link to the HubSpot record
06

Activate the daily schedule

Set the trigger to run daily. This ensures your team starts every morning with a list of the latest career moves.

What to do next

  • Automate “New Role” sequences: Trigger a HubSpot workflow that sends a congratulatory gift or email when a change is detected.
  • Execute the “Backfill” play: Use Lusha to find the replacement for the person who just left the account.
  • Monitor “Warm Path” conversion: Track how many new opportunities are opened from contacts who moved companies.

The goal: Your CRM shouldn’t be a graveyard of old titles. This play turns career moves into a competitive advantage, powered by Lusha data and delivered exactly where your reps work.

No FAQ items available at this time.

Related Plays

Ready to run this?

One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.

Get free access Read the Docs