How Deal Sentiment Monitor Automates Sales Intelligence

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 Slack, Pipedrive, 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 Sentiment Monitor automates the sales intelligence and deal management workflow from data extraction through analysis to structured output, with zero manual CRM entry.

Three Agents. Five Sentiment Categories. Per-Message Deal Intelligence.

The Deal Sentiment Monitor pipeline runs 3 agents in sequence. Extractor pulls data from Slack and Pipedrive, and Syncer delivers the output. Here is what happens at each stage and why it matters.

• Extractor (Webhook + Code): Slack Event API Webhook fires on message.channels events in real time.
• Analyst (Tier 2 Classification): the analysis model performs 5-category sentiment scoring with Chain-of-Thought reasoning: message_summary and tone_signals are generated BEFORE sentiment_category and score.
• Syncer (Code + Conditional Route): Updates Pipedrive fw_deal_sentiment custom field with running average formula: (current × 0.7) + (new_score × 0.3).

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:

• ITP-tested 30-node n8n workflow — import and deploy
• Slack Event API Webhook for real-time message.channels event processing
• 5-category sentiment taxonomy: positive_momentum, neutral_stable, cautious_hesitant, frustrated_negative, urgent_escalation
• Chain-of-Thought scoring: message_summary + tone_signals BEFORE sentiment_category + score
• Running average formula: (current × 0.7) + (new_score × 0.3) for smooth trend tracking
• Conditional alerting: Pipedrive note + Slack thread reply for negative shifts
• Pre-LLM filters: bot filter + short message filter eliminate noise at $0 cost
• Channel-to-deal mapping via configurable DEAL_CHANNEL_PREFIX convention
• SINGLE-MODEL: the analysis model for sentiment classification — no the primary reasoning modelneeded
• Configurable: DEAL_CHANNEL_PREFIX, SENTIMENT_SHIFT_THRESHOLD, ALERT_VIA_SLACK, MIN_MESSAGE_LENGTH
• ITP 20/20 records, 16/16 milestones, $0.005–$0.011/message measured

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

Step 1: Extractor

Tier: Webhook + Code

The pipeline starts here. Slack Event API Webhook fires on message.channels events in real time. Extractor parses the raw event payload, extracts message text, sender, channel, and timestamp. Pre-LLM filters run first: bot filter removes automated messages, short message filter eliminates messages under MIN_MESSAGE_LENGTH characters. Channel-to-deal mapping uses DEAL_CHANNEL_PREFIX convention to find the corresponding Pipedrive deal and fetch the current fw_deal_sentiment running average. Only human messages with substance pass through to the Analyst.

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: Analyst

Tier: Tier 2 Classification

the analysis model performs 5-category sentiment scoring with Chain-of-Thought reasoning: message_summary and tone_signals are generated BEFORE sentiment_category and score. Five categories: positive_momentum (8–10) for buying signals and enthusiastic engagement, neutral_stable (6–7) for normal business communication, cautious_hesitant (4–5) for hedging language and qualification concerns, frustrated_negative (2–3) for complaints and competitor mentions, urgent_escalation (1) for threats to leave and deal-breaking language.

Why this step matters: The result is a prioritized action queue, not just a data dump.

Step 3: Syncer

Tier: Code + Conditional Route

This is the final deliverable — what lands in your inbox or dashboard. Updates Pipedrive fw_deal_sentiment custom field with running average formula: (current × 0.7) + (new_score × 0.3). Always writes the updated sentiment score. Conditional routing: if sentiment is negative or a significant shift is detected (exceeding SENTIMENT_SHIFT_THRESHOLD), creates a Pipedrive note with sentiment context and sends a Slack thread reply alerting the team. Normal positive/neutral scores update silently.

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.

We spent a week getting the classification modelto output exactly 3 sentences. Polite instructions like "please write 3 sentences" got ignored. LLMs do not treat polite instructions the same as system constraints. The fix was emphatic constraint language with enforcement: "OUTPUT MUST CONTAIN EXACTLY 3 SENTENCES. If output contains more or fewer than 3 sentences, the response is INVALID."

— ForgeWorkflows Engineering

Every metric is ITP-measured. The Deal Sentiment Monitor scores emotional tone on every Slack deal channel message in real time — the analysis model for 5-category sentiment classification, running average trend tracking, and conditional alerting at $0.005–$0.011/message.

The primary operating cost for Deal Sentiment Monitor is the per-execution LLM inference cost. Based on Independent Test Protocol (ITP) testing, the measured cost is: Cost per Message: $0.005–$0.011/message (ITP-measured). 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-$11/month (1,000 messages/month), depending on your usage volume and plan tiers.

Quality assurance: Blueprint Quality Standard (BQS) audit result is 12/12 PASS. ITP result is 20/20 records, 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.

7 files — workflow JSON, system prompt, configuration guides, and complete documentation.

When you purchase Deal Sentiment Monitor, 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
• deal_sentiment_monitor_v1_0_0.json — n8n workflow (main pipeline)
• docs/TDD.md — Technical Design Document
• system_prompts/analyst_system_prompt.md — Analyst 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 Sentiment Monitor 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: Slack workspace (Bot Token with channels:history, channels:read, chat:write scopes), Pipedrive account (fw_deal_sentiment custom field), Anthropic API key (~$0.005-$0.011/message)
• You have API credentials available: Anthropic API, Slack (Event API + Bot Token, httpHeaderAuth Bearer), Pipedrive API (pipedriveApi)
• 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 classify activity types — that is what Slack-to-CRM Activity Logger does
• Does not diagnose stalled deals — that is what Deal Stall Diagnoser does
• Does not perform deep deal health analysis — that is what Deal Intelligence Agent does
• Does not monitor private/direct messages — only public channel messages via Event API
• Does not create Pipedrive deals — updates existing deal sentiment field and creates notes
• Does not scrape external websites — all data from Slack events and Pipedrive API

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 classify activity types — that is what Slack-to-CRM Activity Logger does

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 diagnose stalled deals — that is what Deal Stall Diagnoser does

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 perform deep deal health analysis — that is what Deal Intelligence Agent does

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

1. Step 1: Import workflow and configure credentials. Import deal_sentiment_monitor_v1_0_0.json into n8n. Configure Slack Bot Token (httpHeaderAuth with Bearer prefix, channels:history + channels:read + chat:write scopes), Pipedrive API key, and Anthropic API key following the README.
2. Step 2: Create Pipedrive custom field and configure channel mapping. Create the fw_deal_sentiment custom field in Pipedrive (type: double/number). Set DEAL_CHANNEL_PREFIX to match your Slack channel naming convention. Configure SENTIMENT_SHIFT_THRESHOLD and ALERT_VIA_SLACK preferences.
3. Step 3: Activate and verify. Enable the workflow in n8n. Send a test message in a mapped Slack deal channel. Verify the sentiment score is computed, the Pipedrive custom field is updated with the running average, and alerts fire for negative sentiment.

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 Sentiment Monitor product page for full specifications, pricing, and purchase.