GitLab Extended icon

GitLab Extended

Extended GitLab node
Join our community

Actions66

Overview

The "GitLab Extended" node integrates with GitLab's API to manage various GitLab resources. Specifically, the Project - Get Many operation allows users to list multiple projects from a GitLab instance. This is useful for scenarios where you want to retrieve an overview of all accessible projects, filter projects by search terms, or automate workflows that depend on project metadata.

Practical examples include:

  • Fetching all projects in a GitLab instance to generate reports.
  • Searching projects by name or keyword to trigger downstream automation.
  • Integrating project lists into dashboards or other tools.

Properties

Name Meaning
Authentication Choose between using saved credentials ("Credential") or providing custom connection details ("Custom").
GitLab Server Base URL of your GitLab instance (e.g., https://gitlab.com). Used only if "Custom" authentication is selected.
Access Token Personal access token with API permissions. Used only if "Custom" authentication is selected.
Project Owner Namespace or owner of the project. Ignored if "Project ID" is set. Used only if "Custom" authentication is selected.
Project Name Project slug or name. Ignored if "Project ID" is set. Used only if "Custom" authentication is selected.
Project ID Numeric project ID. Takes precedence over owner and name if provided. Used only if "Custom" authentication is selected. Default is 0.
Resource The resource to work with; here it is fixed as "Project".
Operation The action to perform on the resource; here it is "Get Many" (list projects).
Return All Whether to return all results or limit the number of projects returned.
Limit Maximum number of projects to return if "Return All" is false.
Search Term Term to search for projects when using the "search" operation variant.

Note: For this specific operation, the relevant properties are mainly those controlling authentication, pagination (Return All and Limit), and optionally filtering via Search Term.

Output

The node outputs an array of JSON objects representing GitLab projects. Each object corresponds to a single project and contains its metadata as returned by the GitLab API. Typical fields include project ID, name, description, namespace, visibility, URLs, and other project-specific details.

The output does not include binary data.

Example output structure (simplified):

[
  {
    "id": 123,
    "name": "example-project",
    "description": "A sample GitLab project",
    "namespace": { "name": "group-name", "id": 45 },
    "visibility": "public",
    "web_url": "https://gitlab.com/group-name/example-project",
    ...
  },
  ...
]

Dependencies

  • Requires an API key credential with appropriate permissions to access GitLab projects.
  • Supports connecting to any GitLab instance by specifying the base URL and access token if using custom authentication.
  • Uses internal helper functions to handle API requests and pagination.

Troubleshooting

  • Invalid Credentials: If the node fails due to authentication errors, verify that the API token has sufficient permissions to read projects.
  • Project ID Validation: When specifying a project ID, it must be a positive number; otherwise, the node throws an error.
  • JSON Parsing Errors: Some parameters accept JSON input (not directly relevant for this operation but common in others); ensure valid JSON syntax.
  • API Rate Limits: Large queries may hit GitLab API rate limits; consider enabling pagination with limits.
  • Unknown Resource Error: If the resource parameter is incorrect or unsupported, the node will throw an error indicating an unknown resource.

Links and References

Discussion