Zapier is the fastest path to production for teams that want results without writing code. Perfect for: inbound forms, quick scoring logic, and Slack alerts.
What you’ll build
A three-step score that combines:
Company enrichment → ICP fit
Person enrichment + email confidence → trust layer
Signals → timing multiplier
Prerequisites
- Lusha API or
- CRM (Salesforce/HubSpot)
- Slack or Microsoft Teams (optional)
Flow overview
Trigger: New lead in CRM (or “New form submission” via webhook).
Company enrich: Lusha Company → employee_count, industry, revenue_band.
Person enrich: Lusha Contact → title, seniority, phone, email, email_confidence.
Filters/Paths: Apply score + validation.
Signals check: Optional step for funding/hiring indicators.
Update lead: Write score + disposition to CRM.
Notify: Post context to Slack.
Field mapping (minimum)
- Company domain → Lusha Company input
- Lead email and/or name + company → Lusha Person input
- Outputs to CRM:
lusha_employee_count,lusha_industry,lusha_title,lusha_seniority,lusha_email_confidence,lusha_phone,lead_score,lead_disposition
Scoring model (example)
Fit (Company)
Employee count 50–500: +20
Industry in target list: +15
Trust (Person)
Email confidence ≥ 90: pass (else fail or send to manual queue)
Seniority Director/VP/C-level: +25
Timing (Signals)
Funding in last 90 days: +30
Hiring surge for relevant roles: +10
Thresholds
- ≥ 60 = Route to SDR now
- 35–59 = Nurture
- < 35 or failed confidence gate = Suppress / Manual validate
Build steps in Zapier
Trigger: Salesforce “New Lead” (or HubSpot contact created).
Action: Lusha Connect → Enrich Company (map domain).
Action: Lusha Connect → Enrich Contact (map name/email + company).
Filter: Email confidence ≥ 90 (fail → “Manual validation” Google Sheet).
Paths:
– Hot path: employee_count in range AND industry in list → set
lead_scorewith Formatter step (numbers + lookup table).– Warm path: partial fit → lower score.
Action: CRM → Update lead fields + owner (round robin).
Action: Slack → message with name, company, score, phone, seniority, funding flag.
Testing
- Run three samples: a high-fit + high-confidence lead, a mid-fit lead, and a low-confidence email.
- Confirm score math, routing, and Slack payload.
Pitfalls to avoid
- Overwriting trusted CRM fields without a confidence or “is_empty” check.
- Mixing free-text industries with picklists; normalize with Formatter.
- Skipping dedupe—avoid duplicate contacts before creating tasks/sequences.
“Zapier let us stand up a Lusha-powered scoring flow in a day. The confidence gate alone cut bounces by more than half, and SDRs finally trust what shows up in their queue.”
