Hunter + Slack: only qualified leads hit your team

Q: Can I customize this lead scoring automation workflow for a different “qualified” definition?

Yes, and you should. The main change is in the Evaluate Fit Score “If” check, where you raise or lower the score threshold. You can also tweak which form fields are sent into MadKudu in the request step (so your scoring uses the signals you actually collect). Common customizations include setting a higher bar for employee count, routing different segments to different Slack channels, and adding a “review later” path instead of doing nothing.

Your Slack shouldn’t feel like a slot machine. One minute it’s a legit demo request, the next it’s “hi sir” from a made-up address, and your team still has to check. That constant noise kills follow-up speed, and honestly, it makes people stop trusting notifications.

Marketing managers get blamed for “bad leads.” Sales reps get interrupted all day. Founders see it too, because every false positive becomes a tiny tax on momentum. This lead scoring automation filters the junk, validates emails, scores fit, then pings Slack only when someone is worth a fast reply.

Below you’ll see how the workflow runs in n8n, what it changes day-to-day, and the practical knobs you can turn to make “qualified” match your business.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Hunter + Slack: only qualified leads hit your team

Click to explore

flowchart LR

    subgraph sg0["n8n Form Flow"]
        direction LR
        n0["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/slack.svg' width='40' height='40' /></div><br/>Slack"]
        n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/form.svg' width='40' height='40' /></div><br/>n8n Form Trigger"]
        n2@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Check if the email is valid", pos: "b", h: 48 }
        n3@{ icon: "mdi:cog", form: "rounded", label: "Email is not valid, do nothing", pos: "b", h: 48 }
        n4["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Score lead with MadKudu"]
        n5["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/hunter.png' width='40' height='40' /></div><br/>Verify email with Hunter"]
        n6@{ icon: "mdi:cog", form: "rounded", label: "Not interesting enough", pos: "b", h: 48 }
        n7@{ icon: "mdi:swap-horizontal", form: "rounded", label: "if customer fit score  60", pos: "b", h: 48 }
        n1 --> n5
        n4 --> n7
        n5 --> n2
        n7 --> n0
        n7 --> n6
        n2 --> n4
        n2 --> n3
    end

    %% Styling
    classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
    classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
    classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
    classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
    classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
    classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
    classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
    classDef disabled stroke-dasharray: 5 5,opacity: 0.5
    class n1 trigger
    class n2,n7 decision
    class n4 api
    classDef customIcon fill:none,stroke:none
    class n0,n1,n4,n5 customIcon

The Problem: Slack Alerts Don’t Mean “Qualified”

Most teams start with the simplest setup: a form comes in, Slack gets a message, someone checks it. It works until it doesn’t. Once you’re getting a steady stream of inquiries, the bad ones blend in with the good ones. People open Slack, skim, maybe click through, then decide it’s not worth it. Do that 15 times a day and you’ve burned a chunk of focus, plus you’ve trained the team to respond slower to the leads that actually matter.

The friction compounds. Here’s where it breaks down.

Invalid or risky emails sneak in, so you waste time chasing prospects who never could have replied.
Good leads and low-fit leads look identical in Slack, which means your fastest follow-up goes to whoever submitted last.
Manual “quick checks” turn into a daily habit, and it quietly eats about an hour of attention across the team.
When the channel gets noisy, reps mute it, and the whole point of instant routing disappears.

The Solution: Validate with Hunter, Score with MadKudu, Then Alert Slack

This workflow starts the moment a new lead hits your form. First, it checks the email with Hunter so you can separate real, deliverable addresses from the obvious garbage. If the email fails validation, the workflow quietly stops. No Slack ping. If the email looks good, it sends the lead details to MadKudu to assess fit (things like company size, intent signals, and whatever your scoring model is set up to consider). Finally, n8n evaluates the fit score against your threshold and posts to your chosen Slack channel only when the lead is high enough quality to justify an interruption.

The workflow begins with form intake, then runs two “gates.” Gate one is Hunter email verification. Gate two is MadKudu scoring, which decides if Slack hears about it or not.

What You Get: Automation vs. Results

What This Workflow Automates

Results You’ll Get

A form submission triggers the workflow automatically in n8n.
Hunter verifies the lead’s email status before anything else happens.
MadKudu scores the lead so you can filter by fit, not gut feel.
Slack only receives a message when the fit score clears your threshold.

Cut “check-and-triage” down from about 1 hour a day to a few minutes.
Fewer false alarms in Slack, so reps actually trust the channel again.
Faster follow-up on high-intent prospects because they stand out immediately.
Cleaner handoffs between marketing and sales, with fewer arguments about quality.
A consistent qualification bar that you can raise or lower as volume changes.

Example: What This Looks Like

Say your form brings in 25 leads a day. A rep spending “just 2 minutes” per lead to sanity-check email, look up the company, and guess intent is suddenly at about 50 minutes daily, and that’s before any real outreach. With this workflow, submitting the form takes the same time, but qualification runs in the background. You skim maybe 5 Slack alerts for the best leads, which is closer to 10 minutes total. That’s roughly 40 minutes back every day, and the interruptions drop hard.

What You’ll Need

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
Hunter for email verification and status checks.
MadKudu to score lead fit and intent.
Slack to notify the right channel instantly.

Skill level: Beginner. You’ll connect credentials, pick a Slack channel, and adjust one scoring threshold.

Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).

How It Works

Form intake kicks it off. A new submission hits the n8n form trigger, capturing the fields you care about (usually name, email, company, maybe employee count).

Email verification happens first. Hunter checks if the email looks valid and deliverable. If it doesn’t pass, the workflow routes to an “ignore” path and stops quietly.

MadKudu scores the lead. n8n sends lead data via HTTP request to MadKudu, then receives a fit score (and often extra attributes you can use later, like segment or intent notes).

