Skip to main content

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

Register now (opens in a new tab)
STEL Order
Stripe

Connect STEL Order and Stripe

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

Get started free

Create a custom workflow

Integrate STEL Order 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.

STEL Order
Trigger: Watch Clients
Stripe
Action: Select an action
1. Select a trigger

  • This trigger monitors and retrieves newly created or updated client records in STEL Order since the last run. It uses the UTC last modification date to fetch only recent changes, ensuring accurate and efficient synchronization of client data.

  • This trigger monitors and retrieves recently updated events in STEL Order since the last run. It utilizes the UTC last modification date to identify and fetch changes, ensuring accurate and efficient synchronization of updated event data.

  • This trigger periodically checks for incidents updated in STEL Order since the last run. It uses the UTC last modification date to fetch only recently updated records, ensuring efficient synchronization.

  • This module retrieves Ordinary Invoice Receipts from STEL Order. You can fetch individual receipts or a list, apply filters like amount, payment status, or date, and use sorting and pagination for better data management.

  • This trigger monitors and retrieves newly created or updated ordinary invoices in STEL Order since the last run. It ensures efficient synchronization by using the UTC last modification date to fetch only recent changes, helping you keep your invoice data accurate and up-to-date.

  • This trigger periodically checks for products updated in STEL Order since the last run. It uses the UTC last modification date to fetch only recently updated records, ensuring efficient synchronization.

  • This trigger monitors and retrieves newly created or updated sales delivery notes in STEL Order since the last run. It uses the UTC last modification date to fetch only recent changes, ensuring efficient synchronization of delivery notes and keeping your sales processes up-to-date.

  • This trigger periodically monitors and retrieves newly created or updated sales estimates in STEL Order since the last run. It ensures efficient synchronization by using the last modification date in UTC format to fetch only recent changes.

  • This trigger monitors and retrieves newly created or updated sales orders in STEL Order since the last run. It ensures efficient synchronization by using the UTC last modification date to fetch only recent changes, keeping your data accurate and up-to-date.

  • This trigger monitors and retrieves newly created or updated Work Estimates in STEL Order since the last run. It supports filtering by creation or last modification date (UTC), ensuring accurate and efficient synchronization of work estimate data.

  • This trigger monitors and retrieves newly created or updated Work Orders in STEL Order since the last run. It supports filtering by creation or last modification date (UTC), ensuring accurate and efficient synchronization of work estimate data.

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 STEL Order and Stripe.

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
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
This module allows you to create new clients in STEL Order using the provided API endpoint. It supports adding essential client details such as name, email, tax identification number, phone, and other optional attributes. Ideal for automating the client creation process as part of an integrated workflow.
Action
Create a Customer
Creates a new customer object.
Action
Create a Payment Intent
Creates a Payment Intent.
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.