TriggerGitLabReal-timeUpdated June 2026

When does GitLab fire on merge requests?

Short answer: In TinyCommand, add the GitLab GitLab Merge Request trigger to a workflow and publish. It listens through a GitLab webhook and fires your workflow within seconds of the event, with no polling and no code. Add a filter if you only want some events to start a run.

Trigger workflows on GitLab Merge Request in GitLab — start free All 5 GitLab triggers

Trigger workflows on GitLab Merge Request in GitLab — start free

Anatomy

What this trigger looks like in a workflow.

Drop it on the canvas. Configure a couple of fields. Publish.

In the builder

Trigger

GitLab Merge Request

When the matching event happens

when a merge request is opened, updated, or merged in gnew merge requestwatch for merge requestwhen merge requeston merge request

What this trigger returns

for the curious

You don’t need to read this. TinyCommand auto-maps every field into the visual picker so downstream nodes can pull values by clicking. We show it here for power users who want to know what’s on the wire.

{
  "iid": 1,
  "url": "https://gitlab.com/group/my-project/-/merge_requests/1",
  "state": "opened",
  "title": "Add dark mode support",
  "action": "open",
  "author": "johndoe",
  "source_branch": "feature/dark-mode",
  "target_branch": "main"
}

Output shape

Fields available to downstream nodes.

Every field below can be referenced by name in any action or filter that comes after this trigger.

Field	Type	Example
iid	number	1
url	string	"https://gitlab.com/group/my-project/-/merge_requests/1"
state	string	"opened"
title	string	"Add dark mode support"
action	string	"open"
author	string	"johndoe"
source_branch	string	"feature/dark-mode"
target_branch	string	"main"

Pairs with

Drop these actions after GitLab Merge Request.

Add Labels to Message

Gmail · Email

Add Reaction

Slack · Communication

Add Sheet Tab

Google Sheets · Spreadsheets & Databases

Create Company

HubSpot · CRM & Sales

FAQ

Questions about GitLab Merge Request.

How does the GitLab Merge Request trigger work in GitLab?

Fires on MR events — opened, updated, closed, merged. The hook for "auto-assign reviewer", "post to review channel", "trigger downstream CI" workflows.

Is the GitLab Merge Request trigger real-time?

Yes. GitLab Merge Request uses webhooks or push subscriptions, not polling. Your workflow fires within seconds of the event happening in GitLab.

What data does GitLab Merge Request return?

The full event payload from GitLab. The output shape table on this page lists every field, its type, and an example value so you can map fields into downstream nodes.

Can I filter GitLab Merge Request so only some events start a workflow?

Yes. Add a Filter node right after the trigger and match on any field, whether that's subject, sender, status, or anything else in the payload. Workflows only continue when the filter passes.

Do I need GitLab admin permissions to use GitLab Merge Request?

For most GitLab accounts a standard user can authorize the trigger. Some GitLab plans require an admin to enable third-party webhooks. Check GitLab's docs if the trigger fails to register.