Get GitLab Issue: GitLab action

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.

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 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 Get GitLab Issue support batch operations?

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