GitLab API

GitlabTool
Join our community

Actions905

Overview

This node operation retrieves packages associated with a specific GitLab group using the GitLab API v4. It is useful for scenarios where you need to list or filter packages within a group, such as managing dependencies, auditing package usage, or integrating package data into workflows. For example, you can fetch all npm packages in a group or get packages filtered by creation date or status.

Use Case Examples

  1. Fetch all packages for a group by its ID.
  2. Retrieve only npm packages from a group.
  3. Get packages ordered by creation date in ascending order.

Properties

Name Meaning
Skip Authentication Determines whether to skip authentication for the API request.
Authentication Specifies the authentication method to use, typically an API key credential for GitLab.
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 for the API call including path and query parameters such as group ID, pagination, sorting, filtering by package type, name, version, and status.
Query Parameters Collection of optional query parameters to filter and paginate the package list, including exclude_subgroups, page, per_page, order_by, sort, package_type, package_name, package_version, include_versionless, and status.
Path Parameters Path parameter specifying the group ID or URL-encoded path to identify the group whose packages are being retrieved.

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., npm, maven).
  • status - Current status of the package (e.g., default, hidden).
  • created_at - Timestamp when the package was created.
  • project_path - Path of the project associated with the package.

Dependencies

  • GitLab API authentication credential

Troubleshooting

  • Ensure the group ID path parameter is correctly provided and URL-encoded if necessary.
  • Verify that the authentication credentials are valid and have sufficient permissions to access group packages.
  • Check that query parameters like page and per_page are within acceptable ranges to avoid pagination errors.
  • If the API returns errors related to package filtering, confirm that the package_type, status, and other filters use valid values as per the API documentation.

Links

Discussion