Skip to content

Finance & payments integration

Stripe integration for AI workflows.

Get paid from your workflows: Stripe customers, payment links and invoices — and react to every payment, and every failed one.

Beta

In short

Fluxo Flow connects to Stripe with an API key or credentials you provide; workflows can create a customer, find a customer by email and create a payment link and more, and start from new successful payment, new successful payment (instant) and new customer. The integration is in beta.

Beta means it works but hasn't been tested against every account setup yet; actions and fields may still change. Found a problem? Tell us.

What you can do

Actions and triggers for Stripe.

Actions

  • Create a customer

    Creates a customer.

  • Find a customer by email

    Finds customers with an exact email address (newest first).

  • Create a payment link

    Creates a shareable checkout link for a price (send it by email or SMS).

  • Create a draft invoice

    Creates a draft invoice for a customer, emailed with a due date when sent. Add lines with “Add an invoice line”, then “Finalize” and “Send”.

  • Add an invoice line

    Adds a line (amount + description) to a draft invoice.

  • Finalize an invoice

    Finalizes a draft invoice: it gets a number, a payment page and a PDF.

  • Send an invoice

    Emails a finalized invoice to the customer from Stripe.

  • List payments

    Lists recent payments (PaymentIntents), optionally for one customer.

  • List refunds

    Lists recent refunds (newest first), optionally only those created since a time or for one payment.

