- Integrations
- /
- GitLab
- /
- Actions
- /
- List GitLab Projects
ActionGitLabUpdated May 2026
What GitLab projects can I access?
Short answer: Drop the "GitLab → List GitLab Projects" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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.
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
Other GitLab actions.
Action
Add GitLab Comment
Posts a comment on an issue, merge request, or commit. For AI-code-review bots or for cross-tool sync ("Linear status changed → comment on the linked MR").
ActionCreate GitLab Issue
Files an issue with title, description, labels, assignees, milestone. For "Sentry error → file repo issue" or "support ticket marked bug → create issue" workflows.
ActionCreate GitLab Merge Request
Opens a new MR from source branch to target branch with title, description, reviewers, labels. For automation that auto-creates MRs from generated branches (dependabot-style).
ActionGet GitLab Issue
Returns an issue by ID with all metadata. The standard lookup for cross-system sync workflows that need fresh issue state.
ActionGet GitLab Project
Returns project metadata — name, namespace, visibility, default branch, recent activity. Useful for project inventory workflows.
ActionList GitLab Branches
Returns the project's branches with last commit info. Useful for "find stale branches for cleanup" maintenance workflows.
Send list gitlab projects from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.