Skip to main content

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

Register now (opens in a new tab)
Assembly
Stripe

Connect Assembly and Stripe

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

Get started free

Create a custom workflow

Integrate Assembly 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.

Assembly
Trigger: Watch Activated Clients
Stripe
Action: Select an action
1. Select a trigger

  • Triggers when a client is activated in Copilot.

  • Triggers when a task is archived.

  • Triggers when a subscription is canceled.

  • Triggers when a form response is completed.

  • Triggers when a task is completed.

  • Triggers when a client is created in Copilot.

  • Triggers when a company is created.

  • Triggers when a file is created.

  • Triggers when a folder is created in the Files app.

  • Triggers when an internal user is created.

  • Triggers when an invoice is created.

  • Triggers when a link is created in the Files app.

  • Triggers when a message channel is created.

  • Triggers when a note is created.

  • Triggers when a notification has been sent to a client or internal user

  • Triggers when a price is created.

  • Triggers when a product is created.

  • Triggers when a subscription is created.

  • Triggers when a task is created.

  • Triggers when a client is deleted.

  • Triggers when a company is deleted.

  • Triggers when a file is deleted.

  • Triggers when a folder is deleted.

  • Triggers when an internal user is deleted.

  • Triggers when an invoice is deleted.

  • Triggers when a link is deleted from a file channel.

  • Triggers when a message channel is deleted.

  • Triggers when a note is deleted.

  • Triggers when a task is deleted.

  • Triggers when a payment fails.

  • Triggers when an invoice is paid.

  • Triggers when an internal user requests a contract signature from a client.

  • Triggers when an invoice is sent.

  • Triggers when a message is sent.

  • Triggers when a contract is signed.

  • Triggers when a payment is successful.

  • Triggers when a client custom field is updated.

  • Triggers when a client is updated.

  • Triggers when a company is updated.

  • Triggers when a company custom field is updated.

  • Triggers when a file has been renamed or moved within a file channel.

  • Triggers when a folder is renamed or moved.

  • Triggers when an invoice is updated.

  • Triggers when a link has been renamed or moved within a file channel.

  • Triggers when a note is updated.

  • Triggers when a product name or status is updated. Prices added to products will not trigger this module, for this use the Price Created trigger.

  • Triggers when a task is updated.

  • Triggers when an invoice is voided.

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 Assembly 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
Cancel a Subscription
Cancels a specific subscription. Status must be 'active' or 'not started'.
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
Creates a client in Copilot.
Action
Create a Company
Creates a new company.
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.