Skip to main content

Make Waves ’26. Find out everything we’ve announced to build a more transparent future for AI agents in business

Read now (opens in a new tab)
GitLab
MOCO

Connect GitLab and MOCO integrations

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

Get started free

Create a custom workflow

Integrate GitLab with MOCO 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
MOCO
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

  • Creates a new comment.

  • Creates a new company.

  • Creates a new contact.

  • Creates a new lead.

  • Creates a new presence.

  • Creates a new project.

  • Creates a new project expense.

  • Creates a new purchase.

  • Creates a new task on the selected project.

  • Creates a new user.

  • Creates a new invoice.

  • Creates a new invoice payment.

  • Deletes the selected comment.

  • Deletes the selected presence.

  • Deletes an existing project expense. Deletions are only possible if this entry is not yet billed.

  • Deletes an existing project task. Deleting a task on a project is only possible as long as no hours were tracked on this task.

  • Deletes the selected purchase. It's possible only if the status is pending and no payments have been registered.

  • Deletes the selected user. Deleting a staff member is only possible if no hours are billed already.

  • Deletes the selected invoice payment.

  • Returns information about the selected comment.

  • Returns information about the selected company.

  • Returns information about the selected contact.

  • Returns information about the selected lead.

  • Returns information about the selected presence.

  • Returns information about the selected project.

  • Returns information about the selected project expense.

  • Returns information about the selected project task.

  • Returns information about the selected purchase.

  • Returns information about the selected purchase category.

  • Returns information about the selected user.

  • Returns information about the selected invoice.

  • Returns information about the selected invoice payment.

  • Returns a PDF of an invoice.

  • Performs an arbitrary authorized API call.

  • Updates the selected comment.

  • Updates the selected company.

  • Updates the selected contact.

  • Updates the selected lead.

  • Updates the selected presence.

  • Updates the selected project.

  • Updates the selected project expense. Updates are only possible if this entry is not yet billed.

  • Updates the selected project task.

  • Updates status of the selected purchase.

  • Updates the selected user.

  • Updates the selected invoice payment.

  • Updates status of the selected invoice.

Select a trigger and an action

Create workflow (opens in a new tab)

Triggers and actions

Explore what you can automate between GitLab and MOCO.

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 Comment
Creates a new comment.
Action
Create a Company
Creates a new company.
Action
Create a Contact
Creates a new contact.
Action
Create a File in a Repository
Creates a file in a repository.
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.