Only the best leads reach Slack. An “If” check compares the score to your threshold. High-fit leads post to your chosen Slack channel, while low-fit leads go down a “do nothing” path.

You can easily modify the score threshold to match your pipeline capacity based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Form Trigger

Start by setting up the form that collects lead email addresses and triggers the workflow.

Add the Form Intake Trigger node as your workflow trigger.
Set Path to 0bf8840f-1cc4-46a9-86af-a3fa8da80608.
Set Form Title to Contact us and Form Description to We'll get back to you soon.
Add a form field labeled What's your business email? to collect the lead email.

Step 2: Connect Email Verification and Lead Enrichment

Verify the submitted email and enrich the lead data before scoring.

Add Confirm Email with Hunter after Form Intake Trigger.
Set Operation to emailVerifier and Email to ={{ $json['What\'s your business email?'] }}.
Credential Required: Connect your hunterApi credentials in Confirm Email with Hunter.
Add Validate Email Status and set the condition Left Value to ={{ $json.status }} and Right Value to valid.
Connect the true output of Validate Email Status to Assess Lead via MadKudu and the false output to Ignore Invalid Email.
In Assess Lead via MadKudu, set URL to =https://api.madkudu.com/v1/persons?email={{ $json.email }}.
Credential Required: Connect your httpHeaderAuth credentials in Assess Lead via MadKudu.

⚠️ Common Pitfall: The MadKudu request uses {{ $json.email }}. Ensure the Hunter verification output includes email or map it before calling Assess Lead via MadKudu.

Step 3: Set Up Lead Scoring Logic

Filter out low-fit leads and route only high-fit leads to Slack.

Add Evaluate Fit Score after Assess Lead via MadKudu.
Configure the condition with Left Value ={{ $json.properties.customer_fit.score }}, Operator gt, and Right Value 60.
Connect the true output of Evaluate Fit Score to Post to Slack Channel and the false output to Low Interest Path.

Note: Evaluate Fit Score outputs to both Post to Slack Channel and Low Interest Path in parallel based on the condition result.

Step 4: Configure Slack Notifications

Send a formatted hot-lead notification to your Slack channel.

Add Post to Slack Channel and connect it to the true output of Evaluate Fit Score.
Set Select to channel and Channel to #interesting_leads.
Set Text to =⭐ Got a hot lead for you {{ $json.properties.first_name }} {{ $json.properties.last_name }} from {{ $json.company.properties.name }} ({{ $json.company.properties.domain }}) based out of {{ $json.company.properties.location.state }}, {{ $json.company.properties.location.country }}. {{ $('Assess Lead via MadKudu').item.json.properties.customer_fit.top_signals_formatted }}.
Credential Required: Connect your slackApi credentials in Post to Slack Channel.

Step 5: Test and Activate Your Workflow

Validate the full flow from form submission to Slack notification and activate for production use.

Use the Form Intake Trigger test URL to submit a sample email that should be valid.
Confirm that Confirm Email with Hunter returns valid and that Assess Lead via MadKudu returns a customer_fit.score.
Verify that high-fit leads (score > 60) reach Post to Slack Channel and appear in #interesting_leads.
Submit a low-fit or invalid email to ensure the flow routes to Low Interest Path or Ignore Invalid Email as expected.
Click Activate to enable the workflow for live form submissions.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

Hunter credentials can expire or your plan may block certain endpoints. If things break, check your Hunter dashboard API usage and key status first.
If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
MadKudu scoring models differ by account, so a “good” score in one workspace may be “meh” in another. Calibrate your threshold using a week of real leads before you trust the Slack routing.

Frequently Asked Questions

How long does it take to set up this lead scoring automation?

About 30 minutes if your Hunter, MadKudu, and Slack accounts are ready.

Do I need coding skills to automate lead scoring?

No. You’ll connect accounts and adjust a couple of settings in n8n. The logic is already built into the workflow.

Is n8n free to use for this lead scoring automation workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Hunter and MadKudu usage costs based on your lead volume.

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

Can I customize this lead scoring automation workflow for a different “qualified” definition?

Yes, and you should. The main change is in the Evaluate Fit Score “If” check, where you raise or lower the score threshold. You can also tweak which form fields are sent into MadKudu in the request step (so your scoring uses the signals you actually collect). Common customizations include setting a higher bar for employee count, routing different segments to different Slack channels, and adding a “review later” path instead of doing nothing.

Why is my Hunter connection failing in this workflow?

Usually it’s an expired or rotated API key, so regenerating the key in Hunter and updating the credential in n8n fixes it. It can also be a plan/permission issue if the endpoint you’re calling isn’t available on your tier. If it fails only when volume spikes, you may be hitting rate limits, which means you’ll want to slow down requests or add a small queue.

How many leads can this lead scoring automation handle?

Most small teams run hundreds of leads a week without issues, and if you self-host n8n the main constraint becomes your server plus Hunter/MadKudu API limits.

Is this lead scoring automation better than using Zapier or Make?

Sometimes. If your routing is simple and you never plan to change it, Zapier or Make can be quicker to click together. But this exact setup usually grows legs: you’ll want branching rules, “do nothing” paths, and more control over what gets posted to Slack. n8n handles that without making every extra condition feel like a paid upgrade, and self-hosting can be a big deal once volume increases. If you’re torn, Talk to an automation expert and describe your lead flow in plain language.

The best part is the calm. Slack becomes a signal again, and your team responds faster because the workflow already did the skeptical work upfront.

Hunter + Slack: only qualified leads hit your team

How This Automation Works

n8n Workflow Template: Hunter + Slack: only qualified leads hit your team

The Problem: Slack Alerts Don’t Mean “Qualified”