Resources · Zapier integration

Stripe Zapier integrationAutomate Stripe with Zapier.

The Stripe Zapier integration gives you 16 triggers, 13 actions and 8 searches to react to payments, subscriptions and disputes, then create customers, invoices or payment links without opening the Stripe dashboard. It works on the free plan.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Stripe Zapier integration actually does for you

It links your Stripe account to Zapier so that something happening in Stripe (a payment, a cancellation, a dispute) starts an automation, and so that other tools can write back into Stripe. Stripe is not a premium app on Zapier, so the free plan is enough to start.

Three results come up again and again. A churn alert: Canceled Subscription fires the moment someone leaves, and the next step warns whoever owns the account. A dunning follow-up: Invoice Payment Failed or Failed Payment hands the failed attempt to your support or finance tool. A sale built from a form: Create Payment Link or Create Checkout Session turns a request typed elsewhere into a link the buyer can pay.

Most of the Stripe triggers are instant: 11 of the 16 report to Zapier on their own, so a free plan does not slow them down. The five others (new events, invoices, invoice items, payment links, refunds) are checked on a timer.

What it does not do: there is no refund action and no delete action in the list, so refunds and clean-ups stay in the dashboard. Nothing that happened before the Zap went live is picked up either. If you are weighing other tools, the Stripe n8n integration and the Stripe Make integration pages cover the same app on the other two platforms.

Vocabulary

Zapier vocabulary in one minute

Eight words are enough to read the rest of this page. Each one is used exactly as defined here.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every single time that trigger event happens.
Trigger
The Stripe event that starts the Zap. Once the Zap is switched on, Zapier sits and waits for that event to happen.
Action
What the Zap does after it starts: the step that creates, sends or changes something for you, in Stripe or in another tool.
Task
The unit Zapier bills you for: one action your Zap completes successfully. Your plan's allowance is a count of these.
Polling trigger
A trigger Zapier checks on a timer: it asks Stripe for new items at a fixed interval and keeps only the ones it has not seen.
Instant trigger
A trigger Stripe reports by itself: it calls Zapier the moment the event happens, so nothing waits for the next check.
Filter
A step that lets the Zap continue only when what arrived meets your condition, and stops it in every other case.
Search step
A step that looks up something already in Stripe, a customer or an invoice, so the next steps can use what it found.
Cost

What a Stripe Zap really costs

Watching Stripe is free. A payment or a cancellation that starts your Zap costs nothing, and Zapier checking a polling trigger costs nothing either. Only completed actions are billed.

  • Trigger0 tasks, every time
  • Action that works1 task each
  • Action that fails0 tasks
  • Free plan100 tasks a month, unlimited Zaps, two steps per Zap
  • Filter or search stepmakes the Zap multi-step, paid plan

Each action that goes through counts as one task, separately: a failed payment that updates a customer and posts a message elsewhere eats two. A failed action is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but every Zap stays at two steps, one trigger and one action. Adding a second action, a filter or a search turns it into a multi-step Zap, and that needs a paid plan. A few apps and actions take more than one task.

Connect

Connect your Stripe account in three steps

  1. 01

    Open your Apps page

    In Zapier, go to the Apps page of your account and click + Add connection. A connection is your Stripe account, linked once and then reused by every Stripe step. You need a Stripe account that can reach whatever the Zap will read or write.

  2. 02

    Pick Stripe

    Type Stripe in the search box of the dialog, select it, then click Add connection. A new tab opens on the Stripe side so you can sign in with your usual login.

  3. 03

    Grant access

    Sign in to Stripe in that tab and allow Zapier to reach the account. Back in Zapier, the connection shows up in your list, and every Stripe step reuses it.

First Zap

Your first Stripe Zap: tag customers who cancel

GoalWhen a subscription is canceled, find the Stripe customer behind it and update their record, so the cancellation is visible on the customer itself.

  1. 01

    Build the trigger

    Create a Zap, pick Stripe as the app and Canceled Subscription as the event, then choose your Stripe connection. This trigger is instant, so the plan interval never applies.

  2. 02

    Test it on real data

    Run the trigger test. Zapier brings back the three most recent cancellations from your account, and you pick one to map the next steps on a real record.

  3. 03

    Add the search

    Add Find Customer and pass it the customer from the cancellation. This search step makes the Zap multi-step, so it needs a paid plan.

  4. 04

    Add the update

    Add Update Customer, map the Customer ID returned by the search, and fill in the fields you want changed on that customer.

  5. 05

    Test, then publish

    Run each step once and read what came back before going further. When every step looks right, click Publish to switch the Zap on.

