Detect job and company changes with Lusha bulk enrichment and HubSpot
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This workflow has 8 nodes and runs on a schedule (every 24 hours). Along the way it connects HubSpot, Slack and Lusha (community).
How it runs
Trigger: On a schedule (every 24 hours).
- Get CRM Contacts (HubSpot): get many (contact)
- Format for Bulk Enrichment (Code): runs custom JavaScript code
- Re-Enrich All in Bulk (Lusha): enrich bulk
- Detect Changes (Code): runs custom JavaScript code
- Has Job Changes? (If): checks a condition and branches into true / false
- Update CRM Record (HubSpot): update (contact)
- Alert Rep on Slack (Slack): uses Slack
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that @lusha-org/n8n-nodes-lusha is verified or supports 3.0 (used in Re-Enrich All in Bulk).
Nodes used (6)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - HubSpot
n8n-nodes-base.hubspot - Code
n8n-nodes-base.code - Lusha
@lusha-org/n8n-nodes-lusha.lusha - If
n8n-nodes-base.if - Slack
n8n-nodes-base.slack
From the author
How it works 1. A daily schedule pulls your existing contacts from HubSpot 2. All contacts are bulk-enriched with Lusha in a single API call for efficiency 3. A code node compares current Lusha data against CRM records to detect job title or company changes…