Resources · Make integration

Stripe Make integrationAutomate Stripe with Make.

One payment lands, and the rest of the work can run itself. The Stripe Make integration hands you 41 ready-made bricks, called modules, for payments, customers, invoices and payouts. This page says what each one is for, then builds your first automation with you.

Try the Stripe integration on Make See the 41 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Stripe Make integration actually do?

It puts Stripe inside a scenario. A scenario is the automation you build in Make: a chain of modules that runs on a schedule, or when an app calls Make. Stripe brings 41 of those modules, so a payment, a customer record, an invoice or a payout stops being a screen you log into and becomes a step you can place, reorder and reuse.

Three shapes come back over and over. The first is billing that closes itself: Watch Events catches the event you picked in Stripe, Search Customers finds the right record, Create an Invoice opens the document and Finalize a Draft Invoice locks it. Nobody retypes a thing.

The second is refunds handled where the request lands. List All Refunds checks what already went back, Create a Refund sends the money, Retrieve a Refund confirms it left. For an online store, a support ticket turns into a refund without a detour through the dashboard.

The third is cash you can see. Retrieve Balance reads the account balance, List All Balance History brings back the movements behind it, and Create a Payout sends funds to your own bank account when someone decides to.

What Make will not do for you is anything outside the objects listed here. The 41 modules cover payment intents, customers, refunds, payouts, balance, invoices, invoice items and the lines of a payment link. Everything else in the Stripe API goes through Make an API Call, on the same connection. On the Free plan, 2 scenarios stay switched on at a time, which is enough to get a first one running.

Stripe also lives on the n8n side, so the choice is a real one: the Stripe n8n integration page covers that ground, and n8n vs Make lays out the criteria without crowning a winner. If you would rather learn the editor properly before wiring live payments, the Make training exists for that.

Connect

How do you connect Stripe to Make?

01
Add a Stripe module
Inside a scenario, click the +, search Stripe by name and pick any of its modules. The module asks for a connection, which is your Stripe account linked to Make once and reused afterwards by every other Stripe module. You need a Stripe account before you start.
02
Create the connection
Click Create a connection. Give it a name if you juggle several Stripe accounts, then authorize Make on the Stripe side, or paste the key Stripe gives you, depending on what the window asks for. The documentation lists no other prerequisite.
03
Save it and forget it
Click Save. The connection now shows up in the dropdown of every Stripe module, so the other 40 never ask you to log in again. When a module refuses to load its options, the connection is the first thing worth checking.

First scenario

Your first scenario, step by step

GoalWhen the Stripe event you picked happens, Make finds the customer and opens an invoice for them.

01
Create the scenario
From the Scenarios page, start a new scenario and click the + to drop in the first module. An empty canvas with a single circle on it is exactly what you should be looking at.
02
Put Watch Events in front
Search Stripe, pick Watch Events, create the connection if you have not yet, then choose the event this trigger should watch. The module carries an instant tag: Stripe calls Make the second the event happens.
03
Add the customer lookup
Click the + to the right of the trigger and add Search Customers. Map the data the trigger hands over into the criteria, so the search aims at one customer instead of the whole book.
04
Open the invoice
Add Create an Invoice behind the search and map the customer ID it returns. The invoice is created for that customer and waits for whatever the scenario adds next.
05
Test with Run once
Click Run once, the button that executes the scenario a single time, then make a real event happen in Stripe. Open each module and read the bundles it got, a bundle being one item passed to the next module.
06
Switch it on
An instant trigger has no interval to set: Stripe calls Make as soon as the event lands. Flip the scenario on and it stays on watch. Push one more real payment through before you trust it with the rest.

Triggers

What can start a Stripe scenario?

1 module starts a scenario when something happens in Stripe. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Stripe as soon as it happens.

Stripe1Watch Events

Watch Events

Instant trigger

In Make“Triggers when a given event occurs.”

Watch Events is the only module that starts a Stripe scenario on its own. It waits for the event you selected, then pushes it down the chain, so nothing runs until something happens on the account.

How it fires

instantly. Stripe calls Make through a webhook the moment the event occurs, which is why the module carries an instant tag next to its name.

When to use it

whenever a payment, a refund or an invoice change should set off work somewhere else, for an online store that ships once the money clears.

Watch out

