FlowRunner
PricingContact
Theme
Start Free

Stripe

Payments

Automate your full revenue cycle. Stripe triggers fire on payment events. Agents process charges, manage subscriptions, issue refunds, and escalate anomalies to your team before they become problems.

Verified 1 trigger 66 actions OAuth available
Stripe website ↗ Capability data verified 2026-08-04
Parse Webhook Event fires when subscription payment fails
Agent retrieves failure reason: insufficient funds vs. expired card
Agent sends payment update email for expired card failures
Agent waits 3 days and retries for insufficient funds failures
Billing team receives Slack alert if second attempt also fails
Accounts that fail twice routed to billing team for grace period or cancellation decision

What This Integration Enables

The Stripe integration gives agents control over the complete payment infrastructure. Agents collect payment through intents, checkout sessions, and payment links, handle subscription lifecycles, process refunds, run the invoice from draft to void, and read across connected accounts. Combined with FlowRunner's human-in-loop capability, agents process routine transactions automatically and surface anomalies for your team to review before money moves.

Without FlowRunner

Manual payment failure handling Billing staff check Stripe dashboard daily for failed payments and handle each manually
No dunning logic All failed payments treated the same regardless of failure reason
Slow dispute response Chargeback evidence assembled over 2-3 hours by pulling records from multiple systems

With FlowRunner

Automated failure reason routing Expired cards and insufficient funds each get the appropriate recovery sequence
4-minute dispute evidence package Order records, emails, and shipping data compiled and uploaded to Stripe automatically
New customer fully provisioned Stripe customer, subscription, invoice, and notification all created within seconds of deal close

Use Case Scenarios

Subscription Renewal with Dunning Logic

A subscription payment fails. Parse Webhook Event fires. The agent checks the failure reason: insufficient funds versus expired card. For expired cards, it sends an automated email with a payment update link. For insufficient funds, it waits 3 days and retries. If the second attempt fails, it pauses and routes to the billing team via Slack: "This account has failed twice. Do you want to extend grace period or begin cancellation?" The team decides. The agent acts.

Dispute Detection and Evidence Package

A chargeback dispute opens. Parse Webhook Event fires. The agent pulls the original order record, retrieves related emails and shipping data from connected systems, and assembles an evidence package for the team, who submit it in the Stripe Dashboard. The assembly that normally eats an afternoon of cross-system digging is waiting in the queue when someone picks the dispute up. The agent surfaces any disputes it cannot confidently build evidence for with full context.

New Customer Onboarding

A deal closes in HubSpot. The Salesforce or HubSpot integration fires. The agent creates a Stripe customer, creates a subscription, generates the first invoice, finalizes it, and sends it, then posts a summary to the #revenue-ops Slack channel. The customer is billed and the team knows about it without anyone touching Stripe manually.

Human-in-Loop Highlight

Refunds, cancellations, and large transactions should not move without human awareness. Configure threshold rules: any refund over $500 pauses the workflow and routes to the billing manager via Slack with the refund reason and customer history. The manager approves or modifies with one click. The agent processes the exact amount approved. Every decision is logged in the audit trail with the approver's identity and timestamp.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via Slack
Human decides
Agent resumes with decision

Agent Capabilities

66 actions

Customers

5
  • Create Customer Creates a Stripe customer record. Used in onboarding: a new contact in the CRM provisions the billing identity without anyone opening Stripe.
  • Get Customer Retrieves a customer by ID. The standing check before any workflow bills, credits, or cancels against that account.
  • Update Customer Updates a customer's email, default source, payment method, or metadata. Used when an account change in one system has to propagate to the system that takes the money.
  • Get Customers List Returns customers sorted newest first. Used for reconciliation, audit, and cohort reporting.
  • Delete Customer Permanently deletes a customer and immediately cancels their active subscriptions. It cannot be undone, which is why it belongs behind an approval rather than inside a cleanup loop.

Payment Intents

5
  • Create Payment Intent Creates the object representing an intent to collect from a customer. Used when authorization and capture need to be separate steps rather than one call.
  • Get Payment Intent Retrieves a payment intent with its current status. The state check in any multi-step collection flow.
  • Confirm Payment Intent Confirms a payment intent against a specific payment method, moving it toward capture. Run once the agent has verified the conditions the business actually cares about.
  • Cancel Payment Intent Cancels a payment intent while it is still in a cancellable state. Used when an upstream condition fails and the charge should never happen.
  • Get Payment Intents List Lists payment intents with filters. Used for reconciliation and monitoring against the ledger of record.

Subscriptions

5
  • Create Subscription Creates a subscription on an existing customer. Used when a deal closes: the agent provisions recurring billing and starts the welcome sequence in the same run.
  • Get Subscription Retrieves a subscription by ID. The verification step before dunning, upgrade, or churn logic branches.
  • Update Subscription Modifies a subscription's plan, quantity, or billing behavior. Used for upgrade and downgrade flows driven by usage data rather than by a support ticket.
  • Cancel Subscription Cancels a subscription and by default finalizes the current period and issues a final invoice, with optional proration behavior. Used in churn flows, after a human has confirmed the intent.
  • Get Subscriptions List Lists subscriptions filtered by customer or status. Used for revenue reporting and cohort analysis.

Products and Prices

