Skip to main content

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

Register now (opens in a new tab)
GitLab
Stripe

Connect GitLab and Stripe

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

Get started free

Create a custom workflow

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

GitLab
Trigger: Watch Issue Notes
Stripe
Action: Select an action
1. Select a trigger

  • Triggers on note events.

  • Triggers when a new issue is created or an existing issue was updated/closed/reopened.

  • Triggers on status change of a job.

  • Triggers when a new merge request is created, an existing merge request was updated/merged/closed or a commit is added in the source branch.

  • Triggers on pipeline events.

  • Triggers when a new project is added of which the authenticated user is a member.

  • Triggers on push events.

  • Triggers on tag push events.

  • Triggers when a new todo is added. When no filter is applied, the trigger is run when a new pending todo is added.

  • Triggers when a wiki page is created or edited.

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 GitLab and Stripe.

Accept a Merge Request
Merges changes submitted with merge request.
Action
Cancel a Job
Cancels a single build of a project.
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 a Pipeline's Jobs
Cancels a pipeline's builds.
Action
Cancel Merge When Pipeline Succeeds
Cancels a merge request when the pipeline succeeds.
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
Cherry Pick a Commit
Cherry picks a commit to a given branch.
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.