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
Facebook Lead Ads

Connect GitLab and Facebook Lead Ads

Explore ready-made GitLab and Facebook Lead Ads templates and start automating in minutes.

Get started free

Create a custom workflow

Integrate GitLab with Facebook Lead Ads 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
Facebook Lead Ads
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

  • Returns information about the form.

  • Returns the information that the user filled in, in the lead generation form. Use this action after the New Lead trigger.

  • The action unsubscribes a selected page from the connection to Make.

Select a trigger and an action

Create workflow (opens in a new tab)

Triggers and actions

Explore what you can automate between GitLab and Facebook Lead Ads.

Accept a Merge Request
Merges changes submitted with merge request.
Action
Cancel a Job
Cancels a single build of a project.
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
Cherry Pick a Commit
Cherry picks a commit to a given branch.
Action
Create a File in a Repository
Creates a file in a repository.
Action
Create a Group
Creates a group.
Action
Create a Label
Creates a new label for the given repository with the given name and color.
Action
Create a Merge Request
Creates a new merge request.
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.