GitLab API

GitlabTool
Join our community

Actions1000

Overview

This node operation retrieves members of a specific GitLab group using the GitLab API v4. It is useful for scenarios where you need to list or search for members within a group, filter members by user IDs, exclude certain users, or get additional seat and identity information. For example, it can be used to manage group memberships, audit group access, or integrate group member data into other workflows.

Use Case Examples

  1. Retrieve all members of a GitLab group by specifying the group ID.
  2. Search for members in a group using a query string to filter results.
  3. Get membership details for specific user IDs within a group.
  4. Exclude certain users from the membership list by specifying their user IDs.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the API request (boolean). Defaults to false.
Authentication The authentication method used for the API request, hidden unless Skip Authentication is false.
baseUrl The base URL of the GitLab instance to send the API request to. Defaults to https://gitlab.com.
Method The HTTP method to use for the API request. Defaults to GET.
Query Parameters Collection of optional query parameters to filter or paginate the members list.
Path Parameters Collection of path parameters including the group ID to specify which group's members to retrieve.

Output

JSON

  • id - The unique identifier of the member.
  • username - The username of the member.
  • name - The full name of the member.
  • state - The state of the member (e.g., active, blocked).
  • access_level - The access level of the member within the group.
  • expires_at - The expiration date of the member's access, if any.

Dependencies

  • GitLab API authentication

Troubleshooting

  • Ensure the group ID path parameter is correctly set; missing or incorrect ID will cause errors.
  • Verify authentication credentials if not skipping authentication; invalid or expired tokens will result in authorization errors.
  • Check query parameter formats, especially arrays like user_ids and skip_users, to avoid malformed requests.
  • Pagination parameters (page, per_page) should be valid integers to avoid unexpected results or errors.

Links

Discussion