Get GitLab Project: 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 or group%2Fproject

Sample request

{
  "project_id": "e.g. 123 or group%2Fproject"
}

Returns

{
  "id": 123,
  "name": "My Project",
  "web_url": "https://gitlab.com/group/my-project",
  "star_count": 10,
  "visibility": "private",
  "description": "Our main application",
  "forks_count": 3,
  "default_branch": "main",
  "open_issues_count": 8,
  "path_with_namespace": "group/my-project"
}

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

FAQ

Questions about Get GitLab Project.

What does the Get GitLab Project action do in GitLab?

Returns project metadata — name, namespace, visibility, default branch, recent activity. Useful for project inventory workflows.

What inputs does Get GitLab Project 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 Get GitLab Project support batch operations?

Yes. Run Get GitLab Project 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