Deal Sentiment Monitor

Real-time AI sentiment analysis on Slack deal channel messages — scores emotional tone, detects negative shifts, and alerts your team before deals go cold.

The Deal Sentiment Monitor is a 30-node n8n workflow that monitors Slack deal channel messages in real time via Event API webhook. Three agents process each message: Extractor (code-only) filters bots and short messages, maps channels to Pipedrive deals via DEAL_CHANNEL_PREFIX convention, and fetches running sentiment average. Analyst (the analysis model) performs 5-category sentiment scoring with Chain-of-Thought reasoning. Syncer (code-only) updates Pipedrive fw_deal_sentiment custom field with running average (0.7 × current + 0.3 × new), creates notes for negative shifts, and sends Slack thread replies for alerts. Five sentiment categories: positive_momentum (8-10), neutral_stable (6-7), cautious_hesitant (4-5), frustrated_negative (2-3), urgent_escalation (1). SINGLE-MODEL architecture: only the Analyst uses the analysis model — Extractor and Syncer are code-only. Lowest LLM cost product in the catalog at $0.005-$0.011/message. This came from a CRO who said the biggest pipeline surprise was deals that went cold without warning. We built a monitor that tracks sentiment shift across deal touchpoints and alerts when tone deteriorates.

Last updated March 16, 2026

The average B2B deal cycle has extended to 75+ days, with 40-60% of qualified pipeline stalling before close. Sales managers cannot inspect every deal daily. Automated deal intelligence surfaces risk signals — competitor mentions, sentiment shifts, stakeholder disengagement — before they become lost deals.

triggerSlack Event01ExtractorFilter + Map02AnalystSentiment03SyncerRoute + WritePipedriveSentiment FieldalwaysNote + AlertPD + Slackif negative

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

Extractor

Step 1Extractor

Webhook + Code

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.

Analyst

Step 2Analyst

Tier 2 Classification

What does Analyst actually decide? 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.

Syncer

Step 3Syncer

Code + Conditional Route

Without this step, upstream analysis sits idle. 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.Our first SDR used a flat 3-agent architecture. Splitting into discrete agents with handoff contracts cut processing time and made each agent independently testable.

That's the full pipeline. Here's what it intentionally does NOT do — and why those boundaries exist.

What It Does NOT Do

×

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

With those boundaries clear, here's everything that ships when you purchase.

The Complete Customer Success Bundle

5 files.

CHANGELOG.mdVersion history
README.mdSetup and configuration guide
deal_sentiment_monitor_v1_0_0.jsonn8n workflow (main pipeline)
docs/TDD.mdTechnical Design Document
system_prompts/analyst_system_prompt.mdAnalyst system prompt

The technical specifications below are ITP-measured, not estimated.

Tested. Measured. Documented.

Every metric is Independent Test Protocol (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.

Workflow Nodes

30

Blueprint Quality Standard

12/12 PASS

Agent Architecture

3 agents: Extractor (code-only), Analyst (Sonnet 4.6), Syncer (code-only)

Required Credentials

Slack (Event API + Bot Token, httpHeaderAuth Bearer), Pipedrive API, Anthropic API

Bundle Contents

7 files

Cost per Message

$0.005-$0.011/message (ITP-measured, Sonnet 4.6 only)

ITP Milestones

16/16 PASS (20/20 records, 100% defensible)

n8n Compatibility

2.7.5

Tested on n8n v2.7.5, March 2026

Deal Sentiment Monitor v1.0.0 — Technical Reference━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━Architecture: 30 n8n nodes, 3 agents (Extractor → Analyst → Syncer)Trigger:      Slack Event API Webhook (message.channels, real-time)Input:        Slack Event — message text, sender, channel, timestampIntelligence: Sonnet 4.6 (5-category sentiment scoring with CoT)Output:       Pipedrive (fw_deal_sentiment field update) + Slack (conditional thread reply)Cost:         $0.005–$0.011/message (ITP-measured)ITP:          20/20 records, 16/16 milestones PASSBQS:          12/12 PASSTool A:       Slack (input — deal channel messages via Event API)Tool B:       Pipedrive (output — sentiment field + notes)Intelligence: 5-category sentiment taxonomy + SINGLE-MODEL PER_MESSAGE patternCost Value:   0.008

What You'll Need

Platform

n8n 2.7.5+

Est. Monthly API Cost

$5-$11/month (1,000 messages/month)

Credentials Required

  • Anthropic API
  • Slack (Event API + Bot Token, httpHeaderAuth Bearer)
  • Pipedrive API (pipedriveApi)

Services

  • 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)

