TriggerGitLabReal-timeUpdated May 2026
When does GitLab fire on git tags?
Short answer: Drop the "GitLab → GitLab Tag Pushed" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in GitLab, not on a polling schedule.
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 Tag Pushed
When the matching event happens
watch for tag pushedwhen tag pushedon tag pushednew tag pushedwhen a tag is pushed to a gitlab repository
What this trigger returns
for the curiousYou 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.
{"tag": "v1.0.0","author": "developer","project": "group/project"}
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 |
|---|---|---|
| tag | string | "v1.0.0" |
| author | string | "developer" |
| project | string | "group/project" |
Pairs with
Drop these actions after GitLab Tag Pushed.
FAQ
Questions about GitLab Tag Pushed.
How does the GitLab Tag Pushed trigger work in GitLab?
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").
Is the GitLab Tag Pushed trigger real-time?
Yes. GitLab Tag Pushed uses webhooks or push subscriptions, not polling. Your workflow fires within seconds of the event happening in GitLab.
What data does GitLab Tag Pushed 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 Tag Pushed 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 Tag Pushed?
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.
TriggerGitLab Merge Request
Fires on MR events — opened, updated, closed, merged. The hook for "auto-assign reviewer", "post to review channel", "trigger downstream CI" workflows.
TriggerGitLab 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.
TriggerGitLab Push
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.
Build a workflow on this trigger.
One trigger. 10+ downstream actions. Zero glue.
