ActionGitLabUpdated September 2026

How do I fetch a GitLab issue?

Short answer: You can get gitlab issue in GitLab by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the GitLab Get GitLab Issue action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Get GitLab Issue in GitLab — start free All 10 GitLab actions

Get GitLab Issue in GitLab — start free

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	Project ID or Path. Example: 123
Issue IID issue_iid	string	Required	The project-specific issue number

Sample request

{
  "project_id": "e.g. 123",
  "issue_iid": "e.g. 42"
}

Returns

{
  "id": 1,
  "iid": 42,
  "state": "opened",
  "title": "Fix CI",
  "labels": [
    "bug"
  ],
  "web_url": "https://gitlab.com/group/project/-/issues/42",
  "assignees": [
    {
      "username": "johndoe"
    }
  ]
}

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

Triggered by

Apps that pair well as the trigger for Get 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 Get GitLab Issue.

What does the Get GitLab Issue action do in GitLab?

Returns an issue by ID with all metadata. The standard lookup for cross-system sync workflows that need fresh issue state.

What inputs does Get GitLab Issue require?

Required: Project ID or Path, Issue IID. 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 Get GitLab Issue support batch operations?

Run Get 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