GitLab Push: GitLab trigger

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 Push

When the matching event happens

new push eventwhen code is pushed to a gitlab repositorywhen push eventon push eventwatch for push event

What this trigger returns

for the curious

You don’t need to read this. Tiny Command 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.

{
  "ref": "refs/heads/main",
  "user": "johndoe",
  "project": "group/my-project",
  "commits_count": 1,
  "head_commit_message": "Fix authentication middleware"
}

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
ref	string	"refs/heads/main"
user	string	"johndoe"
project	string	"group/my-project"
commits_count	number	1
head_commit_message	string	"Fix authentication middleware"

FAQ

Questions about GitLab Push.

How does the GitLab Push trigger work in GitLab?

Fires on commit pushes to any branch (or filtered). Payload includes commits with messages and authors. For commit-message-based automation or for custom CI triggers.

Is the GitLab Push trigger real-time?

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

What data does GitLab Push 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 Push 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 Push?

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.

More triggers

Other GitLab triggers.

Trigger

GitLab Issue Created

Fires when a new issue is created in a GitLab project. Payload includes title, description, labels, assignees. Useful for "auto-route to team channel based on labels" or "create cross-tracker copy" sync workflows.

Trigger

GitLab Merge Request

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

Trigger

GitLab Pipeline Completed

Fires when a CI/CD pipeline completes with final status (passed, failed, canceled). For "post deploy result to engineering Slack" or "alert on consecutive failures" workflows.

Trigger

GitLab Tag Pushed

Fires when a new tag is pushed. Useful for release-management workflows that fire on version tags (e.g., "v1.2.3 pushed → trigger production deploy").

When does GitLab fire on commits?

What this trigger looks like in a workflow.

Fields available to downstream nodes.

Drop these actions after GitLab Push.

Questions about GitLab Push.

Other GitLab triggers.

Build a workflow on this trigger.