How NPS/CSAT Response Intelligence Automates Customer Intellig...

Turn survey responses into actionable customer intelligence. That single sentence captures a workflow gap that costs customer success, product teams hours every week. The manual process behind what NPS/CSAT Response Intelligence automates is familiar to anyone who has worked in a revenue organization: someone pulls data from Typeform, Notion, Slack, copies it into a spreadsheet or CRM, applies a mental checklist, writes a summary, and routes it to the next person in the chain. Repeat for every record. Every day.

Three problems make this unsustainable at scale. First, the process does not scale. As volume grows, the human bottleneck becomes the constraint. Whether it is inbound leads, deal updates, or meeting prep, a person can only process a finite number of records before quality degrades. Second, the process is inconsistent. Different team members apply different criteria, use different formats, and make different judgment calls. There is no single standard of quality, and the output varies from person to person and day to day. Third, the process is slow. By the time a manual review is complete, the window for action may have already closed. Deals move, contacts change roles, and buying signals decay.

These are not theoretical concerns. They are the operational reality for customer success, product teams handling customer intelligence and customer success workflows. Every hour spent on manual data processing is an hour not spent on the work that actually moves the needle: building relationships, closing deals, and driving strategy.

This is the gap NPS/CSAT Response Intelligence fills.

Four Agents. Six Themes. Weekly Sentiment Intelligence.

NPS/CSAT Response Intelligence is a multiple-node n8n workflow with 4 specialized agents. Each agent handles a distinct phase of the pipeline, and the handoff between agents is deterministic — no ambiguous routing, no dropped records. The blueprint is designed so that each agent does one thing well, and the overall pipeline produces a consistent, auditable output on every run.

Here is what each agent does:

• Fetcher (Schedule + Code): Schedule Trigger fires weekly (Friday 08:00 UTC) or manual Webhook for on-demand runs.
• Assembler (Code-only): Computes NPS score from raw responses, classifies each into promoter (9–10), passive (7–8), or detractor (0–6) segments, and groups response text for thematic analysis.
• Analyst (Tier 2 Classification): the analysis model receives ONE aggregate call with the entire weekly response batch.
• Formatter (Tier 2 Classification): the analysis model generates three outputs: (1) Notion weekly thematic analysis report with 8 sections — Executive Summary, NPS Score + Trend, Theme Distribution, Promoter Highlights, Detractor Analysis, Feature Gap Inventory, Competitor Intelligence, Week-over-Week Comparison; (2) Slack weekly summary via Block Kit; (3) Slack at-risk detractor alerts — one per actionable detractor with score, themes, verbatim quote, and recommended follow-up..

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. Specifically, you receive:

• Production-ready 23-node n8n workflow — import and deploy
• Weekly Schedule Trigger (Friday 08:00 UTC) or manual Webhook for on-demand runs
• Typeform API pagination for NPS and CSAT survey responses over 7-day lookback
• NPS score computation with promoter/passive/detractor segmentation
• 6-theme taxonomy: product_quality, support_experience, pricing_value, feature_gaps, competitor_mentions, advocacy_signals
• NPS trend comparison vs prior week with delta tracking
• Per-detractor actionable insights with verbatim quotes and recommended follow-up
• Notion weekly thematic analysis report with 8 sections (Executive Summary through Week-over-Week Comparison)
• Slack weekly summary (Block Kit) + at-risk detractor alerts with recommended actions
• AGGREGATE architecture: single Analyst + Formatter calls — $0.072/run regardless of response count
• Dual the analysis model: no the primary reasoning modelrequired
• ITP 8 variations, 14/14 milestones, $0.072/run measured

Every component is designed to be modified. The agent prompts are plain text files you can edit. The workflow nodes can be rearranged or extended. The scoring criteria, output formats, and routing logic are all exposed as configurable parameters — not buried in application code. This means NPS/CSAT Response Intelligence 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 NPS/CSAT Response Intelligence execution flow.

Step 1: Fetcher

Tier: Schedule + Code

Schedule Trigger fires weekly (Friday 08:00 UTC) or manual Webhook for on-demand runs. Fetcher paginates Typeform API for NPS and CSAT survey responses over a configurable 7-day lookback window. Extracts response scores, text feedback, respondent metadata, and submission timestamps.

This stage is critical because it ensures that downstream agents receive structured, validated input. Each agent in the pipeline trusts the output contract of the previous agent. If Fetcher identifies an issue — a missing field, a low-confidence score, or an unexpected input format — the pipeline handles it explicitly rather than passing garbage downstream. This is the difference between a prototype and a production-grade workflow: every handoff is defined, every edge case is documented.

Step 2: Assembler

Tier: Code-only

Computes NPS score from raw responses, classifies each into promoter (9–10), passive (7–8), or detractor (0–6) segments, and groups response text for thematic analysis. Produces a unified weekly response payload with segment counts, NPS delta vs prior week, and response text corpus for the Analyst.

This stage is critical because it ensures that downstream agents receive structured, validated input. Each agent in the pipeline trusts the output contract of the previous agent. If Assembler identifies an issue — a missing field, a low-confidence score, or an unexpected input format — the pipeline handles it explicitly rather than passing garbage downstream. This is the difference between a prototype and a production-grade workflow: every handoff is defined, every edge case is documented.

Step 3: Analyst

Tier: Tier 2 Classification

the analysis model receives ONE aggregate call with the entire weekly response batch. Performs thematic analysis across 6 categories: product_quality, support_experience, pricing_value, feature_gaps, competitor_mentions, and advocacy_signals. Generates NPS trend comparison vs prior week, theme distribution, and per-detractor actionable insights.