Setup Track

Quick Start

~15 min

All credentials live, n8n running

Full Setup

1–2 hrs

Needs API config + tables

From Scratch

2–4 hrs

No n8n, no credentials

Deal Sentiment Monitor v1.0.0

$199

one-time purchase

What you get:

  • 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 Opus needed
  • 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
  • All sales final after download

Frequently Asked Questions

How does it differ from Slack-to-CRM Activity Logger?+

Different output and purpose. SCAL logs ALL Slack deal channel messages to Pipedrive as activities with AI classification (intent category, stakeholder, CRM action). DSM scores the emotional TONE of messages and alerts on negative sentiment shifts.

What are the five sentiment categories?+

positive_momentum (8–10) — buying signals, enthusiastic engagement, deal moving forward. neutral_stable (6–7) — normal business communication, no strong emotional signals. cautious_hesitant (4–5) — hedging language, delayed responses, qualification concerns.

How does the running average work?+

The Syncer updates the Pipedrive fw_deal_sentiment custom field using a weighted running average: (current_score × 0.7) + (new_score × 0.3). This smooths out single-message noise while still responding to sentiment shifts. A single negative message nudges the average down; sustained negativity drives it down further.

When does it send alerts?+

Alerts fire on two conditions: (1) the new sentiment score is in the frustrated_negative or urgent_escalation range, or (2) the sentiment shift exceeds SENTIMENT_SHIFT_THRESHOLD (configurable). When triggered, the Syncer creates a Pipedrive note with the message context, sentiment analysis, and score, plus sends a Slack thread reply on the original message alerting the team. Normal positive/neutral scores update the field silently.

Why only Sonnet instead of Opus?+

Sentiment classification is a structured classification task that the analysis model handles with high accuracy in ITP testing. The Chain-of-Thought prompt (message_summary + tone_signals BEFORE scoring) provides sufficient reasoning structure. Opus would add cost without measurable quality improvement for this task type.

How does channel-to-deal mapping work?+

Uses a configurable DEAL_CHANNEL_PREFIX convention. Channels named with the prefix (e.g., #deal-acme-corp) map to their corresponding Pipedrive deals via prefix matching and deal search. The Extractor strips the prefix, searches Pipedrive for matching deals, and fetches the current fw_deal_sentiment running average for the matched deal.

How does it relate to Deal Stall Diagnoser?+

Complementary products covering different signals. DSM detects sentiment shifts that may PREDICT stalls before they appear in activity metrics — real-time per-message monitoring. DSD diagnoses WHY deals are stalling based on activity patterns and stage duration on a daily schedule.

How does it relate to Deal Intelligence Agent?+

Complementary products covering different scope. DIA provides full deal analysis with risk scoring across multiple dimensions on demand. DSM monitors real-time message sentiment as a leading indicator of deal health.

Does it use web scraping?+

No. All data comes from two sources: Slack Event API (message payload) and Pipedrive API (deal lookup, custom field update, notes). No web_search, no external data sources, no scraping.

Is there a refund policy?+

All sales are final after download. Review the Blueprint Dependency Matrix and prerequisites before purchase. Questions?

Read the full guide →

Related Blueprints