How Email Intent Classifier Routes Buyer Signals to CRM

Your sales team has 47 deals in the proposal stage. 12 have not had contact in 5+ days. Three have gone completely dark. Which ones are at risk — and which ones just have a slow procurement process? A rep answering this question manually checks Pipedrive, Gmail, cross-references email history, and makes a judgment call on each deal. At 15 minutes per deal, that is 30–60 minutes per cycle of triage before any follow-up happens.

The cost is not just time — it is revenue leakage. Deals slip because signals were missed. Pipeline reviews rely on data that was accurate two days ago. Scoring criteria drift between team members, and the CRM becomes a lagging indicator rather than an operational tool. Email Intent Classifier automates the intent scoring and revenue operations workflow from data extraction through analysis to structured output, with zero manual CRM entry.

Four Agents. Seven Intents. Emails Routed to Pipedrive Automatically.

The Email Intent Classifier pipeline runs 4 agents in sequence. The Researcher pulls data from Pipedrive and Gmail, and The Syncer delivers the output. Here is what happens at each stage and why it matters.

• The Researcher (Tier 1 Reasoning): Receives inbound email data from Gmail and conducts web-based sender research — company intelligence, role seniority, and deal context from Pipedrive.
• The Classifier (Tier 1 Reasoning): Scores each email across 7 intent categories: DEMO_REQUEST, PRICING_INQUIRY, OBJECTION, RENEWAL_INTEREST, CHURN_SIGNAL, GENERAL_INQUIRY, and SPAM_OR_NOISE.
• The Router (Conditional): Three-way confidence gate: high confidence (≥ 0.7) routes to Pipedrive CRM — deals, activities, and notes created based on intent category.
• The Syncer (Integration): Writes to Pipedrive based on intent: DEMO_REQUEST, PRICING_INQUIRY, and RENEWAL_INTEREST create Deals + Activities.

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:

• 30-node n8n workflow (.json) — you own it
• 2 tested agent system prompts (ITP-validated)
• 8 SDC inter-agent schemas
• Intent taxonomy with 7 categories and examples
• Confidence threshold tuning guide
• Error handling matrix (26 failure modes documented)
• Dependency matrix with ITP-measured costs
• README setup guide (15 minutes)

Scoring thresholds, output destinations, and CRM field mappings are configurable in the system prompts — no workflow JSON edits required. This means Email Intent Classifier 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 Email Intent Classifier execution flow.

Step 1: The Researcher

Tier: Tier 1 Reasoning

The pipeline starts here. Receives inbound email data from Gmail and conducts web-based sender research — company intelligence, role seniority, and deal context from Pipedrive. Outputs a structured research payload that gives the Classifier the context it needs for accurate intent scoring.

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 Classifier

Tier: Tier 1 Reasoning

Scores each email across 7 intent categories: DEMO_REQUEST, PRICING_INQUIRY, OBJECTION, RENEWAL_INTEREST, CHURN_SIGNAL, GENERAL_INQUIRY, and SPAM_OR_NOISE. Outputs intent classification with a confidence score (0–1.0) and chain-of-thought reasoning.

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

Step 3: The Router

Tier: Conditional

Three-way confidence gate: high confidence (≥ 0.7) routes to Pipedrive CRM — deals, activities, and notes created based on intent category. Low confidence routes to human review with full classification context. SPAM/noise logs and skips with zero additional LLM calls.

Every field in the output is structured for the next agent to consume without parsing.

Step 4: The Syncer

Tier: Integration

This is the final deliverable — what lands in your inbox or dashboard. Writes to Pipedrive based on intent: DEMO_REQUEST, PRICING_INQUIRY, and RENEWAL_INTEREST create Deals + Activities. OBJECTION and CHURN_SIGNAL create Notes on existing deals. GENERAL_INQUIRY creates an Activity. Non-blocking writes — pipeline never stalls on CRM errors.

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.

Ghost contacts, rebranded companies, missing fields — that is what ITP fixtures contain. A 524-day inactive contact is now a standard test case. You do not find out if error handling works by testing happy paths. You find out by throwing data that should not exist and verifying the pipeline does not crash.

— ForgeWorkflows Engineering

All values below are from ITP testing — not estimates, not projections. Measured across 20 test emails spanning all 7 intent categories, borderline confidence cases, and edge cases.

The primary operating cost for Email Intent Classifier is the per-execution LLM inference cost. Based on Independent Test Protocol (ITP) testing, the measured cost is: Cost per Email (ITP-Measured): $0.116/email (ITP-measured blended 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 a sales ops 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–60/month depending on email volume, depending on your usage volume and plan tiers.

Quality assurance: Blueprint Quality Standard (BQS) audit result is 12/12 PASS. ITP result is 14/14 PASS, 20/20 intent accuracy (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, 2 system prompts, intent taxonomy, threshold guide, and complete documentation.

When you purchase Email Intent Classifier, 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
• README.md — Setup and configuration guide
• blueprint_dependency_matrix.md — Third-party service dependencies
• confidence_threshold_guide.md — Confidence threshold guide
• email_intent_classifier_v1_0_0.json — n8n workflow (main pipeline)
• intent_taxonomy.md — Intent taxonomy
• system_prompt_classifier.txt — Classifier system prompt
• system_prompt_researcher.txt — Researcher 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.

Email Intent Classifier is built for Sales, Revops 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 sales or revops 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, Gmail account
• You have API credentials available: Anthropic API, Pipedrive API, Gmail OAuth2
• 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 send reply emails — output is Pipedrive records and classification data
• Does not process email attachments — classification is based on subject and body text only
• Does not support CRMs other than Pipedrive in v1 — Pipedrive-specific deal, activity, and note creation
• Does not handle email threading — each inbound email is classified independently

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 send reply emails — output is Pipedrive records and classification data

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 process email attachments — classification is based on subject and body text only

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, activity, and note 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 Email Intent Classifier bundle is designed for the following tools: n8n, Anthropic API, Pipedrive, Gmail. Here is the recommended deployment path:

1. Step 1: Connect Gmail and configure credentials. Import the n8n workflow JSON and configure your Gmail OAuth2, Anthropic API key, and Pipedrive API token.
2. Step 2: Review intent taxonomy and adjust threshold. Review the 7 intent categories in the included taxonomy guide. Adjust the confidence threshold (default 0.7) based on your email volume and review capacity.
3. Step 3: Activate and receive classified emails. Activate the workflow. Inbound emails are automatically researched, classified by intent, and routed — high confidence to Pipedrive, low confidence to human review, spam to log.

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 Email Intent Classifier product page for full specifications, pricing, and purchase.