9
  • Create Product Creates a product object for use in subscriptions or checkout. Used so a launch in the product system syncs the billing catalog instead of waiting on someone to mirror it.
  • Get Product Retrieves a product by ID.
  • Update Product Updates an existing product's details.
  • Delete Product Deletes a product, and with it every price attached to that product. The blast radius is larger than the name suggests.
  • Get Products List Lists products, filterable by active status.
  • Create Price Creates a price defining a recurring or one-time charge for a product.
  • Get Price Retrieves a price by ID.
  • Update Price Updates an existing price.
  • Get Prices List Lists prices, filterable by active status or product.

Invoicing

9
  • Create Invoice Creates an invoice for a customer. Used in AR flows where a completed milestone should produce a bill the same day rather than at month end.
  • Get Invoice Retrieves an invoice by ID.
  • Update Invoice Updates an invoice that is still editable.
  • Get Invoices List Lists invoices filtered by customer or date.
  • Finalize Invoice Locks the invoice against further changes and attempts to charge the customer. This is the point where a draft stops being a draft, and the natural place to put a review step.
  • Send Invoice Emails the invoice to the customer. The write that reaches a person outside the company and cannot be recalled.
  • Void Invoice Marks a finalized invoice void. This cannot be undone, but unlike deletion it preserves the paper trail, which is what an auditor will ask for.
  • Mark Invoice as Uncollectible Flags an invoice as bad debt for write-off. Used to keep the AR ledger honest about what is genuinely never arriving.
  • Pay Invoice Attempts collection on an invoice outside the normal subscription schedule. Used for off-cycle collection and retry logic.

Refunds

5
  • Create Refund Refunds a charge or payment intent. The money-out write, and the one most flows put a threshold on.
  • Retrieve Refund Retrieves a refund by ID.
  • Update Refund Updates a refund's metadata.
  • Get Refunds List Lists refunds filtered by charge, payment intent, or limit.
  • Cancel Refund Cancels a refund, but only while it has not yet been submitted to the bank or card network. The window is short and closes without warning, which is exactly why the approval belongs before Create Refund rather than after.

Payouts and Transfers

9
  • Create Payout Creates a payout to a bank account or debit card. Money leaving the Stripe balance for the real world.
  • Get Payout Retrieves a payout by ID.
  • Update Payout Updates a payout's metadata.
  • Get Payouts List Lists payouts filtered by creation date, destination, or status.
  • Cancel Payout Cancels a payout while its status is still pending, returning the funds to the available balance. Automatic Stripe payouts cannot be canceled at all, so the reversibility here depends on how the account is configured.
  • Create Transfer Moves funds between accounts. Used in marketplace and platform settlement flows.
  • Get Transfer Retrieves a transfer by ID.
  • Update Transfer Updates a transfer's metadata.
  • Get Transfers List Lists transfers with filters.

Checkout and Payment Links

11
  • Create Checkout Session Creates a hosted checkout session so a customer can pay on Stripe's page rather than in a form you maintain.
  • Get Checkout Session Retrieves a checkout session by ID.
  • Update Checkout Session Updates a session's metadata and payment method options.
  • Get Checkout Sessions List Lists checkout sessions filtered by customer or limit.
  • Expire Checkout Session Expires a session, preventing any further interaction or payment through it. Used to close a quote window that has passed.
  • Create Payment Link Creates a shareable payment URL. Used in sales automation: a quote is accepted, and the agent delivers the link by email or Slack in the same minute.
  • Get Payment Link Retrieves a payment link by ID.
  • Update Payment Link Updates a payment link, including deactivating it.
  • Deactivate Payment Link Deactivates a payment link so it stops accepting payment. Worth knowing that a deactivated link is still a URL someone has in their inbox, and it fails visibly rather than quietly.
  • Get Payment Links List Lists payment links with filters.
  • Get Payment Link Line Items Retrieves the line items on a specific payment link. Used to confirm what a link actually charges for before it goes out.

Account and Infrastructure

8
  • Get Balance Returns the current account balance. The read that fronts daily treasury reporting and any payout decision.
  • Get Connected accounts Lists every connected account under the platform. Used in marketplace reporting and settlement flows.
  • Create Webhook Endpoint Creates a webhook endpoint to receive Stripe events. Used when standing up a new workflow environment.
  • Get Webhook Endpoint Retrieves a webhook endpoint by ID.
  • Update Webhook Endpoint Updates an endpoint's URL or subscribed event list.
  • Get Webhook Endpoints List Lists the configured webhook endpoints.
  • Delete Webhook Endpoint Deletes a webhook endpoint. Removing the wrong one silently stops a production flow from ever waking up, and nothing in Stripe will tell you.
  • Run Custom Request Runs any Stripe method with the connection's credentials attached. The escape hatch for edge cases the pre-built actions do not cover.

Triggers

1 triggers

Event Triggers

1
  • Parse Webhook Event (handles all Stripe webhook events) Receives Stripe webhook events and parses the payload into a structured event for the rest of the flow. It handles every Stripe event type: payment succeeded, payment failed, subscription created, subscription canceled, dispute opened, refund updated. This single trigger is the entry point for the whole reactive side of payment automation, which is also why the branching logic that follows it carries so much weight.

Frequently Asked Questions

What can FlowRunner do with Stripe?

FlowRunner agents can run Get Balance, Get Connected accounts, and Create Customer in Stripe, plus 63 more actions.

Does connecting Stripe to FlowRunner require OAuth?

Yes. Stripe connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can Stripe trigger a FlowRunner workflow automatically?

Yes. Stripe supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Stripe

$100 in credits. No card required. Connect in minutes.