Make creates and attaches the webhook while you set the trigger up, so there is nothing to paste into Stripe. Going to look for it is the classic first mistake.

Modules

Everything Stripe can do inside a scenario

Stripe gives you 40 modules in 9 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Universal

1 module

Stripe1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Whatever the other modules leave out, this one still reaches. It sends an authorized call to any endpoint of the Stripe API, on the connection you already made, and hands the answer back to the scenario.

When to use it

a Stripe object or option that none of the modules on this page covers.

Watch out

you write the call yourself, so there is no list of fields to pick from. Keep it for the gaps, not for the daily path.

Payment Intents

7 modules

Stripe2

List Payment Intents

In Make“Retrieves a list of payment intents or filters by customer ID.”

Pulls back your payment intents, either all of them or only those of one customer, and sends each one on as a separate bundle.

When to use it

you reconcile Stripe against your accounting and need the raw list, or a customer asks what they were charged for.

Watch out

a search can return none, one or many bundles, and each bundle costs one operation in the module that follows. An operation is one run of one module on one item, and it is what Make counts on your plan.

Stripe3

Create a Payment Intent

Action

In Make“Creates a Payment Intent.”

Opens a new payment intent in Stripe straight from the scenario, so an order taken somewhere else ends up as a real Stripe payment instead of a line in a spreadsheet.

When to use it

a quote accepted by email, or a form on your site that never goes through Stripe checkout.

Watch out

creating an intent is not the same as taking the money. Confirming it and capturing it are two other modules.

Stripe4

Retrieve a Payment Intent

Action

In Make“Retrieves the details of a Payment Intent that has previously been created.”

Fetches one payment intent by its ID and drops its details into the scenario.

When to use it

before acting on a payment, to read the state it is really in rather than assume it.

Watch out

nothing here changes the payment. The module only reads.

Stripe5

Confirm a Payment Intent

Action

In Make“Confirms a payment intent by its ID. Upon confirmation, the payment intent will attempt to initiate a payment.”

Confirmation is the step where Stripe tries to take the money. Give the module a payment intent ID and the payment is attempted.

When to use it

the customer details are in place and the scenario decides the charge should go through now.

Watch out

an attempt is an attempt. The module running is not proof the money arrived, so read the result before the next step depends on it.

Stripe6

Capture a Payment Intent

Action

In Make“Captures an existing uncaptured payment intent by its ID.”

An intent that was left uncaptured gets captured here, which is the moment the funds are collected.

When to use it

you authorize when the order is placed and only collect when the goods leave the shelf.

Watch out

it works on an uncaptured intent, so check the state with Retrieve a Payment Intent when the scenario is not the one that created it.

Stripe7

Update a Payment Intent

Action

In Make“Updates the specified payment intent by setting the values of the parameters passed.”

Changes an existing payment intent with the values you pass, leaving what you do not touch as it was.

When to use it

the order grew or shrank between the moment it was taken and the moment it gets paid.

Watch out

you need the ID of the intent, so the trigger or a search has to hand it over first.

Stripe8

Cancel a Payment Intent

Action

In Make“Cancels a payment intent by its ID. For payment intents with status ’requires_capture’, the remaining capturable amount will automatically be refunded.”

Closes the door on a payment intent, by its ID.

When to use it

an order pulled back before it was collected, or a duplicate created by a scenario that fired twice.

Watch out

on an intent sitting at requires_capture, Stripe refunds the remaining capturable amount by itself. Handy, as long as no later step expects to refund it again.

Customers

6 modules

Stripe9

Search Customers

In Make“Retrieves a list of customers filtered by criteria.”

Looks through your customers with the criteria you give it and returns the ones that match.

When to use it

an event arrives and you need the existing record before a second one gets created for the same person.

Watch out

a search can come back with several customers, or with none at all, so decide what the scenario does in both cases.

Stripe10

List All Customers

In Make“Retrieves a list of customers.”

No criteria, no filter: this one walks the whole customer list and pushes each record into the scenario.

When to use it

a one-off export, or a clean-up pass over an account you have just inherited.

Watch out

on a busy account that is a long queue of bundles, and every one of them keeps costing operations further down the chain.

Stripe11

Create a Customer

Action

In Make“Creates a new customer object.”

Adds a new customer record in Stripe with the details the scenario is carrying.

When to use it

a signup form or a CRM entry that should exist in Stripe before the first invoice goes out.

