Hunter + Telegram: only qualified leads get through
Your contact form should feel like opportunity. Instead, it often feels like spam triage, with fake emails, students “just researching,” and bots filling your inbox at 2 a.m.
Hunter Telegram leads automation hits hardest when you’re the marketing manager owning inbound quality, but founders and client-facing sales reps get stuck in the same loop. You want the real leads surfaced fast, so you can reply while they’re still warm.
This workflow verifies every email with Hunter, scores each lead with MadKudu, then alerts you in Telegram only when the lead clears your bar. You’ll see how it works, what you need, and where teams usually trip up.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Hunter + Telegram: only qualified leads get through
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/form.svg' width='40' height='40' /></div><br/>n8n Form Trigger"]
n1@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Check if the email is valid", pos: "b", h: 48 }
n2@{ icon: "mdi:cog", form: "rounded", label: "Email is not valid, do nothing", pos: "b", h: 48 }
n3["<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"]
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/hunter.png' width='40' height='40' /></div><br/>Verify email with Hunter"]
n5@{ icon: "mdi:cog", form: "rounded", label: "Not interesting enough", pos: "b", h: 48 }
n6@{ icon: "mdi:swap-horizontal", form: "rounded", label: "if customer fit score 60", pos: "b", h: 48 }
n7["<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/telegram.svg' width='40' height='40' /></div><br/>Telegram"]
n0 --> n4
n3 --> n6
n4 --> n1
n6 --> n7
n6 --> n5
n1 --> n3
n1 --> n2
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 n0 trigger
class n1,n6 decision
class n3 api
classDef customIcon fill:none,stroke:none
class n0,n3,n4,n7 customIcon
The Problem: Your Form Leads Aren’t “Leads” Yet
Inbound forms create a sneaky kind of busywork. You’re not just reading messages, you’re validating identity, checking if the company is real, guessing intent, and deciding if the lead deserves a fast response. Do that 20 times a day and it becomes a background tax on the whole team. Worse, manual checks are inconsistent. One person flags a lead as “junk,” another chases it, and now you’ve got awkward handoffs plus a messy pipeline.
It adds up fast. Here’s where it breaks down in real life.
- You end up reacting to whoever emailed last, not whoever is the best fit right now.
- Fake or mistyped emails sneak through, so follow-ups bounce and your team loses momentum.
- Lead quality is judged by gut feel, which means your “rules” change depending on the day.
- Notifications become noise, so people mute channels and miss the few great leads.
The Solution: Verify, Score, Then Alert (Only When It Matters)
This n8n workflow turns a messy form submission into a clean, qualified lead alert. It starts when someone submits your form through an n8n form trigger. Before anything else, Hunter checks the email, so you’re not scoring or notifying on bad data. If the email fails verification, the workflow stops quietly. If it passes, the lead gets sent to MadKudu for scoring, which is where your “is this worth it?” logic becomes consistent. From there, a customer-fit check decides what happens next: high-quality leads get a Telegram message, and low-interest leads get filtered out without interrupting anyone.
The workflow begins with form intake, then runs email verification through Hunter. Next, MadKudu scores the lead and n8n evaluates your fit rules (like employee count or similar traits). Finally, Telegram receives a clean alert only when the lead qualifies, so you can respond quickly without drowning in pings.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say your site gets 15 form submissions a day. Manually, it’s easy to spend about 5 minutes per lead checking the email, searching the company, and deciding if it’s worth a quick reply, which is roughly 75 minutes daily. With this workflow, you submit the form as usual and the automation does the verification and scoring in the background. You only get Telegram alerts for the handful that qualify, so your “review time” drops to maybe 10 minutes total. That’s about an hour back on a normal day.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Hunter for email verification and deliverability checks.
- MadKudu to score and qualify inbound leads.
- Telegram to receive instant qualified-lead notifications.
- MadKudu API key (get it from your MadKudu dashboard).
Skill level: Beginner. You’ll connect accounts, set a Telegram chat ID, and tweak a threshold in one or two places.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A new lead submits your form. The workflow triggers instantly from the n8n form intake, so you don’t need extra scripts or a separate form tool to begin testing.
Email quality gets checked first. Hunter verifies the submitted address, then n8n runs a quick pass/fail decision. If the email is invalid, the workflow stops (quietly) so you don’t waste time scoring junk.
Lead scoring and fit rules kick in. Verified leads go to MadKudu via HTTP request, and n8n evaluates the score against your requirements. This is where you set rules like “only alert me when the score is above X” or “only companies above a certain employee count.”
Qualified leads reach you in Telegram. When a lead clears the fit check, Telegram receives a message with the details you care about, so you can follow up fast. Low-interest leads are filtered out and don’t clutter your notifications.
You can easily modify the scoring 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
Set up the form that collects incoming lead emails and starts the workflow.
- Add and open Form Intake Trigger.
- Set Path to
0bf8840f-1cc4-46a9-86af-a3fa8da80608. - Set Form Title to
Contact usand Form Description toWe'll get back to you soon. - Add a form field with Field Label set to
What's your business email?.
What's your business email?.Step 2: Connect Email Verification and Validation
Verify the lead email with Hunter and route only valid emails forward.
- Open Hunter Email Verification and set Operation to
emailVerifier. - Set Email to
={{ $json['What\'s your business email?'] }}. - Open Validate Email Status and configure the condition: Left Value
={{ $json.status }}, Operationequals, Right Valuevalid. - Ensure the false branch routes to Invalid Email Halt to stop invalid emails.
Step 3: Set Up Lead Scoring and Fit Logic
Send valid emails to MadKudu and evaluate customer fit for alerting.
- Open MadKudu Lead Scoring and set URL to
=https://api.madkudu.com/v1/persons?email={{ $json.email }}. - Set Authentication to
genericCredentialTypeand Generic Auth Type tohttpHeaderAuth. - Open Customer Fit Check and set the condition to: Left Value
={{ $json.properties.customer_fit.score }}, Operationgt, Right Value60. - Ensure the false branch routes to Low Interest Stop to halt low-score leads.
Step 4: Configure the Alert Output
Send high-fit lead alerts to Telegram with the scoring highlights.
- Open Telegram Lead Alert and set Chat ID to your Telegram ID (replace
[YOUR_ID]). - Set Text to
=⭐ New hot lead: {{ $json.email }}... {{ $json.properties.customer_fit.top_signals_formatted }}. - Credential Required: Connect your telegramApi credentials.
top_signals_formatted field in the message to give immediate context on why the lead is high quality.Step 5: Test and Activate Your Workflow
Validate the full lead qualification path from intake to Telegram alert.
- Manually execute Form Intake Trigger and submit a test email via the form.
- Confirm that Hunter Email Verification returns
status: validand that Validate Email Status routes to MadKudu Lead Scoring. - Verify that Customer Fit Check routes high scores to Telegram Lead Alert and low scores to Low Interest Stop.
- Check Telegram for the alert message including the email and top signals.
- Once successful, activate the workflow using the Active toggle.
Common Gotchas
- Hunter credentials can expire or lack the right plan permissions. If verification suddenly returns errors, check your Hunter API status and key permissions first.
- If you’re using Wait behavior (or MadKudu responds slowly at busy times), processing times vary. Bump up any wait duration or retry settings if downstream checks fail because the score hasn’t arrived yet.
- Telegram “chat not found” issues are usually a wrong chat ID or the bot not being added to the chat. Confirm the chat ID and send a test message from the bot before you blame n8n.
Frequently Asked Questions
About 30 minutes if you already have the accounts.
No. You’ll connect Hunter, MadKudu, and Telegram, then adjust a couple of rules. Most of the work is copying keys and testing with a sample submission.
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 MadKudu and Hunter costs based on your usage.
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.
Yes, and it’s the most common tweak. You’ll change the condition in the customer-fit check (the If logic) to raise or lower the bar, then adjust the Telegram message fields to match what your team wants to see. Some teams also add a second rule that routes “maybe” leads to a Google Sheet for later review.
Usually it’s an expired API key or the wrong Hunter workspace being used in n8n. Regenerate the key in Hunter, update the credential in n8n, then run one test submission end-to-end. If it still fails, check if your Hunter plan or limits are blocking verification for certain domains.
A lot, as long as your plan limits support it.
Often, yes, if your qualification logic is more than a simple filter. n8n makes it easier to stop early on invalid emails, branch cleanly for “qualified” vs “low interest,” and keep everything in one readable workflow. It’s also nice that you can self-host for high volume without paying per tiny step. Zapier and Make can be quicker for a two-action setup, but they get expensive and awkward when you add scoring, multiple checks, and “do nothing” paths. If you’re torn, Talk to an automation expert and we’ll map it to your exact volume and tools.
Once this is live, your form stops being a distraction and starts acting like a filter. The workflow handles the repetitive checks, and you only jump in when the lead is actually worth your time.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
