List GitLab Projects: 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
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.

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

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