Watch out

nothing stops two runs from creating the same person twice. A Search Customers step in front is the usual guard.

Stripe12

Retrieve a Customer

Action

In Make“Retrieves the details of an existing customer.”

One customer, read by ID, with the details Stripe holds right now instead of the copy stored in your own tool.

When to use it

you already have the ID and want the current version before writing anything.

Watch out

this reads a single record. When you only know an attribute and not the ID, Search Customers is the module for it.

Stripe13

Update a Customer

Action

In Make“Updates the specified customer by setting the values of the parameters passed.”

Writes new values onto a customer who already exists in Stripe, leaving the rest of the record as it was.

When to use it

an address change or a billing detail corrected in your own tool that has no reason to stay wrong in Stripe.

Watch out

the customer ID has to reach this module, so a search or the trigger hands it over first.

Stripe14

Delete a Customer

Action

In Make“Permanently deletes a customer. It cannot be undone.”

Removes a customer from Stripe for good.

When to use it

a duplicate record, or a deletion request you have to honor.

Watch out

it cannot be undone. Put it behind a step that checks the ID twice, and never straight behind a search that might return more than one person.

Refunds

4 modules

Stripe15

List All Refunds

In Make“Returns a list of all refunds you’ve previously created.”

Brings back the refunds already created on the account, one bundle per refund.

When to use it

a check before money goes back out, so the same order is not refunded twice.

Watch out

like every search here, the answer can be empty, and an empty answer leaves the following steps with nothing to work on.

Stripe16

Create a Refund

Action

In Make“Creates a new refund.”

Issues a refund from inside the scenario, without anyone opening the Stripe dashboard.

When to use it

a support ticket closed with money back, or an order cancelled in your shop.

Watch out

money leaving is not a draft. Keep this module at the end of a path a human has already approved.

Stripe17

Retrieve a Refund

Action

In Make“Retrieves the details of an existing refund.”

Checks a single refund by its ID and reports the state it is in.

When to use it

a customer asks where the money went and you would rather answer from Stripe than from memory.

Watch out

one refund per run. For everything issued on the account, List All Refunds is the module to reach for.

Stripe18

Update a Refund

Action

In Make“Updates the specified refund by setting the values of the parameters passed.”

Sets new values on a refund that has already been issued.

When to use it

a correction your finance side decides on after the refund left, and that has to be written back onto the record.

Watch out

the refund ID is required, so a List All Refunds or Retrieve a Refund step usually runs just before.

Payouts

5 modules

Stripe19

List All Payouts

In Make“Returns a list of existing payouts sent to third-party bank accounts or that Stripe has sent you.”

Returns the payouts on the account, both those sent to outside bank accounts and those Stripe sent you.

When to use it

you reconcile what actually landed on the bank statement against what Stripe says it sent.

Watch out

it is a search, so expect a handful of bundles and narrow them down before anything gets written anywhere.

Stripe20

Create a Payout

Action

In Make“To send funds to your own bank account, you create a new payout object.”

Sends funds from the Stripe balance to your own bank account, on demand from the scenario.

When to use it

a transfer your finance side decides to make, started from a form or an approval rather than from the dashboard.

Watch out

real money moves out of Stripe here. The module belongs behind an approval step, not at the tail of a scenario anyone can set off.

Stripe21

Cancel a Payout

Action

In Make“Cancels a previously created payout.”

Stops a payout that was created earlier.

When to use it

a transfer fired with the wrong amount and someone catches it fast.

Watch out

it needs the payout ID, which means the scenario has to keep the one Create a Payout gave back.

Stripe22

Retrieve a Payout

Action

In Make“Retrieves the details of an existing payout.”

Where does one transfer stand? This module answers, from the payout ID, and drops the payout into the scenario.

When to use it

a quick check before telling the team, or the accountant, that the transfer is done.

Watch out

it reads and nothing more. Stopping a transfer is the job of Cancel a Payout.

Stripe23

Update a Payout

Action

In Make“Updates the specified payout by setting the values of the parameters passed.”

A payout already created can still take new values, and this is the module that writes them.

When to use it

your finance process adds information to a transfer after it was created.

Watch out

it changes the record inside Stripe and nothing at all in your own tools, which still need their own step.

Balance

3 modules

Stripe24

Retrieve Balance

Action

In Make“Retrieves the current account balance.”

