Versioning in Stripe Workflows: Ship workflow changes with confidence

Tanya BoiteauDec 10, 2025

Source: Stripe
Published: Dec 10, 2025
Added to Yomu: Aug 28, 2026

Summary

Stripe Workflows previously required teams to edit live workflow definitions directly, leaving no draft state, historical definitions, straightforward rollback, or reliable way to inspect which configuration shaped an older run. Versioning addresses this with a dedicated draft for iteration, immutable numbered published versions, and version history that can include descriptions, authors, status, and run counts. Publishing creates a complete snapshot containing steps, branches, conditions, variable references, calls, and configuration; new runs use it immediately, while in-progress runs finish on the version they started with. Each run records its exact version and exposes the workflow definition, including taken and untaken branches, while a past version can seed a new draft for rollback; versioning is available in Stripe Workflows, where new workflows include a draft by default.

Context

Updating a live workflow previously overwrote its last version, with no draft state, historical definitions, easy rollback, or way to determine who changed logic and why. Troubleshooting older runs was limited because run details showed only the path taken, while the workflow definition might have changed or no longer existed.

Approach / What changed

Versioning separates editing from production through a dedicated draft, immutable numbered published versions, and version history. Publishing freezes a complete workflow snapshot and makes it active; future edits occur in a draft, and past versions can be used to create new drafts. Versions can include descriptions, and runs record the exact version used.

Takeaways

Drafts let teams add steps, branches, conditions, messages, or other logic without affecting the active production version until publication.
Published versions are immutable snapshots. New runs use the newly published version immediately, while in-progress runs finish on the version they started on.
Each run records its workflow version, allowing inspection of the definition and both taken and untaken branches; a known version can also support rollback.

Deployment Developer Experience Reliability

Read original post

Versioning in Stripe Workflows: Ship workflow changes with confidence

Tanya BoiteauDec 10, 2025

Source: Stripe
Published: Dec 10, 2025
Added to Yomu: Aug 28, 2026

Summary

Context

Approach / What changed

Takeaways

Drafts let teams add steps, branches, conditions, messages, or other logic without affecting the active production version until publication.
Published versions are immutable snapshots. New runs use the newly published version immediately, while in-progress runs finish on the version they started on.
Each run records its workflow version, allowing inspection of the definition and both taken and untaken branches; a known version can also support rollback.

Deployment Developer Experience Reliability

Read original post

Related reading

Stripe · May 7, 2025
Introducing Stripe Workflows: Tailoring Payments to Your Business Needs
Stripe introduces Stripe Workflows, a Dashboard-based system for orchestrating Stripe products and APIs through responsive, end-to-end automation. It addresses the complexity of coordinating multiple Stripe products by replacing custom event-handling and dependency-management code with visual workflows that support real-time triggers, branching logic, dynamic fields, and more than 600 event triggers. Workflows includes execution monitoring with event-payload and step-level tracing, 30-day default log retention, exponential-backoff retries, built-in idempotency, and recursion protection capped at a depth of five. The post describes applications including reducing chargeback risk, routing high-value transactions for compliance review, and creating custom-priced subscriptions from finalized quotes without additional infrastructure.
Ben Smith
Stripe · May 7, 2025
Sessions 2025 Developer Track resources
Stripe’s Sessions 2025 developer track recap presents new products, APIs, and enhancements for building and managing financial infrastructure. Stripe’s Workflows provides visual automation for real-time events, with more than 600 triggers, branching logic, dynamic fields, and built-in error handling, while the MCP server and agent toolkit connect AI tools and agents to Stripe documentation, account data, APIs, and financial capabilities. Accounts v2 unifies connected-account management, and fully localized Connect Mobile Embedded Components bring onboarding to iOS and Android; the Payment Element also gains support for the Checkout Sessions API. New Stripe Apps UI components, generally available Sandboxes, Organization-wide sharing of customers and payment methods, and conversational documentation extend customization, testing, and collaboration.
Ashley Ansari
Stripe · Sep 11, 2025
Workflows: Automate compliance safeguards by flagging transactions
Stripe Workflows can automate additional compliance safeguards by flagging transactions that need review before order processing. The described pattern starts when a Payment intent succeeded event occurs, retrieves the customer, and checks whether the customer’s custom_status metadata is not “Approved” while the payment amount exceeds $5,000. When these conditions are met, the workflow emails one or more designated team members with instructions for assessing the order. The examples motivating review include unusually high order values, unfamiliar sales regions, and behavioral patterns commonly associated with fraud, such as a new customer order above a monetary threshold. Workflows uses a visual building interface in the Stripe dashboard to sequence actions across multiple Stripe products, helping enforce business rules, reduce manual effort, and support risk management.
Ashley Ansari
Stripe · Jul 22, 2025
Workflows: Automatically customize an object with metadata
Stripe Workflows can customize Stripe objects with metadata, adding contextual key-value information without changing the core data model or storing it separately. The example targets customers associated with successful Payment Intents that include a tip, so a customer can be labeled for business use, such as reconciliation, reporting, or internal integrations. To build it, the workflow retrieves the customer from the Payment Intent, emails a team member, checks whether the successful Payment Intent contains a non-empty tip amount, and updates that customer with the metadata key Tier and value VIP. Workflows runs a trigger and sequential actions or conditions in a visual Stripe Dashboard builder, while metadata can carry information to later workflow steps and support automation, analytics, and debugging.
Ashley Ansari