Score and enrich inbound leads with Lusha, Slack, 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 12 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects Slack, HubSpot and Lusha (community).
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Validate Email (Code): runs custom JavaScript code
- Enrich with Lusha (Lusha): uses Lusha
- Calculate Lead Score (Code): runs custom JavaScript code
- Is Hot Lead? (If): checks a condition and branches into true / false
- Respond to Webhook: sends the response back to the webhook caller
- Alert SDR Team (Hot Lead) (Slack): uses Slack
- CRM Upsert (Hot Lead) (HubSpot): uses HubSpot
- Is Warm Lead? (If): checks a condition and branches into true / false
- CRM Upsert (Warm — Outreach) (HubSpot): uses HubSpot
- Notify Warm Lead (Slack): uses Slack
…plus 1 more step. See the full node list below.
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 Enrich with Lusha).
Nodes used (7)
- Webhook
n8n-nodes-base.webhook - Code
n8n-nodes-base.code - Lusha
@lusha-org/n8n-nodes-lusha.lusha - If
n8n-nodes-base.if - Slack
n8n-nodes-base.slack - HubSpot
n8n-nodes-base.hubspot - Respond to Webhook
n8n-nodes-base.respondToWebhook
From the author
How it works 1. A webhook receives a new lead with an email address, which is validated 2. Lusha enriches the lead with seniority, company size, industry, and phone data 3. A lead score is calculated based on ICP fit (seniority, company size, industry match,…