Triggers

The 16 Stripe triggers

16 events start a Zap when something happens in Stripe, and 11 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Canceled Subscription

Instant trigger

In Zapier“Triggers when a subscription is canceled (by a subscriber or due to end of billing period).”

Starts the Zap when a subscription is canceled, whether the subscriber left on their own or the billing period came to its end. The signal sits on the subscription itself, not on a payment.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
warn the account owner in your CRM or team chat so someone can reach out before the customer is gone for good.
Watch out
subscriptions canceled before you publish the Zap are never picked up, so an old churn list has to be moved by other means.
2

Checkout Session Completed

Instant trigger

In Zapier“Triggers when a checkout session is completed.”

Fires once a buyer completes a Stripe Checkout session, which is the moment a sale really exists.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
send the new buyer to your onboarding tool or your email list as soon as the payment page closes, with no manual export.
Watch out
when you test it, Zapier pulls the three most recent completed sessions of the connected account, so map the next steps on one of those.
3

Failed Payment

Instant trigger

In Zapier“Triggers when a payment attempt fails.”

As soon as a payment attempt fails in your Stripe account, the Zap starts, so the failure reaches a person instead of sitting in the dashboard.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
open a ticket for your support team or ping the sales rep who closed the deal, while the buyer still remembers the purchase.
Watch out
Invoice Payment Failed is a separate trigger, described for invoice payments only. Pick the one whose description matches the alert you want.
4

Invoice Payment Failed

Instant trigger

In Zapier“Triggers when an invoice payment fails.”

Reacts when the payment of an invoice fails, so the follow-up starts from the invoice that was not paid.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
feed a dunning sequence, a finance channel or a follow-up task with the exact invoice that was not paid, so nobody hunts for it in the dashboard.
5

New Charge

Instant trigger

In Zapier“Triggers when a new charge is completed.”

Reports each completed charge in your Stripe account, as soon as Stripe records it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
log every incoming amount in a spreadsheet or accounting tool.
Watch out
the trigger has a required Ignore payments intents setting. Set it to True if you also use New Payment, otherwise the same sale can arrive twice, once as a charge and once as a payment.
6

New Customer

Instant trigger

In Zapier“Triggers when a new customer is added.”

Each new customer added to your Stripe account starts the Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
copy the new customer into your CRM or newsletter tool, so sales and marketing see the same people as billing.
Watch out
a Zap that answers this trigger with Create Customer creates a new customer, which fires the trigger again, and the loop eats your tasks.
7

New Dispute

Instant trigger

In Zapier“Triggers when a customer disputes a charge.”

When a customer disputes a charge, this trigger reports the new dispute to Zapier.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
alert whoever handles disputes and open a task with the disputed charge attached, so the case has an owner as soon as it opens.
Watch out
later changes to the same case are the job of Updated Dispute.
8

New Subscription

Instant trigger

In Zapier“Triggers when a customer is signed up for a new plan.”

Fires when a customer is signed up to a plan, the starting point of every recurring relationship in Stripe.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
give the new subscriber access to your product, add them to a welcome sequence, or post the win in the sales channel the moment it happens.
Watch out
plan changes on an existing subscription do not start this trigger. They come through Updated Subscription instead.
9

New Event

Polling trigger

In Zapier“Triggers on a new event.”

The catch-all: it picks up new events from your Stripe account, including types no dedicated trigger covers. Think of it as the fallback when the list above has nothing for your case.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
react to an event that has no trigger of its own, after checking that none of the instant ones fits.
Watch out
unlike most Stripe triggers, this one waits for the next check, so on the free plan the reaction is never immediate.
10

New Invoice Item

Polling trigger

In Zapier“Triggers when a new invoice item is created.”

Watches the individual items added to invoices rather than the invoices themselves.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
track add-ons, usage fees or one-off extras pushed onto a customer's next invoice, line by line, in a sheet your team can read.
Watch out
it is a polling trigger, so on the free plan a new item shows up at the next check, not the moment it is added.
11

New Invoice

Polling trigger

In Zapier“Triggers on a new invoice. You can filter based on the invoice's status. (supports line items)”

