How Stripe Plan Migration Intelligence Classifies Changes

Your support team closed 340 tickets last week. Average resolution time: 4.2 hours. But 23 of those tickets were escalations that sat for 6+ hours before anyone noticed the SLA clock. A team lead spends 1–2 hours daily pulling reports from Stripe, Pipedrive, Slack, Gmail, cross-referencing with CRM data, and writing up findings. By the time the analysis is done, the queue has moved on.

The result is reactive support instead of proactive operations. SLA risks surface after the breach. Routing problems persist because nobody has time to audit the rules. Agent coaching happens based on gut feel, not pattern data. Stripe Plan Migration Intelligence automates the revenue intelligence workflow, delivering structured analysis from Stripe, Pipedrive, Slack, Gmail data without manual report-building.

Four Agents. Migration Classification. Three-Channel Delivery.

The Stripe Plan Migration Intelligence pipeline runs 5 agents in sequence. Fetcher pulls data from Stripe and Pipedrive and Slack and Gmail, and Formatter delivers the output. Here is what happens at each stage and why it matters.

• Fetcher (Code Only): Stripe webhook fires on customer.subscription.updated.
• Enricher (Code Only): Enriches the migration event with Pipedrive CRM context — deal stage, owner, recent activities, and account history.
• Analyst (Tier 1 Reasoning): Classifies the migration type (upgrade, downgrade, cross-grade, interval change), identifies the likely driver (feature need, cost optimization, usage growth, competitive pressure), and generates CS talking points.
• Urgency Router (IF Logic): Routes by migration urgency.
• Formatter (Tier 2 Classification): Generates three outputs: (1) Slack Block Kit migration alert with classification, driver, and talking points.

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 31-node n8n workflow — import and deploy
• Event-driven: Stripe webhook fires on customer.subscription.updated
• Migration classification: upgrade, downgrade, cross-grade, interval change
• Driver identification: feature need, cost optimization, usage growth, competitive pressure
• CS talking points tailored to migration type and driver
• Pipedrive CRM enrichment for full customer context
• Urgency routing: downgrades and high-value changes delivered instantly
• Three-channel delivery: Slack alert + Pipedrive deal note + Gmail CS draft
• Gmail drafts created for CS review — not sent automatically
• SINGLE-MODEL: the analysis model for analysis and formatting — no the primary reasoning modelneeded
• PER_EVENT pattern: runs per Stripe subscription change, not batch
• ITP 20/20 records, 14/14 milestones measured

SLA thresholds, escalation rules, and routing logic are configurable in the system prompts — customize for your ticket volume and priority structure. This means Stripe Plan Migration 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 Stripe Plan Migration Intelligence execution flow.

Step 1: Fetcher

Tier: Code Only

The pipeline starts here. Stripe webhook fires on customer.subscription.updated. Fetcher extracts subscription change data including previous and current plan details, pricing deltas, billing intervals, and customer metadata. Zero LLM cost.

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

Tier: Code Only

Enriches the migration event with Pipedrive CRM context — deal stage, owner, recent activities, and account history. Assembles a complete migration context package for the Analyst. Zero LLM cost.

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

Step 3: Analyst

Tier: Tier 1 Reasoning

Classifies the migration type (upgrade, downgrade, cross-grade, interval change), identifies the likely driver (feature need, cost optimization, usage growth, competitive pressure), and generates CS talking points. the analysis model.

This is where the pipeline applies judgment — not just data retrieval, but analysis.

Step 4: Urgency Router

Tier: IF Logic

Routes by migration urgency. Downgrades and high-value changes trigger immediate multi-channel delivery. Upgrades route through standard delivery. Configurable thresholds.

Why this step matters: This step narrows the dataset so downstream agents only process records that matter.

Step 5: Formatter

Tier: Tier 2 Classification

