Best Zapier automations for lead qualification

Recommendation (short):
Build a multi-step Zap that scores each Typeform submission inside Zapier (Formatter or Code), filters out low scores before any HubSpot call, then conditionally Find/Update/Create the contact in HubSpot. Use Zapier Storage and a conservative threshold + manual-review queue for borderline cases to minimize API calls and false positives.

Why this works:
- Filtering before HubSpot means HubSpot API is only called for truly qualified leads (big API savings).
- Storage and de-dup checks reduce repeated Find/Create calls for the same lead.
- A manual-review queue for borderline leads cuts false positives while keeping automation fast for clear prospects.

Decision criteria (pick approach by):
- Budget: If on Zapier Free/Starter, Paths/Storage/Code steps may be limited — upgrade if you need reliability and storage. For heavy volumes (>500 qualified/day) consider batch ingestion or a server-side pipeline.
- Skill level: Formatter + Filters are low-code. Use “Code by Zapier” or Webhooks if you need complex scoring or batch HubSpot API calls and you’re comfortable with JS/HTTP.
- Team & workflow stage: If sales needs a review step, route borderline leads to Slack/Sheets for quick human qualification.

Practical checklist (step-by-step):
1) Trigger: Typeform — New Entry.
2) Normalize data: Formatter by Zapier — clean email, phone, UTM, company size, job title.
3) Score: Use Formatter math or Code by Zapier to compute a numeric score (examples below). Include at least 2 signal types (intent answers + firmographics). Save score to output.
4) Filter: Only continue if score >= high_threshold (e.g., 70/100). If score is between low_threshold and high_threshold (e.g., 40–69), route to a manual-review Zap or Slack channel.
5) De-dup & Rate-limit: Use Storage by Zapier to store recent email hashes or Typeform IDs. If email exists in Storage and was processed within X days, stop the Zap.
6) HubSpot step (run only for filtered leads): Find Contact in HubSpot by email. If found, compare stored score (use properties or internal note) and Update only if new score is higher by N points. If not found, Create Contact and set lifecycle stage + score property.
7) Logging & notification: Log all qualified pushes to a Google Sheet or Slack channel. Keep an audit trail of score and why it passed.
8) Optional: Batch borderline leads daily for a human QC sweep (Delay/Schedule + Digest) to reduce false positives.

Scoring examples (simple, transparent):
- Answer-based intent: +50 for “ready to buy” answers, +20 for “interested”.
- Firmographics: +20 if company size >= target, +10 for matching industry.
- Negative rules: -50 if competitor checkbox is ticked, -30 if email domain is generic and no other signals.
Require 2 independent signals (intent + firmographic) to pass.

Best-for / Avoid-if
- Best for: small-to-medium teams who need accurate, low-API-cost qualification with simple to moderate scoring.
- Avoid if: you have very high volume (>500–1,000 qualified/day) or need complex ML scoring — then use batch HubSpot ingestion or a small ETL/service instead.

Notes: Use Zapier Storage and Filters to minimize HubSpot API calls. If you want help designing the exact scoring formula or conditional JSON for Code by Zapier, I can draft that next.

Compare Zapier and Make