TriggerGitLabReal-timeUpdated June 2026

When does GitLab fire on new issues?

Short answer: Drop the "GitLab → GitLab Issue Created" 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.

Use this trigger All 5 GitLab triggers

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 Issue Created

When the matching event happens

new issue createdissue addedon issue createdwatch for issue createdwhen issue creatednew issuewhen a new issue is created on gitlab

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.

{
  "url": "https://gitlab.com/group/project/-/issues/1",
  "state": "opened",
  "title": "TC issue",
  "action": "open",
  "labels": [],
  "issue_id": 100,
  "author_id": 12345,
  "issue_iid": 1,
  "user_name": "Tester",
  "created_at": "2026-04-11T10:00:00Z",
  "event_type": "issue",
  "project_id": 67890,
  "updated_at": "2026-04-11T10:00:00Z",
  "description": "test",
  "object_kind": "issue",
  "assignee_ids": [],
  "milestone_id": null,
  "project_name": "TC Project",
  "project_path": "tc/project",
  "user_username": "tester"
}

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
url	string	"https://gitlab.com/group/project/-/issues/1"
state	string	"opened"
title	string	"TC issue"
action	string	"open"
labels	array	[]
issue_id	number	100
author_id	number	12345
issue_iid	number	1
user_name	string	"Tester"
created_at	string	"2026-04-11T10:00:00Z"
event_type	string	"issue"
project_id	number	67890
updated_at	string	"2026-04-11T10:00:00Z"
description	string	"test"
object_kind	string	"issue"
assignee_ids	array	[]
milestone_id	null	null
project_name	string	"TC Project"
project_path	string	"tc/project"
user_username	string	"tester"

Pairs with

Drop these actions after GitLab Issue Created.

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 Issue Created.

How does the GitLab Issue Created trigger work in GitLab?

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.

Is the GitLab Issue Created trigger real-time?

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

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

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.