How Inbound Lead Qualifier Scores Submissions in Seconds

Your team runs this workflow every week: pull records from Pipedrive, cross-reference with a second source, apply judgment, format the output, and route it to 3 different stakeholders. Last Tuesday it took 30–60 minutes per cycle. This Tuesday the person who usually runs it is out sick, and nobody else knows the exact steps. The output varies by who runs it and when.

The core issue is data fragmentation. The information exists, but assembling it into actionable intelligence requires manual effort that does not scale with headcount. Inbound Lead Qualifier closes that gap by automating the lead qualification workflow from data extraction through structured output delivery.

Three Agents. One Webhook. Qualified Leads in Pipedrive.

The Inbound Lead Qualifier pipeline runs 3 agents in sequence. The Researcher pulls data from Pipedrive, and The Router delivers the output. Here is what happens at each stage and why it matters.

• The Researcher (Tier 1 Reasoning): Receives validated form data and conducts web-based company research — firmographic, technographic, and news intelligence.
• The Qualifier (Tier 1 Reasoning): Scores each submission on a 0–10 ILQ scale using 4 weighted criteria: Company-ICP Fit (35%), Role Authority (25%), Intent Signal Strength (25%), and Data Completeness (15%).
• The Router (Conditional): IF node evaluates ILQ score against a configurable threshold (default: ILQ ≥ 6).

When the pipeline completes, you get structured output that is ready to act on. The blueprint bundle includes everything needed to deploy, configure, and customize the workflow:

• 27-node n8n workflow (.json) — you own it
• 3 tested agent system prompts (ITP-validated)
• 7 SDC inter-agent schemas
• Error handling matrix (28 failure modes documented)
• Pipedrive custom field setup guide (fw_ prefix)
• Dependency matrix with ITP-measured costs
• README setup guide (15 minutes)

All scoring criteria, output formats, and routing rules are configurable in the system prompts — no workflow JSON edits required. This means Inbound Lead Qualifier adapts to your specific process, terminology, and integration requirements without forking the entire workflow.

Understanding how the pipeline works helps you customize it for your environment and troubleshoot issues when they arise. Here is a step-by-step walkthrough of the Inbound Lead Qualifier execution flow.

Step 1: The Researcher

Tier: Tier 1 Reasoning

The pipeline starts here. Receives validated form data and conducts web-based company research — firmographic, technographic, and news intelligence. Outputs a structured research payload with confidence scores. Companies with minimal web presence receive lower confidence but are not rejected.

This stage ensures all downstream agents receive clean, validated input. If this step returns incomplete data, every downstream agent works with a degraded picture.

Step 2: The Qualifier

Tier: Tier 1 Reasoning

Scores each submission on a 0–10 ILQ scale using 4 weighted criteria: Company-ICP Fit (35%), Role Authority (25%), Intent Signal Strength (25%), and Data Completeness (15%). Chain-of-thought reasoning produces transparent, auditable qualification decisions.

Why this step matters: This is where the pipeline applies judgment — not just data retrieval, but analysis.

Step 3: The Router

Tier: Conditional

This is the final deliverable — what lands in your inbox or dashboard. IF node evaluates ILQ score against a configurable threshold (default: ILQ ≥ 6). Qualified leads route to Pipedrive — person record + deal with ILQ score, qualification brief, and research summary in custom fields. Disqualified leads return a structured webhook response.

The entire pipeline executes without manual intervention. From trigger to output, every decision point follows a documented path. Every execution produces a traceable audit trail.

All nodes have been validated during Independent Test Protocol (ITP) testing on n8n v2.7.5. The error handling matrix in the bundle documents the recovery path for each failure mode.

Models wrap JSON in markdown code fences even when told not to. The prompt says "respond with raw JSON only" and the model responds with ```json\n{...}\n```. Every parser in every blueprint strips markdown fences before calling JSON.parse. It is not a bug — it is a known model behavior you must design around.

— ForgeWorkflows Engineering

All values below are from ITP testing — not estimates, not projections. Measured across 20 test submissions spanning strong ICP matches, borderline cases, disqualified leads, and edge cases.

The primary operating cost for Inbound Lead Qualifier is the per-execution LLM inference cost. Based on Independent Test Protocol (ITP) testing, the measured cost is: Cost per Qualified Lead (ITP-Measured): $0.234/qualified lead (ITP-measured avg). This figure includes all API calls across all agents in the pipeline — not just the primary reasoning step, but every classification, scoring, and output generation call.

To put this in context, consider the manual alternative. A skilled team member performing the same work manually costs $50–75/hour for an operations analyst at a fully loaded rate (salary, benefits, tools, overhead). If the manual version of this workflow takes 30–60 minutes per cycle, the per-execution cost in human labor is significant. The blueprint executes the same pipeline for a fraction of that cost, with consistent quality and zero fatigue degradation.

Infrastructure costs are separate from per-execution LLM costs. You will need an n8n instance (self-hosted or cloud) and active accounts for the integrated services. The estimated monthly infrastructure cost is $10–50/month depending on lead volume, depending on your usage volume and plan tiers.

