This article provides a complete, practical walkthrough of the Telegram Hunter Send Webhook n8n agent. It connects HTTP Request, Webhook across approximately 1 node(s). Expect a Intermediate setup in 15-45 minutes. One‑time purchase: €29.

What This Agent Does

This agent orchestrates a reliable automation between HTTP Request, Webhook, handling triggers, data enrichment, and delivery with guardrails for errors and rate limits.

It streamlines multi‑step processes that would otherwise require manual exports, spreadsheet cleanup, and repeated API requests. By centralizing logic in n8n, it reduces context switching, lowers error rates, and ensures consistent results across teams.

Typical outcomes include faster lead handoffs, automated notifications, accurate data synchronization, and better visibility via execution logs and optional Slack/Email alerts.

How It Works

The workflow uses standard n8n building blocks like Webhook or Schedule triggers, HTTP Request for API calls, and control nodes (IF, Merge, Set) to validate inputs, branch on conditions, and format outputs. Retries and timeouts improve resilience, while credentials keep secrets safe.

Third‑Party Integrations

• HTTP Request
• Webhook

Import and Use in n8n

1. Open n8n and create a new workflow or collection.
2. Choose Import from File or Paste JSON.
3. Paste the JSON below, then click Import.
4. Show n8n JSON

   Title:  
   Automate Smart Lead Qualification with n8n, Hunter, MadKudu, and Telegram  
   
   Meta Description:  
   Discover how to automate lead collection and qualification using n8n with integrations like Hunter for email validation, MadKudu for lead scoring, and Telegram for hot lead notifications.  
   
   Keywords:  
   lead scoring automation, n8n workflow, email verification, Telegram bot alert, MadKudu integration, Hunter API, lead qualification, smart lead generation, business automation, no-code CRM optimization  
   
   Third-Party APIs Used:
   
   1. Hunter.io – for email verification  
   2. MadKudu – for customer fit scoring and lead enrichment  
   3. Telegram Bot API – for real-time lead notifications  
   
   —
   
   Article:
   
   Streamline Lead Qualification with This Smart n8n Workflow  
   
   In today’s online-driven business landscape, timely response and accurate lead qualification can make the difference between converting a high-value client or missing a major opportunity. Manual processes often lag behind real-time interactions, making automation essential. Fortunately, there's a smarter way to filter leads as they come in — with workflows like the one demonstrated using n8n.
   
   Let’s dive into a powerful use case for lead qualification involving real-time email verification, lead scoring, and instant team notifications — all orchestrated within the n8n workflow automation platform using best-in-class APIs.  
   
   🧩 The Workflow Breakdown  
   
   This n8n-based automation begins with a simple contact form, but it's what happens after submission that adds major value. Here's all that this one workflow accomplishes:
   
   1. Captures business emails via a web form  
   2. Validates the email for authenticity using Hunter  
   3. Scores the lead using MadKudu based on customer fit metrics  
   4. Notifies your team via Telegram if the lead is promising  
   
   Let’s go step-by-step.
   
   📨 Step 1: Email Collection with an n8n Web Form  
   
   The automation kicks off with an embedded n8n Webhook Form (also known as the Form Trigger). It asks a single, critical question: “What’s your business email?” This form can be easily replaced or integrated with other form services like Typeform, Google Forms, or SurveyMonkey.
   
   🧪 Step 2: Verify Email Validity with Hunter.io  
   
   Incoming email addresses get verified immediately through Hunter’s Email Verifier API. This step checks if the address is real, deliverable, and professional. If the result is not "valid", the workflow stops gracefully — saving time and server calls downstream.
   
   Key insights from Hunter include:
   - MX record check
   - SMTP validations
   - Disposable email detection
   - Public domain check
   
   🔍 Step 3: Qualify with MadKudu’s Lead Scoring  
   
   If the email checks out, it goes next to MadKudu. This SaaS scoring platform evaluates the lead using company data and behavior-based signals like:
   - Industry and location
   - Company size
   - Funding history
   - Tech stack
   - Website traffic  
   
   In this example, the lead's customer fit score was an impressive 81 (out of 100), which MadKudu categorized as “good.” That score, generated via their enriched data model, is the cornerstone to deciding whether the lead is “hot” or not.
   
   ⚖️ Step 4: Route Based on Score Threshold  
   
   The workflow uses an n8n "IF" node to make a decision: if the customer fit score is greater than 60, a notification is triggered. Otherwise, it tags the lead as "Not interesting enough" – a polite no-op that avoids unnecessary team alerts.
   
   📬 Step 5: Get Instant Alerts via Telegram  
   
   When a lead qualifies as "hot," a custom message is sent to your Telegram chat, including:
   - The lead’s email
   - A formatted list of top scoring signals from MadKudu  
   
   For instance:
   
   > ⭐ New hot lead: jan@n8n.io  
   > ✔ Company raised $ is 13,500,000  
   > ✔ Company is located in is Germany  
   > ✔ Website traffic is medium large  
   > …and more  
   
   This instant alert lets sales reps jump on leads while they’re still warm — and with context that supports personalized outreach.  
   
   —
   
   💡 Why This Workflow is Powerful  
   
   This no-code automation hits the sweet spot in modern lead funnels — acting fast, scoring smartly, and cutting through the noise. In one flow:
   - You ensure data quality (Hunter)  
   - Get contextual insights (MadKudu)  
   - Act only on high-potential prospects (Telegram alert)  
   
   Additionally, this entire setup is modular. Want to swap in Slack for Telegram? Easy. Prefer different form tools or scoring services? Just replace the relevant nodes.
   
   🔧 Getting Started  
   
   To make this workflow your own:
   1. Plug in your MadKudu, Hunter, and Telegram API credentials  
   2. Set your Telegram chat ID  
   3. Run a test with your email to inspect the behavior  
   4. Deploy the production webhook URL for scalable lead intake  
   
   —
   
   Conclusion  
   
   With platforms like n8n and rich APIs like Hunter and MadKudu, building an intelligent lead pipeline has never been easier. This particular flow is a blueprint for how you can leverage automation to enhance your customer acquisition strategy — validating, qualifying, and alerting all within seconds. 
   
   Whether you're a startup founder, growth marketer, or sales operator, integrating smart logic into your lead generation can drive more focused conversations and faster conversions. Let automation handle the heavy lifting — your sales team will thank you.
   
   —
   
   Keywords:  
   lead scoring automation, n8n workflow, business automation, email validation, Hunter API, MadKudu API, Telegram bot integration, contact form automation, smart CRM, sales pipeline automation