Reads the current balance of the Stripe account and hands the figure to the scenario.

When to use it

a check before a payout, or a number posted to the team without anyone logging in.

Watch out

it is a snapshot taken when the module runs, not a history. For the movements behind the figure, the next module is the one you want.

Stripe25

List All Balance History

In Make“Returns a list of transactions that have contributed to the Stripe account balance.”

Every movement that built the current balance comes back here, one transaction per bundle.

When to use it

the accountant asks why the balance moved and you would rather send a list than a screenshot.

Watch out

on a busy account this returns a lot of bundles, and the whole chain behind it runs on each one.

Stripe26

Retrieve a Balance Transaction

Action

In Make“Retrieves the balance transaction with the given ID.”

Zooms in on a single balance transaction, by its ID.

When to use it

one line in the history looks odd and you want its detail inside the scenario.

Watch out

the ID is required, and it normally comes from List All Balance History running just before.

Invoices

8 modules

Stripe27

Search Invoices

In Make“Retrieves a list of invoices filtered by criteria.”

Finds invoices with the criteria you set and pushes the matches down the scenario.

When to use it

a chase over what is still open, or a pack of documents to hand over to the accountant.

Watch out

several invoices can match, so the steps after it run once per invoice.

Stripe28

List All Invoice Line Items

In Make“Retrieves a list of invoice line items by the invoice ID.”

Opens one invoice and returns its lines, one bundle per line.

When to use it

you need the detail of what was billed and not just the total, for an export or a check.

Watch out

it works from an invoice ID, so a Search Invoices or Retrieve an Invoice step has to come first.

Stripe29

Create an Invoice

Action

In Make“Creates a new invoice by the customer ID.”

Creates an invoice for a customer, from the customer ID the scenario is carrying.

When to use it

work delivered, a subscription handled outside Stripe, or anything your own tool decides should be billed.

Watch out

this module does not finalize anything. Invoice items attach to a draft and Finalize a Draft Invoice closes it, so plan the three steps together.

Stripe30

Retrieve an Invoice

Action

In Make“Retrieves the details of an existing invoice with the given ID.”

Gets one invoice by its ID and makes its content available to the next steps.

When to use it

a document mentioned in a ticket or on a bank line, when you want the Stripe version of it and not a copy.

Stripe31

Update an Invoice

Action

In Make“Updates the specified invoice by setting the values of the parameters passed.”

Corrects an invoice that is already in Stripe with the values you pass, and leaves alone whatever you do not set.

When to use it

something was wrong and it was caught before the document went out to the customer.

Watch out

the invoice ID is what the module works from, so Search Invoices often runs just before it.

Stripe32

Finalize a Draft Invoice

Action

In Make“Finalizes a draft invoice by its ID.”

Turns a draft into a finalized invoice, which is the version that counts.

When to use it

the lines are complete and the document is ready to exist officially.

Watch out

after this, Delete a Draft Invoice no longer applies. Void an Invoice becomes the only way back.

Stripe33

Void an Invoice

Action

In Make“Voids a finalized invoice with the given ID. This cannot be undone.”

Cancels a finalized invoice and leaves it in Stripe as void.

When to use it

a document issued by mistake, or an order cancelled once the invoice was already closed.

Watch out

it cannot be undone, and it is the route to take as soon as the invoice is finalized.

Stripe34

Delete a Draft Invoice

Action

In Make“Permanently deletes a draft invoice. Use "Void an Invoice" module for finalized invoice.”

Erases a draft invoice permanently.

When to use it

a draft left behind by a test run, or by a scenario that fired twice on the same order.

Watch out

drafts only. A finalized invoice goes through Void an Invoice instead, and neither move can be taken back.

Invoice Items

5 modules

Stripe35

Search Invoice Items

In Make“Retrieves a list of invoice items filtered by criteria.”

Searches the invoice items that match your criteria and returns them one by one.

When to use it

a look at what is waiting to be billed before a draft gets finalized.

Watch out

zero results is a normal answer here, not an error, so the scenario has to survive it.

Stripe36

Create an Invoice Item

Action

In Make“Creates a new invoice item to be added to a draft invoice.”

Adds a line to a draft invoice, which is how an invoice gets its content in the first place.

When to use it

each deliverable, each seat or each hour that has to show up on the document.

Watch out

