How Deal Intelligence Agent Surfaces Pipeline Risks

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, Slack, 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. Deal Intelligence Agent automates the deal intelligence workflow from data extraction through analysis to structured output, with zero manual CRM entry.

Four Agents. Real-Time Alerts. Zero CRM Scrolling.

The Deal Intelligence Agent pipeline runs 4 agents in sequence. The Researcher pulls data from Pipedrive and Slack, and The Router delivers the output. Here is what happens at each stage and why it matters.

• The Researcher (Web Intelligence): Fires on every Pipedrive deal update.
• The Analyst (Reasoning (Tier 1)): Scores deal health across weighted criteria: deal stage velocity, engagement recency, stakeholder signals, and competitive risk.
• The Writer (Creative (Tier 2)): Generates structured Slack alerts tailored to each tier.
• The Router (Delivery (4-Tier)): Routes alerts to the right Slack channel based on DHS tier.

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)
• 4 Slack Block Kit alert templates (per tier)
• Error handling matrix (failure modes documented)
• Dependency matrix with cost estimates
• Configurable DHS scoring weights

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

Step 1: The Researcher

Tier: Web Intelligence

The pipeline starts here. Fires on every Pipedrive deal update. Pulls company context, recent news, competitive signals, and stakeholder changes from the web. Builds a real-time intelligence layer your CRM can’t provide on its own.

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 Analyst

Tier: Reasoning (Tier 1)

Scores deal health across weighted criteria: deal stage velocity, engagement recency, stakeholder signals, and competitive risk. Outputs a Deal Health Score (DHS) that routes each deal into one of four priority tiers — Critical, Attention, Healthy, or Champion.

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

Step 3: The Writer

Tier: Creative (Tier 2)

Generates structured Slack alerts tailored to each tier. Critical deals get immediate action items. Attention deals get risk summaries. Healthy deals get concise status updates. Champion deals get celebration + expansion signals.

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

Step 4: The Router

Tier: Delivery (4-Tier)

This is the final deliverable — what lands in your inbox or dashboard. Routes alerts to the right Slack channel based on DHS tier. Critical and Attention alerts go to #deals-urgent. Healthy updates go to #deals-pipeline. Champion alerts go to #deals-wins. Configurable per team.

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.

A ghost contact with 524 days inactive crashed the pipeline because output exceeded the token limit. Every field was null, the model tried to explain why each was missing, and the response ballooned past the buffer. Fix: always set max_tokens to 2x expected output and validate response completeness.

— ForgeWorkflows Engineering

All values below are from ITP testing — not estimates, not projections.

The primary operating cost for Deal Intelligence Agent is the per-execution LLM inference cost. Based on Independent Test Protocol (ITP) testing, the measured cost is: Cost per Deal Analysis: $0.22/deal analysis (incl. web search). 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 $5–15/month, 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 milestones PASS. 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.

13 files. Workflow, prompts, Slack templates, and complete documentation.

When you purchase Deal Intelligence Agent, 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
• deal_intelligence_agent_v1.json — n8n workflow (main pipeline)
• dependency_matrix.md — Third-party service dependencies
• error_handling_matrix.md — Error handling reference
• slack_templates/attention_alert.json — Slack template — Attention Alert
• slack_templates/champion_alert.json — Slack template — Champion Alert
• slack_templates/critical_alert.json — Slack template — Critical Alert
• slack_templates/healthy_update.json — Slack template — Healthy Update
• system_prompts/analyst.txt — Analyst system prompt
• system_prompts/researcher.txt — Researcher system prompt
• system_prompts/writer.txt — Writer 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.

Deal Intelligence Agent is built for Sales 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 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, Slack workspace
• You have API credentials available: Anthropic API, Pipedrive API, Slack Bot Token
• 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 move deals between pipeline stages — output is Slack alerts and intelligence, not CRM automation
• Does not replace your sales methodology — it surfaces signals, your team makes decisions
• Does not integrate with HubSpot — Pipedrive only in v1
• Does not track email engagement metrics — intelligence comes from deal data and web research

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 move deals between pipeline stages — output is Slack alerts and intelligence, not CRM automation

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 replace your sales methodology — it surfaces signals, your team makes decisions

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 integrate with HubSpot — Pipedrive only in v1

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 Deal Intelligence Agent bundle is designed for the following tools: n8n, Pipedrive, Anthropic API, Slack. Here is the recommended deployment path:

1. Step 1: Import workflow and configure credentials. Import the n8n workflow JSON and configure your Pipedrive, Anthropic, and Slack API credentials.
2. Step 2: Configure DHS scoring weights and Slack channels. Set deal health scoring weights in the Analyst node. Map each priority tier (Critical, Attention, Healthy, Champion) to a Slack channel.
3. Step 3: Activate Pipedrive webhook and receive alerts. Enable the Pipedrive deal update trigger. Every deal change is researched, scored, and routed to the appropriate Slack channel with a tier-specific alert.

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 Deal Intelligence Agent product page for full specifications, pricing, and purchase.