Brings each new invoice into the Zap, with its line items, and lets you narrow what comes through by the status of the invoice.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
copy paid invoices into your accounting tool, or open a follow-up for invoices still waiting, depending on the status you keep.
Watch out
set the status in the trigger itself rather than adding a filter later, which would push the Zap into multi-step territory and onto a paid plan.
12

New Payment

Instant trigger

In Zapier“Triggers when a new payment is completed.”

Fires on every completed payment, the record Stripe builds when a buyer actually pays you through a payment flow.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
thank the buyer, notify the person who handles fulfilment, or add the amount to a revenue sheet the minute it lands.
Watch out
this trigger and New Charge can describe the same sale. Run one of them, or switch on Ignore payments intents in New Charge so each sale arrives once.
14

New Refund

Polling trigger

In Zapier“Triggers when a charge is refunded, including partial refunds.”

Picks up refunded charges, partial refunds included, so money going back out is tracked as carefully as money coming in.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
update your books or your margin report, or let the account manager know a customer got part of their money back.
Watch out
the integration has no refund action, so this trigger tells you about refunds but a Zap cannot issue one.
15

Updated Subscription

Instant trigger

In Zapier“Triggers when a customer subscription has changed.”

Any change to an existing subscription starts the Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
keep the plan name and status in your CRM in step with Stripe, so upgrades and downgrades are visible to the people who talk to the customer.
Watch out
it fires on many kinds of change. On a paid plan, a filter on the field you care about keeps the noise out.
16

Updated Dispute

Instant trigger

In Zapier“Triggers when a dispute is updated (usually with evidence).”

Follows an open dispute after its creation, most often when evidence is added to the case.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
keep the task or ticket you opened for the dispute in step with its progress, so whoever owns it does not have to refresh the dashboard.
Watch out
one dispute can be updated several times, and each update runs the Zap and bills its actions again.
Actions

The 13 Stripe actions

Stripe gives you 13 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Cancel Subscription

Action

In Zapier“Cancels a subscription.”

Ends a subscription immediately, from its Subscription ID, and the customer is not charged again for it.

When to use it
close access in Stripe when an offboarding is confirmed in your support or CRM tool.
Watch out
pending invoice items you created are still charged at the end of the period, unless someone deletes them by hand.
2

Confirm Payment

Action

In Zapier“Confirms an existing payment, also known as a PaymentIntent.”

Takes a payment that was prepared but not confirmed and pushes it through, using the Payment ID the step requires.

When to use it
split preparing and charging, with an approval in between, so money only moves once someone has said yes.
Watch out
switch on Error on Requires Action? if you want the step to fail rather than leave a payment waiting on the buyer.
3

Create Checkout Session

Action

In Zapier“Creates a new Checkout Session.”

Creates a new Stripe Checkout session for a buyer to pay through, with promotion codes or automatic tax as options.

When to use it
build a payment page for a single order coming from another tool.
Watch out
the Success URL is required: the page where buyers land after paying must exist before you build the step.
4

Create Customer

Action

In Zapier“Creates a new customer.”

Adds a new customer record to Stripe from data that lives in another tool, a form entry or a CRM contact for instance.

When to use it
prepare the Stripe side before you invoice someone who signed up elsewhere.
Watch out
run Find Customer first if the person might already exist, or you end up with duplicates.
5

Create Invoice

Action

In Zapier“Creates a new invoice.”

Drafts an invoice and, through its yes-or-no options, can also finalize it, send it, try to collect it, or mark it as paid outside Stripe.

When to use it
bill a customer the moment a job is marked done in your project tool.
Watch out
with automatic collection off, the invoice stays where it is until someone acts on it.
6

Create Payment

Action

In Zapier“Creates a new payment, also known as a PaymentIntent.”

Prepares a payment, what Stripe calls a PaymentIntent, and can charge it straight away if you ask.

When to use it
charge a saved customer for an extra service logged elsewhere.
Watch out
Confirm Payment Immediately? is off by default, so the step charges nothing until you switch it on. Once it is on, Stripe recommends turning on Error on Requires Action? and Off Session? too.
8

Create Price

Action

In Zapier“Creates a price.”

Attaches a price to a product. The amount goes in minor units: in US dollars, typing 100 charges $1.00, and 0 makes the price free.

When to use it
set up a new tier or a special rate right after the product exists.
Watch out
the currency must be a supported three-letter ISO code, and forgetting the minor units multiplies or divides the price by a hundred.
9

Create Product

Action

In Zapier“Creates a new product.”