the item attaches to a draft, so Create an Invoice comes first and Finalize a Draft Invoice comes last.

Stripe37

Retrieve an Invoice Item

Action

In Make“Retrieves the details of an existing invoice item with the given ID.”

Single invoice item, read by its ID, with everything it holds.

When to use it

one line queried by a customer, pulled back into the scenario without anyone opening Stripe.

Watch out

one item per run. To walk through the lines of a whole document, List All Invoice Line Items does that job.

Stripe38

Update an Invoice Item

Action

In Make“Updates the specified invoice item by setting the values of the parameters passed.”

Rewrites the values of an invoice item that is already there.

When to use it

a correction made while the invoice is still a draft.

Watch out

work on the lines, then finalize. The order of those two matters more than it looks.

Stripe39

Delete an Invoice Item

Action

In Make“Permanently deletes an invoice item which is not attached to invoices, or if it’s attached to a draft invoice.”

Takes an invoice item out for good, as long as no finalized invoice is holding it.

When to use it

a line added twice by a scenario that ran more than once.

Watch out

the deletion is permanent, and it only works on an item that is free or sitting on a draft.

Other

1 module

Stripe40

List Payment Link Lines

In Make“Retrieves all lines of the specified payment link.”

One payment link, all of its lines, handed to the scenario so it knows what that link actually sells.

When to use it

a link shared in a newsletter or a message, when you want the content of the order without retyping it.

Watch out

this is the only payment link module in the app. Anything else about links goes through Make an API Call.

Need help

Need help automating Stripe with Make?

A person reads every message.

FAQ

Questions that come up next

01Is the Stripe Make integration free?

Yes, from the Free plan. Stripe is a standard app in Make, so no upgrade is needed just to use it. The Free plan keeps 2 scenarios switched on at a time, holds scheduled runs to a minimum of 15 minutes between two executions, stops a run after 5 minutes, caps files at 5 MB and transfer at 512 MB. Paid plans bring the minimum down to 1 minute, lift the cap on active scenarios, allow 40 minutes of run time and count usage in credits, which Make also calls operations, each month. What Stripe charges you to process payments is a separate matter and does not change because a scenario runs.

02What do you need to connect Stripe to Make?

A Stripe account and one connection. Add any Stripe module to a scenario, click Create a connection, name it if you juggle several accounts, then authorize Make on the Stripe side or paste the key Stripe gives you, and save. The documentation lists no other prerequisite, no plan condition and no extra app to install. Once the connection is saved, all 41 modules reuse it, so you do this once and never again unless a second Stripe account joins the party. If a module stops loading its options later on, the connection is the first place to look.

03Does the Stripe trigger react in real time?

Yes. Watch Events is an instant trigger, which means Stripe calls Make through a webhook the moment the event happens, instead of Make checking at an interval the way a scheduled trigger does. Make creates that webhook and attaches it while you set the module up, so there is no address to copy into Stripe and nothing to poll. The catalogue holds exactly 1 trigger for Stripe and this is it, with the instant tag next to its name. Every other Stripe module is an action or a search, and those run when the scenario holding them runs.

04What if a Stripe module is missing?

Reach for Make an API Call. Stripe ships that universal module, so any endpoint of the Stripe API can be called from a scenario on the connection you already created, without waiting for a new module to appear in the catalogue. The 41 modules on this page cover payment intents, customers, refunds, payouts, balance, invoices, invoice items and payment link lines, which is most of what a finance workflow touches. For the rest you write the call yourself, and the Stripe API reference tells you what to send. It is more work than a ready-made module, so keep it for the gaps.

05Make or n8n for Stripe?

It depends on where your team already works, because Stripe exists on both sides and the app itself settles nothing. Make gives you these 41 modules, a visual editor and a count in operations, one per module run on one item. n8n comes at automation from another angle. If nobody around the table writes code and the finance side wants to read the scenario without a translator, Make is the easier one to defend. If n8n already runs everything else in the company, putting Stripe there costs less than introducing a second tool. The comparison page walks through the criteria one by one.

Hack'celeration Lab

Get our weekly automation tips.

No spam. Unsubscribe anytime.

Add a Stripe module

Create the connection

Save it and forget it

Create the scenario

Put Watch Events in front

Add the customer lookup

Open the invoice

Test with Run once

Switch it on

Need help automating Stripe with Make?

Get our weekly automation tips.