Slack Standup Summarizer
AI-powered daily standup summarizer that extracts progress, commitments, blockers, and dependencies from your Slack standup channel — delivered as a structured Notion page every morning.
The Slack Standup Summarizer is a 25+3 node n8n workflow (main + scheduler) that extracts structured standup intelligence from your Slack channel every weekday morning. Split-workflow pattern: Scheduler fires at 10:00 UTC on weekdays, triggers the main pipeline via HTTP Request. Weekend Skip gate prevents unnecessary API calls on Saturday/Sunday. Config Loader enables Independent Test Protocol (ITP) bypass for testing. Slack Fetcher retrieves standup channel messages from the past 24 hours using channels:history API with user resolution via users:read. Assembler (code-only) structures messages by team member with timestamps. Empty Gate prevents LLM calls when no standup messages exist. Analyst (the analysis model) extracts four structured categories per person: progress (what was done), commitments (what will be done), blockers (what is stuck), and dependencies (what needs others). Formatter (code-only) builds Notion blocks with structured sections per team member. Notion Page Creator publishes the daily summary as a new Notion page. SINGLE-MODEL architecture: only the Analyst uses the analysis model — Fetcher, Assembler, and Formatter are code-only. $0.01-$0.04/run. We built this after an engineering manager told us he read 47 Slack standup messages every morning and still missed blockers. The summarizer extracts blockers, progress, and risks from async standups and delivers a structured digest.
Last updated March 16, 2026
Distributed engineering teams generate hundreds of Slack messages per standup channel per week. Managers scan threads manually, missing blockers mentioned at odd hours. Automated standup summarization extracts status, blockers, and commitments from async communication and delivers a structured digest.
Four Agents. One Daily Digest. Zero Manual Standup Notes.
Step 1 — Fetcher
Schedule + Code
Split-workflow pattern: Scheduler fires at 10:00 UTC on weekdays, triggers the main pipeline via HTTP Request. Weekend Skip gate prevents API calls on Saturday/Sunday. Slack Fetcher retrieves standup channel messages from the past 24 hours using channels:history API with user resolution via users:read. Bot messages and system notifications are filtered out before any processing.
Step 2 — Assembler
Code
What does Assembler actually decide? Structures raw Slack messages by team member with timestamps. Groups each person’s standup contributions into a single record with message text, author display name, and posting time. Empty Gate checks if any messages exist — if the channel had no standup messages, the pipeline skips the LLM call entirely at $0 cost.
Step 3 — Analyst
Tier 2 Classification
This step exists because raw data alone is not enough. the analysis model extracts four structured categories per team member from their standup messages: progress (what was completed), commitments (what will be done next), blockers (what is stuck or delayed), and dependencies (what needs input from others). AGGREGATE pattern: single LLM call processes all team members’ messages together for cross-reference and dependency mapping.
Step 4 — Formatter
Code + Notion
Without this step, upstream analysis sits idle. Builds structured Notion blocks with per-person sections containing progress, commitments, blockers, and dependencies. Creates a new Notion page under the configured parent page with the date as the title. The result is a clean, browsable daily standup summary that your team can reference throughout the day.n8n cannot run a schedule trigger and a webhook response in one workflow. Every scheduled blueprint ships as two separate files.
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 extract feature requests — that is what Feature Request Extractor does
Does not score sentiment — that is what Deal Sentiment Monitor does
Does not detect buying signals — that is what Buying Signal Detector does
Does not monitor private/direct messages — only public channel messages via channels:history
Does not create Slack messages or replies — output is Notion pages only
Does not scrape external websites — all data from Slack API and Notion API
With those boundaries clear, here's everything that ships when you purchase.
The Complete Customer Success Bundle
6 files.
The technical specifications below are ITP-measured, not estimated.
Tested. Measured. Documented.
Every metric is Independent Test Protocol (ITP)-measured. The Slack Standup Summarizer extracts structured standup intelligence from your Slack channel every weekday — the analysis model for progress, commitments, blockers, and dependencies extraction at $0.01–$0.04/run.
Workflow Nodes
25+3 (main+scheduler)
Blueprint Quality Standard
12/12 PASS
Agent Architecture
4 agents: Fetcher (code-only), Assembler (code-only), Analyst (Sonnet 4.6), Formatter (code-only)
Required Credentials
Slack (Bot Token, httpHeaderAuth Bearer with channels:history, channels:read, users:read), Notion (httpHeaderAuth Bearer), Anthropic API
Bundle Contents
7+ files
Cost per Run
$0.01-$0.04/run (ITP-measured, Sonnet 4.6 only)
ITP Milestones
16/16 PASS (8/8 records, 100% defensible)
n8n Compatibility
2.7.5
Tested on n8n v2.7.5, March 2026
Slack Standup Summarizer v1.0.0 — Technical Reference━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━Architecture: 25+3 n8n nodes (main+scheduler), 4 agents (Fetcher → Assembler → Analyst → Formatter)Trigger: Daily schedule (10:00 UTC weekdays) + WebhookInput: Slack — standup channel messages (past 24h)Intelligence: Sonnet 4.6 (4-category standup extraction with structured output)Output: Notion — daily standup summary pageCost: $0.01–$0.04/run (ITP-measured)ITP: 8/8 records, 16/16 milestones PASSBQS: 12/12 PASSTool A: Slack (input — standup channel messages via channels:history)Tool B: Notion (output — daily summary page)Intelligence: 4-category extraction + SINGLE-MODEL AGGREGATE patternCost Value: 0.025
What You'll Need
Platform
n8n 2.7.5+
Est. Monthly API Cost
$0.20-$0.80/month (20 weekday runs)
Credentials Required
- ▪Anthropic API
- ▪Slack (Bot Token, httpHeaderAuth Bearer)
- ▪Notion (Integration Token, httpHeaderAuth Bearer)
Services
- ▪Slack workspace (Bot Token with channels:history, channels:read, users:read scopes)
- ▪Notion workspace (Integration with page create permissions)
- ▪Anthropic API key (~$0.01-$0.04/run)
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
Slack Standup Summarizer v1.0.0
$199
one-time purchase
What you get:
- ✓ITP-tested 25+3 node n8n workflow (main + scheduler) — import and deploy
- ✓Split-workflow pattern: independent scheduler for daily 10:00 UTC weekday trigger
- ✓4-category extraction: progress, commitments, blockers, dependencies per team member
- ✓Weekend Skip gate: zero API calls on Saturday/Sunday
- ✓Empty Gate: zero LLM cost when no standup messages exist
- ✓AGGREGATE pattern: single the analysis model call for all messages — cross-references dependencies
- ✓Structured Notion page output with per-person sections and date title
- ✓SINGLE-MODEL: the analysis model for standup analysis — no Opus needed
- ✓Configurable: STANDUP_CHANNEL_ID, NOTION_PARENT_PAGE_ID, SUMMARY_TIME_UTC
- ✓ITP 8/8 records, 16/16 milestones, $0.01–$0.04/run measured
- ✓All sales final after download
Frequently Asked Questions
What does each standup summary contain?+
For each team member who posted in the standup channel, the Analyst extracts four categories: progress (what was completed since last standup), commitments (what they plan to do next), blockers (what is stuck or delayed), and dependencies (what needs input from others). The Notion page organizes these by person with timestamps.
What happens on weekends?+
The Weekend Skip gate checks the current day before any API calls. On Saturday and Sunday, the pipeline exits immediately with zero cost — no Slack API calls, no LLM calls, no Notion writes. The scheduler fires daily but the gate ensures weekday-only execution.
What if the standup channel has no messages?+
The Empty Gate checks whether any standup messages were retrieved from the past 24 hours. If the channel is empty (holiday, team offsite, no one posted), the pipeline skips the Analyst LLM call and exits cleanly at $0 cost. No empty Notion pages are created.
Why only Sonnet instead of Opus?+
Standup extraction is a structured classification task: identify which sentences describe progress, commitments, blockers, or dependencies. the analysis model handles this with high accuracy in ITP testing. Opus would add cost without measurable quality improvement.
How does the split-workflow pattern work?+
Two separate n8n workflows: (1) Scheduler workflow uses Schedule Trigger to fire at 10:00 UTC on weekdays, then sends an HTTP Request POST to the main workflow’s webhook URL. (2) Main workflow uses Webhook Trigger + respondToWebhook for the full pipeline. This lets you customize the schedule independently of the pipeline logic, and test the main workflow via manual webhook calls.
How does it differ from Feature Request Extractor?+
Different output and purpose. FRE extracts feature requests from Slack channels and routes them to Linear as structured tickets with priority and product area. SSS extracts standup progress, commitments, blockers, and dependencies from a dedicated standup channel and delivers a structured Notion page.
How does it differ from Deal Sentiment Monitor?+
Different trigger and focus. DSM scores emotional tone on Slack deal channels in real time per message with Pipedrive sentiment field tracking. SSS summarizes daily standup messages into structured progress reports on a daily schedule with Notion page delivery.
Does it use web scraping?+
No. All data comes from two sources: Slack API (channels:history for messages, users:read for display names) and Notion API (page creation). 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?
Related Blueprints
Feature Request Extractor
Every feature request in Slack becomes a structured Linear issue. Automatically.
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.
Buying Signal Detector
Know which accounts just entered a buying window. Before your competitors do.