Quality assurance: Blueprint Quality Standard (BQS) audit result is 12/12 PASS. ITP result is 16/16 PASS (100%). These are not marketing claims — they are test results from structured inspection protocols that you can review in the product documentation.

All cost and performance figures are ITP-measured — tested against real data fixtures on n8n v2.7.5 in March 2026. See the product page for full test methodology.

9 files. Workflow, 3 system prompts, error handling, and complete documentation.

When you purchase Inbound Lead Qualifier, you receive a complete deployment bundle. This is not a SaaS subscription or a hosted service — it is a set of files that you own and run on your own infrastructure. Here is what is included:

• CHANGELOG.md — Version history
• LICENSE.md — License terms
• README.md — Setup and configuration guide
• dependency_matrix.md — Third-party service dependencies
• error_handling_matrix.md — Error handling reference
• inbound_lead_qualifier_v1.0.0.json — n8n workflow (main pipeline)
• prompts/qualifier.txt — Qualifier system prompt
• prompts/researcher.txt — Researcher system prompt
• prompts/router.txt — Router system prompt

Start with the README.md. It walks through the deployment process step by step, from importing the workflow JSON into n8n to configuring credentials and running your first test execution. The dependency matrix lists every required service, API key, and estimated cost so you know exactly what you need before you start.

Every file in the bundle is designed to be read, understood, and modified. There is no obfuscated code, no compiled binaries, and no phone-home telemetry. You get the source, you own the source, and you control the execution environment.

Inbound Lead Qualifier is built for Marketing teams that need to automate a specific workflow without building from scratch. If your team matches the following profile, this blueprint is designed for you:

• You operate in a marketing function and handle the workflow this blueprint automates on a recurring basis
• You have (or are willing to set up) an n8n instance — self-hosted or cloud
• You have active accounts for the required integrations: Pipedrive CRM
• You have API credentials available: Anthropic API, Pipedrive API
• You are comfortable importing a workflow JSON and configuring API keys (the README guides you, but basic technical comfort is expected)

This is NOT for you if:

• Does not replace your form platform — works with Typeform and Tally via native webhooks
• Does not send follow-up emails or outreach — output is Pipedrive records + webhook response
• Does not support CRMs other than Pipedrive in v1 — Pipedrive-specific deal and person creation
• Does not handle GDPR consent management — out of scope for v1

Review the dependency matrix and prerequisites before purchasing. If you are unsure whether your environment meets the requirements, contact support@forgeworkflows.com before buying.

Every pipeline has boundaries. These are intentional design decisions, not oversights — understanding them helps you deploy with the right expectations and plan for edge cases in your environment.

Does not replace your form platform — works with Typeform and Tally via native webhooks

This is intentional. We default to human-in-the-loop for actions that carry reputational or financial risk. Once your team has validated output accuracy over 20+ cycles, you can adjust the pipeline to auto-execute — the workflow JSON supports it, but the default is conservative.

Does not send follow-up emails or outreach — output is Pipedrive records + webhook response

We scoped this boundary after ITP testing revealed inconsistent results when the pipeline attempted this. The agents handle what they handle well — extending beyond this scope requires custom prompt engineering specific to your data shape.

Does not support CRMs other than Pipedrive in v1 — Pipedrive-specific deal and person creation

This keeps the pipeline focused on a single workflow. Adding this capability would introduce branching logic that varies by organization, and the tradeoff between complexity and reliability was not worth it for a reusable blueprint. Fork the workflow JSON if your use case demands it.

Deployment follows a structured sequence. The Inbound Lead Qualifier bundle is designed for the following tools: n8n, Anthropic API, Pipedrive. Here is the recommended deployment path:

1. Step 1: Create Pipedrive custom deal fields. Create custom deal fields with the fw_ prefix in Pipedrive for ILQ score, qualification brief, and research summary.
2. Step 2: Configure webhook and credentials. Import the n8n workflow JSON and configure your Anthropic API key and Pipedrive API token. Point your Typeform or Tally webhook to the n8n endpoint.
3. Step 3: Submit a form and receive qualification. When a prospect submits your form, the pipeline researches the company, scores ILQ 0–10, and routes qualified leads to Pipedrive with full intelligence. Disqualified leads return a structured webhook response.

Before running the pipeline on live data, execute a manual test run with sample input. This validates that all credentials are configured correctly, all API endpoints are reachable, and the output format matches your expectations. The README includes test data examples for this purpose.

Once the test run passes, you can configure the trigger for production use (scheduled, webhook, or event-driven — depending on the blueprint design). Monitor the first few production runs to confirm the pipeline handles real-world data as expected, then let it run.

For technical background on how ForgeWorkflows blueprints are built and tested, see the Blueprint Quality Standard (BQS) methodology and the Inspection and Test Plan (ITP) framework. These documents describe the quality gates every blueprint passes before listing.

Ready to deploy? View the Inbound Lead Qualifier product page for full specifications, pricing, and purchase.