Registers a new product in your Stripe catalogue, the thing a price will later be attached to.

When to use it
mirror a new offer created in your back office, so the Stripe catalogue never lags behind what sales are selling.
Watch out
a product alone cannot be sold. Pair it with Create Price.
10

Create Subscription

Action

In Zapier“Creates a new subscription.”

Signs an existing customer up to one or more prices, which starts recurring billing on their account.

When to use it
start the subscription once a contract is signed in another tool, without anyone retyping the plan.
Watch out
it needs a Customer ID and accepts up to 20 items. Picking the same item twice makes the step fail.
12

Update Customer

Action

In Zapier“Updates an existing customer.”

Changes an existing customer, identified by the Customer ID the step requires.

When to use it
push a corrected address or contact detail from your CRM back into Stripe so invoices go to the right place.
Watch out
the ID is mandatory, so a Zap that only knows an email needs Find Customer just before this step.
13

API Request (Beta)

Action

In Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”

An advanced escape hatch: a raw request to Stripe that reuses your connection, for anything the ready-made actions do not cover.

When to use it
reach a Stripe feature that has no action here, with someone technical at hand.
Watch out
it only calls Stripe's own domains, and Stop on error decides whether a Stripe error halts the Zap or lets it run on.
Searches

The 8 Stripe searches

8 search steps look for data that already exists in Stripe, so a later step can use it.

Searches sit at the bottom of the action list, under the SEARCH heading. They fetch something that already exists in Stripe so later steps can use it. Any search makes the Zap multi-step, so it needs a paid plan. None of the Stripe searches offers a find-or-create option, and each search has three settings worth knowing.

1

Find Account Balance

Search

In Zapier“Finds the account balance for your stripe account”

Reads the current balance of your Stripe account and hands the figures to the next steps.

When to use it
attach the balance to a weekly finance digest or a cash alert built in another tool.
Watch out
it reads your own account only, so it does not need any ID to work.
2

Find Account by ID

Search

In Zapier“Finds a Stripe account by its ID.”

Looks up a Stripe account from its account ID, the string that starts with acct_.

When to use it
fetch the details of an account whose ID an earlier step carries, before acting on it.
Watch out
the Account ID is required, so an earlier step has to carry it.
3

Find Balance Transactions

Search

In Zapier“Finds transactions that have contributed to the Stripe account balance, such as charges, transfers, and more.”

Returns the movements that made up your Stripe balance: charges, transfers and the like.

When to use it
reconcile what Stripe received with what your accounting tool expects, without exporting a report by hand.
Watch out
several transactions usually match, so set the multiple-results option to what your next step can actually handle.
4

Find Charge

Search

In Zapier“Finds an existing charge by its Stripe ID.”

Fetches one charge from its Stripe ID, the identifier that starts with ch_.

When to use it
enrich a dispute or a refund alert with the details of the original charge.
Watch out
the Stripe Charge ID is required. If your trigger only carries an email or an amount, this search has nothing to look up.
5

Find Customer

Search

In Zapier“Finds an existing customer by their Stripe ID or email address.”

Finds an existing customer either by Stripe ID or by email address.

When to use it
turn an email from a form or a CRM into the Customer ID that most Stripe actions demand.
Watch out
if nothing matches, the default stops the Zap there. Switch on Successful if no search results are found? to carry on without it.
6

Find Invoice

Search

In Zapier“Finds an existing invoice by its Stripe ID.”

Pulls one invoice from its Stripe ID, the identifier starting with in_.

When to use it
fetch the full invoice when a failed-payment alert only gives you its reference, so the person following up sees the amounts.
Watch out
the Invoice ID is required, and an invoice number typed by a human is not the same thing.
7

Find Payment

Search

In Zapier“Finds an existing payment intent by its Stripe ID.”

Retrieves one payment intent from its Stripe ID, which starts with pi_.

When to use it
check the state of a payment before confirming it with Confirm Payment, or show it in a support ticket.
Watch out
the Payment Intent ID is required and charge IDs do not work here.
8

Find Subscription

Search

In Zapier“Finds an existing subscription.”

Locates the subscription of a customer, identified by the Customer ID the step requires.

When to use it
get the subscription to cancel before Cancel Subscription, when your trigger only knows who the customer is.
Watch out
a customer with several subscriptions returns several matches, so decide which one the next step should take.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and skips the steps that depended on it. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create on apps that support it. No Stripe search offers it, so a missing customer has to be created by a separate step.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When it breaks

