How to Set Up an n8n Lead Qualification Workflow with HubSpot and Hunter

An n8n lead qualification workflow is useful when a form submission alone is not enough to decide whether someone should enter outreach. Instead of sending every new lead into the same sequence, you can verify the email, score the lead, and only record or contact the leads that meet your threshold.

The source workflow behind this guide uses a form trigger, Hunter for email verification, a scoring step through MadKudu, Gmail for outreach, and HubSpot for recording engagement. That makes it a strong pattern for inbound lead handling, but it also means you need more setup discipline than a simple form-to-CRM sync.

What you will build

You will build an n8n workflow that starts when a user submits a form. The workflow first checks whether the email is valid, then enriches or scores the lead, then compares that score against a threshold. If the lead passes, n8n sends an outreach email and records the activity in HubSpot. If not, the workflow exits cleanly without cluttering your follow-up process.

When this workflow makes sense

Use this pattern when your inbound volume is high enough that manual review is slowing down response time, but low-quality submissions are still common enough that fully automatic outreach would create noise. It works well for demo requests, waitlists, service inquiries, or gated content forms that attract a mix of high-fit and low-fit leads.

It is not a good first workflow if you do not yet trust your scoring criteria. In that case, start by recording the score without using it for routing, review the results for a week or two, and only then automate outreach.

What you need before you start

• An n8n form or another form source connected to n8n.
• HubSpot credentials and a clear contact model.
• Hunter credentials for email verification.
• A lead scoring service or internal scoring endpoint. The source workflow uses MadKudu.
• A Gmail account for the outreach step.
• A score threshold you can justify, rather than a number chosen at random.

Step-by-step setup process

1. Add the form trigger. If you are replacing the n8n form with Typeform or another source, keep the output field names consistent from the start.
2. Add an If node to confirm the submission contains a usable email address before making external requests.
3. Send the email to Hunter for verification. Decide whether you want to block invalid, risky, or disposable emails, or only fully invalid ones.
4. Send the lead data to your scoring step. In the source pattern, this is an HTTP request to MadKudu. The important part is that the response returns a field you can compare reliably.
5. Add an If node that checks whether the fit score exceeds your chosen threshold.
6. On the qualified branch, use Gmail to send the first outreach email. Keep the message short and specific. The workflow should not impersonate a high-touch sales sequence if the lead is still very early.
7. Record the outreach or contact state in HubSpot so your CRM remains the system of record.
8. On the unqualified branch, do nothing or write a note for later review. A silent branch is better than accidental outreach.

How to validate the setup

Test with at least three lead samples: one clearly good lead, one clearly weak lead, and one lead with an invalid or disposable email. Verify that the workflow stops in the right place for each case. Then inspect HubSpot to confirm the qualified path writes the expected activity or properties. Do not rely only on node success messages. Qualification workflows fail most often in the business logic, not in the API call itself.

Common problems and fixes

• False positives from scoring: A threshold that looks reasonable on paper may still approve weak leads. Review actual outcomes, not only scores.
• Email verification mismatch: Hunter may classify some addresses as risky rather than invalid. Decide how your workflow should treat that middle state.
• HubSpot duplicates: If your workflow both creates and updates contacts, you need a clear rule for which step runs first.
• Outreach sends before CRM update: Put HubSpot logging before or immediately after Gmail, depending on how your team audits outreach.
• Overfitting the threshold: Do not create too many branch rules too early. A single threshold is easier to evaluate and adjust.

Template versus custom build

A prebuilt template is helpful here because the sequence is more important than the exact content. Verification, scoring, qualification, outreach, and CRM logging are the main blocks, and a template saves time by putting those blocks in the right order. You still need to connect your own accounts, rewrite the email copy, and calibrate the score threshold.

If your qualification logic depends on several internal systems, owner assignment rules, or account-based routing, you will probably move beyond a generic template quickly. For most mid-funnel inbound handling, though, the template gives you a useful head start.

FAQ

Can I replace Hunter with another verification tool?

Yes. The workflow pattern stays the same as long as the replacement returns a clear validity result that you can test in an If node.

Do I need a third-party scoring tool?

No. You can score leads inside n8n with your own rules, but an external score can be useful if your team already trusts it.

Should every qualified lead get an email immediately?

Not always. Some teams prefer to update HubSpot first and trigger outreach from the CRM side. The best choice depends on where your team audits communication.

Final implementation notes

The main benefit of this workflow is not just speed. It is decision quality. A basic form-to-CRM automation moves every lead forward equally. A qualification workflow adds judgment before outreach. If your threshold is grounded and your validation steps are clear, n8n can turn noisy inbound traffic into a cleaner queue for sales or lifecycle marketing.