Triggers

  • New successful payment (checked on your plan's schedule interval)

    Starts a run for each successful charge (card, ACH, wallet…), from checkout, payment links or invoices.

  • New successful payment (instant) (instant webhook)

    Starts a run for each successful charge (card, ACH, wallet…), from checkout, payment links or invoices. Instant: Fluxo Flow adds a webhook endpoint to your Stripe account (Stripe allows 16 per account). Needs “Webhook Endpoints: Write” on the key.

  • New customer (checked on your plan's schedule interval)

    Starts a run for each customer created in Stripe.

  • New customer (instant) (instant webhook)

    Starts a run for each customer created in Stripe. Instant: Fluxo Flow adds a webhook endpoint to your Stripe account (Stripe allows 16 per account). Needs “Webhook Endpoints: Write” on the key.

  • Invoice paid (checked on your plan's schedule interval)

    Starts a run when an invoice is paid (online, or marked paid out of band).

  • Invoice paid (instant) (instant webhook)

    Starts a run when an invoice is paid (online, or marked paid out of band). Instant: Fluxo Flow adds a webhook endpoint to your Stripe account (Stripe allows 16 per account). Needs “Webhook Endpoints: Write” on the key.

  • Invoice payment failed (checked on your plan's schedule interval)

    Starts a run each time Stripe fails to collect an invoice: a declined card (including soft declines and failed automatic retries) or no saved payment method. Use it for dunning: email the customer the payment page, alert your team or pause service. Attempt count and the next retry time come with it; the decline reason is on the “Payment failed” trigger.

  • Invoice payment failed (instant) (instant webhook)

    Starts a run each time Stripe fails to collect an invoice: a declined card (including soft declines and failed automatic retries) or no saved payment method. Use it for dunning: email the customer the payment page, alert your team or pause service. Attempt count and the next retry time come with it; the decline reason is on the “Payment failed” trigger. Instant: Fluxo Flow adds a webhook endpoint to your Stripe account (Stripe allows 16 per account). Needs “Webhook Endpoints: Write” on the key.

  • Payment failed (checked on your plan's schedule interval)

    Starts a run each time a payment attempt fails (a PaymentIntent from checkout, a payment link, an invoice or your own app), with the decline code and Stripe's reason.

  • Payment failed (instant) (instant webhook)

    Starts a run each time a payment attempt fails (a PaymentIntent from checkout, a payment link, an invoice or your own app), with the decline code and Stripe's reason. Instant: Fluxo Flow adds a webhook endpoint to your Stripe account (Stripe allows 16 per account). Needs “Webhook Endpoints: Write” on the key.

Build it yourself

What teams build with Stripe.

There's no ready-made template for Stripe yet. These are the workflows to build: each step is a real node or Stripe action.

  • Payment to accounting

    1. Stripe: New successful payment (instant)
    2. QuickBooks Online: Find an invoice
    3. Human Review: check the match
    4. QuickBooks Online: Record a payment
  • Payment links from a quote

    1. Human Review: quote approved
    2. Stripe: Find a customer by email
    3. Stripe: Create a payment link
    4. Send Email
  • Invoice a client

    1. Webhook trigger (job done)
    2. Stripe: Create a draft invoice
    3. Stripe: Add an invoice line
    4. Stripe: Finalize an invoice
    5. Stripe: Send an invoice
  • Failed payment follow-up

    1. Stripe: Invoice payment failed (instant)
    2. Router: last retry?
    3. Slack: Post a message
    4. HubSpot: Create a task

Step-by-step guides: Connecting Stripe to QuickBooks or Xero: when to sync, when to automate

How to connect

Connect Stripe in a minute.

Connects with an API key or credentials, tested before they're saved and encrypted at rest.

  1. In Stripe, open Developers → API keys and create a restricted key with the permissions listed on this page.
  2. Open Settings → Integrations here, click Connect on Stripe and paste the key.
  3. Start a workflow from “New successful payment”, “Invoice paid”, “Payment failed” or “Invoice payment failed”, or create a payment link in a step.

What you need on the Stripe side

  • A restricted Stripe API key with the permissions listed below (Developers → API keys). Use a test-mode key as a separate connection to try things without real money.

Permissions & limits

What it can access, and how fast it runs.

Permissions requested

  • Customers

    Customers: Write

  • Payment links (and the price picker)

    Payment Links: Write, Prices: Read, Products: Read

  • Invoices

    Invoices: Write, Invoice Items: Write

  • List payments

    PaymentIntents: Read

  • List refunds

    Refunds: Read

  • Triggers (payments, failed payments, customers, invoices)

    Events: Read

  • Instant triggers (webhook endpoints)

    Webhook Endpoints: Write

  • Connection label

    Account: Read (optional)

Limits and timing

  • Polling triggers are checked on your plan's schedule interval: Basic every 15 minutes, Pro every 5 minutes, Business every 2 minutes, Elite every minute.
  • Instant triggers arrive by webhook within seconds of the event.
  • If Stripe says to slow down (HTTP 429 or 503), requests wait as told and retry a limited number of times.
  • Instant triggers add a webhook endpoint to your Stripe account; Stripe allows 16 per account.

FAQ

Stripe questions, answered.

Why a restricted key?

It only allows what the integration needs, and you can revoke it in Stripe at any time without touching your other keys.

Can I test without real money?

Yes. Connect a test-mode key (rk_test_…) as a separate connection; it only sees test data.

Can I react to failed payments?

Yes. “Invoice payment failed” fires when Stripe can't collect an invoice (with the attempt count, next retry time and the payment page to send the customer), and “Payment failed” fires for any failed payment attempt with the decline code and reason. Both read the same event log as the other triggers (Events: Read), and both have “(instant)” versions.

How fast do the triggers fire?

The standard triggers read Stripe's event log on your plan's schedule interval (as often as every minute), so nothing is missed even if a check is delayed — Stripe keeps 30 days of events. The “(instant)” versions add a webhook endpoint to your Stripe account and fire within seconds (beta; Stripe allows 16 endpoints per account).

Is the Stripe integration finished?

It's in beta: it works, but it hasn't been tested against every account setup yet. Tell us if something doesn't behave as expected.

Can I use Stripe on the Free plan?

You can connect it, build with it and Dry Run on the Free plan. Running workflows live (triggers, schedules, webhooks) needs a paid plan.

Can I call Stripe endpoints the integration doesn't cover?

Yes, if Stripe has an API: save a key in the encrypted credential vault and call it with an HTTP Request step.

Can I test a workflow without touching my real data?

Yes. Dry Run walks through every step with simulated app calls, so nothing is sent until you run it for real or activate its trigger.

All integrations

Connect Stripe to your first workflow.

Build and Dry Run on the Free plan, no credit card. Run live on a paid plan, on your own AI key at cost.

Free to explore · No credit card · 30-day money-back guarantee on paid plans