GitLab API icon

GitLab API

Gitlab
Join our community

Actions917

Overview

This node interacts with the GitLab API to retrieve detailed membership information for a specific user within a specified group. It is particularly useful for scenarios where you need to verify or audit user memberships across GitLab groups, such as in access control management or user activity tracking.

Use Case Examples

  1. Retrieve membership details of a user in a GitLab group to check their access level.
  2. Audit all members of a GitLab group by iterating over user IDs and fetching their membership details.

Properties

Name Meaning
Skip Authentication Option to bypass authentication for the request, useful for public or unauthenticated endpoints.
Authentication Selects the authentication method, defaulting to GitLab API key authentication.
baseUrl The base URL of the GitLab instance to which the API requests are sent, defaulting to https://gitlab.com.
Method HTTP method used for the API request, defaulting to GET.
Parameter Schema Defines the required path parameters for the API call: group ID and user ID of the member.
Request Body Schema Schema for the request body, not used in this GET operation.
Request Path The API endpoint path template used for the request, with placeholders for group ID and user ID.
Path Parameters Collection of path parameters including 'id' for the group ID and 'user_id' for the member's user ID, required to construct the API request URL.

Output

JSON

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

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the group ID and user ID are correctly provided and exist in the GitLab instance to avoid 404 errors.
  • Authentication errors may occur if the API key is missing, invalid, or lacks sufficient permissions; verify the API key and its scopes.
  • Network or base URL misconfiguration can lead to connection failures; confirm the baseUrl is correct and accessible.

Links

Discussion