GitLab API icon

GitLab API

Gitlab

Actions917

Overview

This node operation retrieves a list of projects associated with a specific user in GitLab by calling the GitLab API endpoint `/api/v4/users/{user_id}/projects`. It supports various query parameters to filter, sort, and paginate the projects, such as ordering by creation date, filtering by visibility, archived status, and more. This operation is useful for automating workflows that require fetching user project data from GitLab, for example, to analyze project statistics, manage project memberships, or integrate project information into other systems.

Use Case Examples

  1. Fetch all projects owned by a specific GitLab user to generate a report on their activity.
  2. Retrieve public projects of a user sorted by last activity date for monitoring recent work.
  3. Get projects with enabled issues and merge requests features for project management automation.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the API request.
Authentication The authentication method used for the API request, defaulting to GitLab API key authentication.
baseUrl The base URL of the GitLab instance to connect to, defaulting to https://gitlab.com.
Method The HTTP method to use for the API request, defaulting to GET.
Parameter Schema Defines the parameters accepted by the API endpoint, including path and query parameters for filtering and sorting projects.
Query Parameters Collection of optional query parameters to filter, sort, and paginate the list of projects, such as order_by, sort, archived, visibility, search, owned, starred, membership, and more.
Path Parameters Path parameter specifying the user ID or username whose projects are to be retrieved.

Output

JSON

  • projects - Array of project objects returned from the GitLab API, each containing project details such as ID, name, visibility, statistics, and other metadata.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the user_id path parameter is correctly set and corresponds to an existing GitLab user.
  • Verify that the API key credential has sufficient permissions to access the user's projects, especially for private or internal projects.
  • Check the baseUrl if connecting to a self-hosted GitLab instance to ensure it is correct.
  • If filtering by certain query parameters, ensure the values are valid and supported by the GitLab API to avoid errors.

Links

Discussion