ActionGitLabUpdated September 2026

What branches exist in this GitLab project?

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

List GitLab Branches in GitLab — start free All 10 GitLab actions

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

Triggered by

Apps that pair well as the trigger for List GitLab Branches.

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 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 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 List GitLab Branches support batch operations?

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