GitLab API

GitlabTool
Join our community

Actions905

Overview

This node operation retrieves a list of projects associated with a specific user from the GitLab API (version 4). It is useful for scenarios where you need to fetch projects owned by or accessible to a particular user, such as for project management, reporting, or integration with other tools. For example, you can use it to get all projects a user has access to, filter projects by visibility or activity, or sort projects by creation date.

Use Case Examples

  1. Fetch all projects for a user with ID '123' ordered by creation date.
  2. Retrieve only public projects owned by a user, sorted in descending order.
  3. Get projects with enabled issues and merge requests features for a specific user.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the request (boolean). Defaults to false.
Authentication Type of authentication used, hidden unless Skip Authentication is false. Defaults to GitLab API key authentication.
baseUrl 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 parameter 'user_id' (required) and various optional query parameters for filtering, sorting, and pagination.
Query Parameters Collection of optional query parameters to filter and customize the projects list, such as order_by, sort, archived, visibility, search, owned, starred, membership, and pagination options.
Path Parameters Path parameter 'user_id' specifying the ID or username of the user whose projects are being retrieved.

Output

JSON

  • id - Unique identifier of the project.
  • name - Name of the project.
  • path - Path of the project repository.
  • url - URL to access the project.
  • visibility - Visibility level of the project (private, internal, public).
  • archived - Boolean indicating if the project is archived.
  • last_activity_at - Timestamp of the last activity in the project.
  • statistics - Optional project statistics if requested.
  • custom_attributes - Optional custom attributes included in the response.

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the 'user_id' path parameter is correctly set; missing or incorrect user ID will cause errors.
  • Verify that the API key credential is valid and has sufficient permissions to access the user's projects.
  • Check the baseUrl if connecting to a self-hosted GitLab instance; incorrect URL will cause connection failures.
  • If filtering by parameters like visibility or archived status, ensure values are valid as per the API documentation.
  • Pagination parameters (page, per_page) should be set correctly to avoid incomplete data retrieval.

Links

Discussion