This article provides a complete, practical walkthrough of the Webhook Code 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:**  
   Real-Time Lead Routing with n8n: Qualify Webflow Leads Using Datagma & Email Intelligence
   
   **Meta Description:**  
   Learn how to build a real-time lead qualification and routing system using n8n, Webflow, and Datagma. Automatically detect professional email domains, enrich lead data, and route prospects to personalized demo experiences.
   
   **Keywords:**  
   n8n workflow, lead routing automation, Webflow form integration, Datagma API, lead enrichment, email domain verification, real-time lead scoring, Calendly lead routing, professional email detection, B2B lead qualification
   
   ---
   
   # Real-Time Lead Routing with n8n: A Smart Workflow for Converting Webflow Leads
   
   In today’s fast-paced sales environment, manually reviewing form submissions isn’t scalable. That’s why smart automation is essential — it allows teams to instantly qualify and route leads based on quality and intent.
   
   This article introduces a fully automated n8n workflow that connects Webflow, Datagma, and custom logic to identify the best leads in real-time. Once a visitor submits your Webflow form, this workflow:
   
   1. Extracts the email domain
   2. Checks whether it’s a free email provider
   3. Enriches the company information using Datagma
   4. Qualifies the lead based on company size
   5. Routes the lead to the appropriate Calendly link (personal demo or group demo)
   
   Let’s dive into how the workflow is structured and why it’s a powerful tool for your lead nurturing strategy.
   
   ---
   
   ## How the Workflow Works
   
   ### Step 1: Capture Form Submissions from Webflow
   
   The process begins with the `Receive form submission from Webflow` node, a webhook that accepts data from a Webflow form trigger. The key data point here is the email address submitted by the user.
   
   ### Step 2: Parse the Email Domain
   
   The first automated step is to extract the domain part of the email address — everything after the “@” symbol. This is handled by the `Get domain from email` node using a simple JavaScript expression:
   ```js
   {{$json.body.email.split("@")[1]}}
   ```
   
   ### Step 3: Identify Free Email Providers
   
   The `Verify professional email` node compares the extracted domain against a large list of known free email providers (e.g., gmail.com, yahoo.com). If the domain is on the list, it's labeled as a non-professional or "free" email. This is crucial in identifying B2B leads, as free email users are typically less valuable in a sales pipeline.
   
   This node returns a flag:  
   - `true` = Free email provider  
   - `false` = Professional or custom domain
   
   ### Step 4: Enrich Company Information with Datagma
   
   If the email domain is professional, the workflow proceeds to the `Enrich with Datagma` node, which sends a request to the Datagma API for company intelligence. By passing the domain as a parameter, the API returns data such as:
   
   - Number of employees
   - Company industry
   - Year founded
   - LinkedIn URL
   - Revenue estimates
   - Funding amount
   - Full company description
   
   The required API key (your `apiId`) can be obtained on the [Datagma dashboard](https://app.datagma.com/user-api). Be sure to replace `YOUR_API_KEY` in the workflow with your actual key.
   
   ### Step 5: Simplify the Data
   
   Datagma's enriched data is often nested and complex. The `Simplify Datagma Output` node pulls only the important fields like `company_size`, `industry`, and `company_revenue`, making it easier to apply logic in the next step.
   
   ### Step 6: Qualify the Lead
   
   Next, we determine if the lead is ideal for a private demo or should be routed to a group event. In the `Qualify Account` node, we evaluate whether the company size exceeds 100 employees:
   ```js
   if (company_size > 100) {
     $input.item.json.result = 1 // Private 1:1 demo
   } else {
     $input.item.json.result = 2 // Group demo
   }
   ```
   
   Users are routed accordingly:
   - `1` for personalized 1:1 demos
   - `2` for group demos or educational webinars
   
   ### Step 7: Return Result to Webflow
   
   Finally, the workflow sends a response back to Webflow via the `Send result to Webflow` node. The response includes the `result` value, which Webflow can use to dynamically display the right Calendly link or redirect the user accordingly.
   
   ---
   
   ## Benefits of This Workflow
   
   - ✅ **Instant Qualification:** No need to manually check leads — get real-time signal intelligence.
   - 🔎 **B2B Filtering:** Avoid free email spam or non-qualified users.
   - 📈 **Better Routing:** Tailor the experience based on lead data.
   - 📬 **Enrichment at Scale:** Use Datagma to pull company data without having to ask users.
   - 🛠 **Fully Customizable:** Replace the 100-employee rule with your own qualification logic.
   
   ---
   
   ## Integration Summary
   
   ### Third-party APIs Used:
   1. **Datagma API**
      - Used to enrich company data by querying domain-related information, such as number of employees, revenue, industry, etc.
   
   2. **Webflow (via Webhook)**
      - Captures form submission data via a POST request from a Webflow form.
   
   ---
   
   ## Final Thoughts
   
   This n8n workflow is a perfect example of how automation can generate better lead insights and improve user experience, all in real-time. With minimal setup, you can enhance your Webflow forms to become smart lead filters — optimized for conversion, qualification, and personalization.
   
   Whether you're sending enterprise-level leads to a strategic sales call or guiding early-stage followers to group demos, this system ensures no opportunity slips through the cracks.
   
   Ready to implement? Head over to the full setup here:  
   👉 [Real-time Lead Routing Guide](https://lempire.notion.site/Real-time-lead-routing-9fc55c9a5a17415ba736cbdbf5d43a30?pvs=4)
   
   Happy automating!

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.