Skip to main content

Make Waves ’26 Step into AI’s glass box. Prague, 19–20 Oct.

Register now (opens in a new tab)
Arbox
Stripe

Connect Arbox and Stripe

Explore ready-made Arbox and Stripe templates and start automating in minutes.

Get started free

Create a custom workflow

Integrate Arbox with Stripe and automate the work that moves between them — no code required.

Create a custom workflow

Every automation starts with a trigger and an action. Select one from each app to generate a workflow tailored to your needs.

Arbox
Trigger: Watch Amount of Check ins
Stripe
Action: Select an action
1. Select a trigger

  • Triggers when a client has x amount of check-ins

  • Trigger when a client books a number of sessions

  • Triggers when a new appointment is booked

  • Triggers when an appointment is cancelled

  • Triggers when an appointment is updated

  • Triggers when membership is canceled

  • Instant trigger on a canceled membership

  • Triggers when an event is cancelled

  • Triggers when a user has to confirm entry from waiting list.

  • Instant trigger on when user has to confirm entry from waiting list.

  • Triggers when a recurring payment is refused.

  • Instant trigger on a credit refusal

  • Triggers when a user entered (access control)

  • Triggers when a user entered a session from a waiting list

  • Instant trigger on when a user entered a session from a waiting list

  • Triggers when a user is inactive

  • Triggers when a lead is converted to a new client

  • Triggers when a lead is marked as lost

  • Triggers when a user has/hasn't medical/waiver

  • triggers when a membership is suspended.

  • Triggers when a new client is added to Arbox

  • Triggers when a new lead is created in Arbox.

  • Triggers when an item is purchased from app/site

  • Instant trigger on a new purchase event

  • Triggers when a client renew or create membership

  • Triggers when a lead is booked to trial class

  • Instant trigger on a new trial class booking

  • Triggers when a lead status is updated

  • Triggers when a user cancels registration

2. Select an action

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

  • Cancels a previously created payout.

  • Capture the payment of an existing, uncaptured, charge.

  • Captures an existing uncaptured payment intent by its ID.

  • Confirms a payment intent by its ID. Upon confirmation, the payment intent will attempt to initiate a payment.

  • Creates a charge.

  • Creates a new customer object.

  • Creates a Payment Intent.

  • Creates a new payment link by line items.

  • To send funds to your own bank account, you create a new payout object.

  • Creates a new refund.

  • Creates a new invoice by the customer ID.

  • Creates a new invoice item to be added to a draft invoice.

  • Permanently deletes a customer. It cannot be undone.

  • Permanently deletes a draft invoice. Use "Void an Invoice" module for finalized invoice.

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

  • Finalizes a draft invoice by its ID.

  • Performs an arbitrary authorized API call.

  • Retrieves the balance transaction with the given ID.

  • Retrieves the details of a charge that has previously been created.

  • Retrieves the details of an existing customer.

  • Retrieves the details of a Payment Intent that has previously been created.

  • Retrieves the details of a payment link with the given ID.

  • Retrieves the details of an existing payout.

  • Retrieves the details of an existing refund.

  • Retrieves the details of an existing invoice with the given ID.

  • Retrieves the details of an existing invoice item with the given ID.

  • Retrieves the current account balance.

  • Updates the specified charge by setting the values of the parameters passed.

  • Updates the specified customer by setting the values of the parameters passed.

  • Updates the specified payment intent by setting the values of the parameters passed.

  • Updates a payment link by its ID.

  • Updates the specified payout by setting the values of the parameters passed.

  • Updates the specified refund by setting the values of the parameters passed.

  • Updates the specified invoice by setting the values of the parameters passed.

  • Updates the specified invoice item by setting the values of the parameters passed.

  • Voids a finalized invoice with the given ID. This cannot be undone.

Select a trigger and an action

Create workflow (opens in a new tab)

Triggers and actions

Explore what you can automate between Arbox and Stripe.

Book to a Trial Class
Book a lead to a trial class
Action
Cancel a Payment Intent
Cancels a payment intent by its ID. For payment intents with status ’requires_capture’, the remaining capturable amount will automatically be refunded.
Action
Cancel a Payout
Cancels a previously created payout.
Action
Cancel Trial Class Booking
Cancel a trial class booking
Action
Capture a Charge
Capture the payment of an existing, uncaptured, charge.
Action
Capture a Payment Intent
Captures an existing uncaptured payment intent by its ID.
Action
Confirm a Payment Intent
Confirms a payment intent by its ID. Upon confirmation, the payment intent will attempt to initiate a payment.
Action
Create a Charge
Creates a charge.
Action
Create a Client
Add new client to Arbox
Action
Load more

Support

FAQs

Everything you need to know about Make. Can't find the answer you're looking for? Please chat to our team.

Start by registering for Make. As a new Make user, you’ll automatically be assigned a free account. Once your account is set up, you can start creating your first scenarios. We recommend starting with our step-by-step video tutorial.

A scenario represents a workflow or a project of your own creation, and it is made up of a series of modules that automate apps and services. Creating a scenario allows you to transfer and transform data between apps and services via these modules to automate anything and improve the way you work.

Modules are the main building blocks of automation in Make. Modules represent actions that Make performs with an app, like creating, updating, or deleting data.

Mapping links the modules in your scenario. When you map an item, you connect the data retrieved by one module to another module to perform the desired action. For example, you can map email addresses and subject lines to create a spreadsheet using this data.