ActionGitLabUpdated September 2026
How do I create a GitLab issue?
Short answer: You can create gitlab issue in GitLab by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the GitLab Create GitLab Issue action to a workflow, map its 7 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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.
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 run history shows the failed step with its input and the error message GitLab returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Create GitLab Issue support batch operations?
Run Create GitLab Issue inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within GitLab's rate limits.
More actions
Other GitLab actions.
Action
Add GitLab Comment
Posts a comment on an issue, merge request, or commit. For AI-code-review bots or for cross-tool sync ("Linear status changed → comment on the linked MR").
ActionCreate GitLab Merge Request
Opens a new MR from source branch to target branch with title, description, reviewers, labels. For automation that auto-creates MRs from generated branches (dependabot-style).
ActionGet GitLab Issue
Returns an issue by ID with all metadata. The standard lookup for cross-system sync workflows that need fresh issue state.
ActionGet GitLab Project
Returns project metadata — name, namespace, visibility, default branch, recent activity. Useful for project inventory workflows.
ActionList GitLab Branches
Returns the project's branches with last commit info. Useful for "find stale branches for cleanup" maintenance workflows.
ActionList GitLab Issues
Paginated issues with filters by state, label, assignee, milestone, date. For "open critical issues" dashboards or per-engineer queue rollups.