Instant inbound lead qualification
Build an inbound workflow where a name + email triggers Lusha enrichment (person + company), an AI model checks ICP fit, and qualified leads get routed instantly to Slack, HubSpot, and Sheets with full context attached.
Why this works
Inbound doesn’t slow down because sales teams don’t respond. It slows down because leads arrive as partial records. A rep gets a name and an email, then burns 15–30 minutes hunting basics like role, company size, funding, and whether the lead is even worth prioritizing.
This play removes the research step. Verified data fills the gaps, and AI applies the same fit logic every time, increasing both speed and consistency.
What you get
A qualification pipeline that turns “form submitted” into “sales-ready context” in ~2–3 seconds:
- Person enrichment (title, phone, LinkedIn, seniority, location, roles)
- Company enrichment (size + growth, revenue range, funding, industry, tech stack, summary)
- AI output fields: Status (qualified/unqualified), Score (1/0), Reason
- Routing: Slack notification + HubSpot create/update + Sheets log
Impact called out in the post: ~30 minutes of research → ~3 seconds.
How to set it up
Trigger from your form (webhook)
A form submission comes in (Typeform, HubSpot, Cal.com, or any webhook-enabled form). That event starts the n8n flow automatically.
Enrich with Lusha (person + company)
Use two POST calls for enrichment: /v2/person and /v2/company.
This gives you the complete profile + firmographics needed to qualify reliably.
Run AI ICP fit checking
Send the enriched payload to an LLM (Manthan uses Google Gemini) to evaluate your ICP.
Output 3 fields:
- Status: qualified/unqualified
- Score: 1/0
Reason: short explanation (one line)
Route qualified leads instantly
If qualified, trigger three actions:
- Slack message to the SDR with full context (name, title, LinkedIn, phone, email, company + size/funding, etc.)
- HubSpot create/update contact with enriched fields
- Google Sheets log for tracking/reporting
If unqualified, still store it for nurture so nothing disappears.
What to do next
- Add routing rules (territory/segment/round-robin) after the “qualified” decision
- Turn the Reason into a first-touch opener (or sequence selection) so outreach stays contextual
- Add guardrails: dedupe, free-email filters, and “missing-minimum-fields” checks before creating CRM records
The goal: inbound leads don’t wait for research. They arrive qualified enough to act on.
No FAQ items available at this time.
Ready to build this?
Get started with Lusha and set up this play in minutes.
