GitLab API icon

GitLab API

Gitlab

Actions917

Overview

This node operation retrieves access tokens for a specific group in GitLab using the GitLab API v4. It is useful for scenarios where you need to manage or audit group access tokens, such as checking which tokens are active or inactive for security or administrative purposes. For example, an admin can use this node to list all active access tokens for a group to ensure only authorized tokens are in use.

Use Case Examples

  1. Retrieve all access tokens for a group by specifying the group's ID or URL-encoded path.
  2. Filter access tokens by their state (active or inactive) to manage token lifecycle.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request, useful for testing or public endpoints.
Authentication Type of authentication used, here it is GitLab API authentication.
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 query parameters to filter the request, such as filtering tokens by their state (active or inactive).
Path Parameters Path parameters required for the request, specifically the group ID or URL-encoded path to identify the group.

Output

JSON

  • access_tokens - List of access tokens for the specified group, including details such as token state and permissions.

Dependencies

  • GitLab API credentials for authentication

Troubleshooting

  • Ensure the group ID or URL-encoded path is correctly specified; otherwise, the API will return an error.
  • If authentication is skipped, the request may fail if the endpoint requires authentication.
  • Check that the base URL is correct for your GitLab instance, especially if using a self-hosted GitLab server.
  • Common error messages include 401 Unauthorized (authentication issues) and 404 Not Found (invalid group ID).

Links

Discussion