List GitLab Pipelines: 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 project_id	string	Required	Project ID. Example: 123
Branch/Tag ref	string	Optional	Branch/Tag. Example: main
Status status	options	Optional	Status. Options: All, Running, Pending, Success, Failed, Canceled
Per Page per_page	string	Optional	Per Page. e.g. "20"

Sample request

{
  "project_id": "e.g. 123",
  "ref": "e.g. main",
  "status": "{{trigger.status}}",
  "per_page": "20"
}

Returns

[
  {
    "id": 789,
    "ref": "main",
    "sha": "abc123",
    "status": "success",
    "web_url": "https://gitlab.com/group/project/-/pipelines/789",
    "created_at": "2025-01-15T12:00:00Z"
  }
]

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

FAQ

Questions about List GitLab Pipelines.

What does the List GitLab Pipelines action do in GitLab?

Paginated pipelines with status and ref filters. For "deploy history this week" reports or for CI-health monitoring workflows.

What inputs does List GitLab Pipelines require?

Required: Project ID. 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 List GitLab Pipelines support batch operations?

Yes. Run List GitLab Pipelines 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