ActionGitLabUpdated September 2026

What GitLab projects can I access?

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

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

List GitLab Projects 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
Membership membership	options	Optional	Membership. Options: Member projects only, All visible
Search search	string	Optional	Search. Example: my-project
Per Page per_page	string	Optional	Per Page. e.g. "20"
Order By order_by	options	Optional	Order By. Options: Last Activity, Name, Created

Sample request

{
  "membership": "{{trigger.membership}}",
  "search": "e.g. my-project",
  "per_page": "20",
  "order_by": "{{trigger.order_by}}"
}

Returns

[
  {
    "id": 123,
    "name": "My Project",
    "web_url": "https://gitlab.com/group/my-project",
    "default_branch": "main",
    "path_with_namespace": "group/my-project"
  }
]

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

Triggered by

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

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 Projects.

What does the List GitLab Projects action do in GitLab?

Returns paginated projects in the namespace or accessible to the user. Useful for cross-project automation and for project inventory workflows.

What inputs does List GitLab Projects require?

List GitLab Projects has no required inputs. Sensible defaults are applied if you leave fields blank.

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 Projects support batch operations?

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