GitLab API

GitlabTool

Actions1000

Overview

This node operation retrieves provisioned users of a specific GitLab group using the GitLab API. It is useful for scenarios where you need to manage or analyze users associated with a group, such as auditing group membership or filtering users based on criteria like username, activity status, or creation date.

Use Case Examples

  1. Fetch all provisioned users of a GitLab group by group ID.
  2. Filter provisioned users by username or search term within a group.
  3. Retrieve only active or blocked users in a group.
  4. Paginate through provisioned users with page and per_page parameters.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the API request.
baseUrl Base URL of the GitLab instance, defaulting to https://gitlab.com.
Method HTTP method to use for the request, default is GET.
Query Parameters Optional filters and pagination parameters for the request, including username, search, active, blocked, created_after, created_before, page, and per_page.
Path Parameters Path parameter specifying the group ID to retrieve provisioned users for.

Output

JSON

  • id - ID of the provisioned user.
  • username - Username of the provisioned user.
  • name - Name of the provisioned user.
  • state - State of the user (e.g., active, blocked).
  • created_at - Timestamp when the user was created.
  • access_level - Access level of the user in the group.

Dependencies

  • GitLab API authentication token or credentials

Troubleshooting

  • Ensure the group ID path parameter is provided and valid; missing or incorrect ID will cause errors.
  • Verify that the authentication token has sufficient permissions to access group user data.
  • Check that query parameters are correctly formatted, especially date-time strings for created_after and created_before.
  • If skipping authentication, ensure the GitLab instance allows unauthenticated access to this endpoint, otherwise requests will fail.

Links

Discussion