5. Set credentials for each API node (keys, OAuth) in Credentials.
6. Run a test via Execute Workflow. Inspect Run Data, then adjust parameters.
7. Enable the workflow to run on schedule, webhook, or triggers as configured.

Tips: keep secrets in credentials, add retries and timeouts on HTTP nodes, implement error notifications, and paginate large API fetches.

Validation: use IF/Code nodes to sanitize inputs and guard against empty payloads.

Why Automate This with AI Agents

AI‑assisted automations offload repetitive, error‑prone tasks to a predictable workflow. Instead of manual copy‑paste and ad‑hoc scripts, your team gets a governed pipeline with versioned state, auditability, and observable runs.

n8n’s node graph makes data flow transparent while AI‑powered enrichment (classification, extraction, summarization) boosts throughput and consistency. Teams reclaim time, reduce operational costs, and standardize best practices without sacrificing flexibility.

Compared to one‑off integrations, an AI agent is easier to extend: swap APIs, add filters, or bolt on notifications without rewriting everything. You get reliability, control, and a faster path from idea to production.

Best Practices

• Credentials: restrict scopes and rotate tokens regularly.
• Resilience: configure retries, timeouts, and backoff for API nodes.
• Data Quality: validate inputs; normalize fields early to reduce downstream branching.
• Performance: batch records and paginate for large datasets.
• Observability: add failure alerts (Email/Slack) and persistent logs for auditing.
• Security: avoid sensitive data in logs; use environment variables and n8n credentials.

FAQs

Can I swap integrations later? Yes. Replace or add nodes and re‑map fields without rebuilding the whole flow.

How do I monitor failures? Use Execution logs and add notifications on the Error Trigger path.

Does it scale? Use queues, batching, and sub‑workflows to split responsibilities and control load.

Is my data safe? Keep secrets in Credentials, restrict token scopes, and review access logs.