List GitLab Branches: 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
Search search	string	Optional	Filter branches by name
Per Page per_page	string	Optional	Per Page. e.g. "20"

Sample request

{
  "project_id": "e.g. 123",
  "search": "e.g. feature/",
  "per_page": "20"
}

Returns

[
  {
    "name": "main",
    "commit": {
      "id": "abc123",
      "title": "Initial commit",
      "short_id": "abc123"
    },
    "default": true,
    "web_url": "https://gitlab.com/group/project/-/tree/main",
    "protected": true
  }
]

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

FAQ

Questions about List GitLab Branches.

What does the List GitLab Branches action do in GitLab?

Returns the project's branches with last commit info. Useful for "find stale branches for cleanup" maintenance workflows.

What inputs does List GitLab Branches require?

Required: Project ID or Path. 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 Branches support batch operations?

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