This is the final deliverable — what lands in your inbox or dashboard. Generates three outputs: (1) Slack Block Kit migration alert with classification, driver, and talking points. (2) Pipedrive deal note with migration context. (3) Gmail draft email for CS outreach with personalized talking points. the analysis model.

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.

n8n's webhook v2 nests data under a body key. The webhook receives { body: { email: "..." } } instead of { email: "..." }. Two lines of defensive code prevent the most common deployment failure: const data = raw.body || raw. Every blueprint ships with this guard.

— ForgeWorkflows Engineering

Every metric is ITP-measured. The Stripe Plan Migration Intelligence classifies subscription changes and generates CS talking points — the analysis model for analysis and formatting, per-event cost.

The primary operating cost for Stripe Plan Migration Intelligence is the per-execution LLM inference cost. Based on Independent Test Protocol (ITP) testing, the measured cost is: Cost per Event: Per-event cost varies by volume. 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 $40–60/hour for a support team lead’s analysis time at a fully loaded rate (salary, benefits, tools, overhead). If the manual version of this workflow takes 1–2 hours daily, 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 Per-event cost varies by volume, depending on your usage volume and plan tiers.

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

8+ files — workflow JSON, system prompts, and complete documentation.

When you purchase Stripe Plan Migration 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:

• CHANGELOG.md — Version history
• README.md — Setup and configuration guide
• docs/TDD.md — Technical Design Document
• stripe_plan_migration_intelligence_v1_0_0.json — n8n workflow (main pipeline)
• system_prompts/analyst_system_prompt.md — Analyst system prompt
• system_prompts/formatter_system_prompt.md — Formatter 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.

Stripe Plan Migration Intelligence is built for Customer Success, 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 customer success 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: Stripe account (subscription billing active), Pipedrive account (pipedriveApi credential in n8n), Slack workspace (Bot Token with chat:write scope), Gmail account (OAuth2 for draft creation), Anthropic API key
• You have API credentials available: Anthropic API, Stripe API, Pipedrive (pipedriveApi), Slack (Bot Token, httpHeaderAuth Bearer), Gmail (OAuth2)
• 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 process payments or modify subscriptions — it analyzes changes, not makes them
• Does not handle failed payment recovery — that is what Stripe Dunning Intelligence does
• Does not compute lifetime value — that is what Customer LTV Intelligence does
• Does not work with non-Stripe billing systems — Stripe webhooks only in v1.0
• Does not send emails automatically — Gmail drafts are created for CS review before sending
• Does not guarantee churn prevention — it provides intelligence and talking points for your CS team

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 process payments or modify subscriptions — it analyzes changes, not makes them

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 handle failed payment recovery — that is what Stripe Dunning Intelligence 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 compute lifetime value — that is what Customer LTV Intelligence 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 Stripe Plan Migration Intelligence bundle is designed for the following tools: n8n, Anthropic API, Stripe, Pipedrive, Slack, Gmail. Here is the recommended deployment path:

1. Step 1: Import workflow and configure credentials. Import stripe_plan_migration_intelligence_v1_0_0.json into n8n. Configure Stripe API credential, Pipedrive API credential (pipedriveApi), Slack Bot Token (httpHeaderAuth with Bearer prefix, chat:write scope), Gmail OAuth2 credential, and Anthropic API key following the README.
2. Step 2: Configure Stripe webhook and output destinations. In the Stripe Dashboard, create a Webhook Endpoint pointing to your n8n webhook URL. Subscribe to customer.subscription.updated events. Set the Slack channel for migration alerts. Configure the Pipedrive deal matching logic. Gmail drafts are created in the authenticated account.
3. Step 3: Activate and verify. Enable the workflow in n8n. Trigger a test subscription change in Stripe (or send a manual webhook POST). Verify the migration classification appears in Slack, the deal note is created in Pipedrive, and the CS draft email appears in Gmail drafts.

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 Stripe Plan Migration Intelligence product page for full specifications, pricing, and purchase.