ActionGitLabUpdated May 2026

How do I create a GitLab issue?

Short answer: Drop the "GitLab → Create GitLab Issue" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 10 GitLab actions

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Project ID or Path project_id	string	Required	Numeric ID or URL-encoded path (e.g. 'group%2Fproject')
Title title	string	Required	Title. Example: Fix CI pipeline timeout
Description description	string	Optional	Supports GitLab-flavored Markdown
Assignee IDs assignee_ids	string	Optional	Comma-separated user IDs
Labels labels	string	Optional	Comma-separated label names
Milestone ID milestone_id	string	Optional	Milestone ID. Example: 7
Due Date due_date	string	Optional	Due Date. e.g. "YYYY-MM-DD"

Sample request

{
  "project_id": "e.g. 123 or my-group%2Fmy-project",
  "title": "e.g. Fix CI pipeline timeout",
  "description": "{{trigger.description}}",
  "assignee_ids": "e.g. 5, 12",
  "labels": "e.g. bug, P1"
}

Returns

{
  "id": 1,
  "iid": 42,
  "state": "opened",
  "title": "Fix CI pipeline timeout",
  "web_url": "https://gitlab.com/group/project/-/issues/42"
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Create GitLab Issue.

Any of these apps can fire this action as part of a workflow.

Google Sheets → GitLab

2 Google Sheets triggers

HubSpot → GitLab

18 HubSpot triggers

FAQ

Questions about Create GitLab Issue.

What does the Create GitLab Issue action do in GitLab?

Files an issue with title, description, labels, assignees, milestone. For "Sentry error → file repo issue" or "support ticket marked bug → create issue" workflows.

What inputs does Create GitLab Issue require?

Required: Project ID or Path, Title. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if GitLab returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Create GitLab Issue support batch operations?

Yes. Run Create GitLab Issue inside a Loop node to process arrays. Tiny Command handles GitLab's rate limits automatically so you don't have to throttle manually.

More actions