This stage is critical because it ensures that downstream agents receive structured, validated input. Each agent in the pipeline trusts the output contract of the previous agent. If Analyst identifies an issue — a missing field, a low-confidence score, or an unexpected input format — the pipeline handles it explicitly rather than passing garbage downstream. This is the difference between a prototype and a production-grade workflow: every handoff is defined, every edge case is documented.

Step 4: Formatter

Tier: Tier 2 Classification

the analysis model generates three outputs: (1) Notion weekly thematic analysis report with 8 sections — Executive Summary, NPS Score + Trend, Theme Distribution, Promoter Highlights, Detractor Analysis, Feature Gap Inventory, Competitor Intelligence, Week-over-Week Comparison; (2) Slack weekly summary via Block Kit; (3) Slack at-risk detractor alerts — one per actionable detractor with score, themes, verbatim quote, and recommended follow-up.

This stage is critical because it ensures that downstream agents receive structured, validated input. Each agent in the pipeline trusts the output contract of the previous agent. If Formatter identifies an issue — a missing field, a low-confidence score, or an unexpected input format — the pipeline handles it explicitly rather than passing garbage downstream. This is the difference between a prototype and a production-grade workflow: every handoff is defined, every edge case is documented.

The entire pipeline executes without manual intervention. From trigger to output, every decision point is deterministic: if a condition is met, the next agent fires; if not, the record is handled according to a documented fallback path. There are no silent failures. Every execution produces a traceable audit trail that you can review, export, or feed into your own reporting tools.

This architecture follows the ForgeWorkflows principle of tested, measured, documented automation. Every node in the pipeline has been validated during ITP (Inspection and Test Plan) testing, and the error handling matrix in the bundle documents the recovery path for each failure mode.

Every metric is ITP-measured. The NPS/CSAT Response Intelligence agent analyzes your weekly Typeform survey responses — computing NPS score, segmenting respondents, performing thematic analysis across 6 categories, and delivering an 8-section Notion report with Slack summary and detractor alerts at $0.072/run.

The primary operating cost for NPS/CSAT Response Intelligence is the per-execution LLM inference cost. Based on ITP testing, the measured cost is: Cost per Run: $0.072/run (ITP-measured average). 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 at a fully loaded rate (salary, benefits, tools, overhead). If the manual version of this workflow takes 20–40 minutes per cycle, that is $17–50 per execution in human labor. 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 $0.31/month (weekly runs) + Typeform/Notion/Slack free tiers, depending on your usage volume and plan tiers.

Quality assurance: BQS audit result is 12/12 PASS. ITP result is 8 variations, 14/14 milestones PASS. These are not marketing claims — they are test results from structured inspection protocols that you can review in the product documentation.

5 files — workflow JSON, system prompts, scoring guide, and complete documentation.

When you purchase NPS/CSAT Response Intelligence, 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:

• nps_csat_response_intelligence_v1_0_0.json — The 23-node n8n workflow
• README.md — 10-minute setup guide with Typeform, Notion, Slack, and Anthropic configuration
• system_prompt_analyst.txt — Analyst system prompt (6-theme taxonomy, NPS trend analysis, aggregate scoring)
• system_prompt_formatter.txt — Formatter system prompt (Notion 8-section report + Slack Block Kit + detractor alerts)
• CHANGELOG.md — Version history

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.

NPS/CSAT Response Intelligence is built for Customer Success, Product 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 customer success or product 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: Typeform account (NPS/CSAT forms with Personal Access Token), Notion workspace (API access), Slack workspace (Bot Token with chat:write scope)
• You have API credentials available: Anthropic API, Typeform (httpHeaderAuth), Notion (httpHeaderAuth), Slack (Bot Token, httpHeaderAuth)
• 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 analyze support tickets — that is what Support Pattern Analyzer does
• Does not recover abandoned forms — that is what Form Abandonment Recovery does
• Does not monitor CRM engagement health — that is what Account Health Intelligence Agent does
• Does not modify Typeform surveys or send follow-up emails — read-only analysis
• Does not scrape external websites — all data from Typeform API
• Does not track individual customer journeys — provides aggregate weekly thematic intelligence

Review the dependency matrix and prerequisites before purchasing. If you are unsure whether your environment meets the requirements, contact support@forgeworkflows.com before buying.

Deployment follows a structured sequence. The NPS/CSAT Response Intelligence bundle is designed for the following tools: n8n, Anthropic API, Typeform, Notion, Slack. Here is the recommended deployment path:

1. Step 1: Import workflow and configure credentials. Import nps_csat_response_intelligence_v1_0_0.json into n8n. Configure Typeform httpHeaderAuth credential (Personal Access Token), Anthropic API key, Notion httpHeaderAuth credential (Bearer token), and Slack httpHeaderAuth credential (Bearer token) following the README.
2. Step 2: Configure schedule and Typeform form IDs. The Schedule Trigger defaults to weekly (Friday 08:00 UTC). Adjust the cron expression to match your reporting cadence. Configure the Typeform form IDs for your NPS and CSAT surveys, the lookback window (default 7 days), and Slack channel for weekly summary and detractor alerts.
3. Step 3: Activate and verify. Enable the workflow in n8n. Trigger a manual run via the Webhook URL. Verify the Notion weekly report is created with all 8 sections, Slack summary posts to the configured channel, and at-risk detractor alerts fire for respondents with low scores and actionable themes.

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 NPS/CSAT Response Intelligence product page for full specifications, pricing, and purchase.