GitLab API

GitlabTool
Join our community

Actions1000

Overview

This node operation retrieves the list of pending members for a specific GitLab group using the GitLab API v4. It is useful for administrators or users managing group memberships who want to see which users have requested access but have not yet been approved. For example, it can be used to automate monitoring of pending membership requests in a GitLab group.

Use Case Examples

  1. Fetch pending members of a GitLab group to review and approve membership requests.
  2. Automate notifications or reports about pending group membership requests.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request.
Authentication The authentication method used for the API request, typically an API key credential.
baseUrl The 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 query parameters for pagination, including page number and items per page.
Path Parameters Path parameters required for the API endpoint, specifically the group ID to identify the group.

Output

JSON

  • id - The unique identifier of the pending member.
  • username - The username of the pending member.
  • name - The full name of the pending member.
  • state - The membership state, typically 'pending'.
  • access_level - The access level requested by the pending member.
  • created_at - Timestamp when the membership request was created.

Dependencies

  • GitLab API authentication token

Troubleshooting

  • Ensure the group ID provided in the path parameters is correct and exists in the GitLab instance.
  • Verify that the API authentication token has sufficient permissions to read group membership information.
  • Check the base URL to ensure it points to the correct GitLab instance, especially if using a self-hosted GitLab server.
  • If pagination parameters are used, ensure they are valid integers and within allowed ranges.

Links

Discussion