GitLab API

GitlabTool

Actions1000

Overview

This node operation retrieves packages associated with a specific group in GitLab using the GitLab API v4. It is useful for scenarios where you need to list or manage packages within a GitLab group, such as fetching package details for auditing, reporting, or integration with other systems.

Use Case Examples

  1. Fetch all packages for a GitLab group by specifying the group ID.
  2. Filter packages by type, name, or version within a group.
  3. Paginate through packages in a group to handle large sets of data.

Properties

Name Meaning
Skip Authentication Determines whether to skip authentication for the API request.
Authentication Specifies the authentication method to use, hidden unless Skip Authentication is false.
baseUrl The base URL of the GitLab instance to connect to, defaulting to https://gitlab.com.
Method HTTP method to use for the request, default is GET.
Parameter Schema Defines the parameters accepted by the API endpoint, including path and query parameters such as group ID, pagination, sorting, filtering by package type, name, version, and status.
Request Body Schema Schema for the request body, not used in this GET operation.
Request Path The API endpoint path template for retrieving group packages.
Query Parameters Collection of query parameters to filter and paginate the packages list, such as exclude_subgroups, page, per_page, order_by, sort, package_type, package_name, package_version, include_versionless, and status.
Path Parameters Collection of path parameters, specifically the group ID or URL-encoded path of the group.

Output

JSON

  • id - Unique identifier of the package.
  • name - Name of the package.
  • version - Version of the package.
  • type - Type of the package (e.g., maven, npm, conan).
  • status - Current status of the package (e.g., default, hidden, processing).
  • created_at - Timestamp when the package was created.
  • project_path - Path of the project associated with the package.

Dependencies

  • GitLab API authentication token or credentials

Troubleshooting

  • Ensure the group ID provided in the path parameters is correct and accessible with the authenticated user.
  • Verify that the base URL is correct and reachable.
  • Check that the authentication token has sufficient permissions to access group packages.
  • Common error messages include 401 Unauthorized (authentication issues), 404 Not Found (invalid group ID), and 400 Bad Request (invalid query parameters).
  • If pagination parameters are used, ensure they are within valid ranges to avoid empty responses.

Links

Discussion