When a Stripe Zap breaks

Most Stripe Zaps that go wrong do so for one of the reasons below, and Zapier keeps help articles on the Stripe-specific ones.

Zapier keeps a help article on common problems with Stripe, plus dedicated ones on test mode data, payment links and the legacy ACH Direct Debit change. The cases below are the ones to check first, and the Zapier troubleshooting page covers the general method.

  • The past is not replayed

    A Zap only reacts to what happens after you publish it. Payments, customers or invoices that existed before are never picked up, and moving that history is a separate job.
  • The same sale arrives twice

    New Charge and New Payment can both describe one sale. Use one of them, or set Ignore payments intents to True on New Charge.
  • A Zap that triggers itself

    A Zap that writes where its own trigger watches, such as Create Customer behind New Customer, sets itself off again and again and burns through tasks fast.
  • A bulk import gets held back

    When a trigger suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold it back instead of running every item.
  • Test data versus live data

    Zapier has a dedicated help article on using test mode data with Stripe. Read it before building a Zap on test payments rather than live ones.
  • Polling triggers never double up

    On the five polling triggers, Zapier remembers what it has already seen, so the same invoice or refund does not start the Zap twice.
Need help

Need help automating Stripe with Zapier?

A person reads every message.

FAQ

Stripe Zapier integration: frequent questions

01Is the Stripe Zapier integration free?
Yes, Stripe is not a premium app, so it works on the free plan. That plan gives 100 tasks a month and unlimited Zaps, with one limit nobody mentions: each Zap has two steps only, one trigger and one action. As soon as you add a second action, a filter or a search such as Find Customer, the Zap becomes multi-step and needs a paid plan. Plenty of useful Stripe Zaps fit in two steps, like a new subscription posted to your team chat or a failed payment turned into a support ticket.
02How many tasks does a Stripe Zap use?
One per action that succeeds, and nothing for the trigger. A Zap where a failed payment updates a customer and then posts a message uses two tasks each time it runs. An action that fails is not counted. Checking Stripe for new items costs nothing either, however often Zapier looks. The thing to watch is volume: Updated Subscription fires on every change to a subscription and Updated Dispute on every update of a case, so the count can climb faster than the number of sales.
03Do Stripe triggers run in real time?
Most of them, yes. Eleven of the sixteen triggers are instant: Stripe tells Zapier the moment the event happens, whatever your plan. That covers payments, charges, customers, subscriptions, checkouts and disputes. The five others are polling triggers: New Event, New Invoice Item, New Invoice, New Payment Link and New Refund. Zapier checks those at an interval set by your plan, every 15 minutes on the free one, 2 on Professional and 1 on Team and Enterprise. An instant trigger shows a lightning bolt in the editor.
04What does it take to connect Stripe to Zapier?
A Stripe account, with access to the data the Zap will touch, and a Zapier account. From the Apps page, click + Add connection, search for Stripe, click Add connection, sign in to Stripe in the tab that opens and allow access. The connection is then reused by every Stripe step. Some options depend on your Stripe settings rather than on the connection: automatic tax on a payment link needs Automate taxes enabled first, and the terms checkbox needs a terms URL in your dashboard.
05Why does one Stripe payment start a Zap twice?
Usually because two triggers describe the same sale: New Charge and New Payment. New Charge carries a required setting called Ignore payments intents. Set to True, it skips charges related to a payment intent, and the setting itself is described as a way to prevent duplicates when New Payment runs too. So either keep only one of the two triggers, or switch that setting on in New Charge before you publish.
06What if the Stripe operation you need is not in the list?
Check New Event first on the trigger side, since it starts on any new event of your Stripe account, keeping in mind it is a polling trigger. On the action side, API Request (Beta) sends a raw request to Stripe through your existing connection, for features with no ready-made action. It needs someone comfortable with Stripe's API, and it can only call domains associated with Stripe. Its Stop on error setting decides whether a failed call halts the Zap.
07Zapier, Make or n8n for Stripe?
There is no single winner, only criteria. On Zapier, Stripe comes with 37 ready-made operations, 11 of its 16 triggers are instant, it works on the free plan, and every successful action is billed as a task, with multi-step Zaps on a paid plan. The questions to settle are whether those operations cover your case, whether two-step Zaps are enough, and which tool your team already runs and maintains. For a first alert, such as a failed payment posted to a team channel, the free plan is enough.