GitLab API icon

GitLab API

Gitlab

Actions917

Overview

This node interacts with the GitLab API to retrieve details of a specific personal access token by its ID. It is useful for scenarios where you need to programmatically access or verify personal access tokens within a GitLab instance, such as auditing token usage or managing token lifecycle.

Use Case Examples

  1. Retrieve details of a personal access token by providing its ID to monitor token permissions and expiration.
  2. Automate token management workflows by fetching token information before performing actions that require authentication.

Properties

Name Meaning
Skip Authentication Option to bypass authentication for the request.
Authentication Type of authentication used for the request, defaulting to GitLab API key authentication.
baseUrl The base URL of the GitLab instance to which the API request is sent.
Method HTTP method used for the API request, defaulting to GET.
Path Parameters Collection of path parameters required for the API endpoint, specifically the 'id' of the personal access token to retrieve.

Output

JSON

  • id - The unique identifier of the personal access token.
  • name - The name assigned to the personal access token.
  • revoked - Indicates if the token has been revoked.
  • scopes - The scopes or permissions granted to the token.
  • created_at - Timestamp when the token was created.
  • expires_at - Expiration date of the token, if set.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the 'id' path parameter is correctly provided and is a valid integer representing an existing personal access token ID.
  • Verify that the GitLab API key credential has sufficient permissions to access personal access token information.
  • If authentication is skipped, the request may fail due to lack of authorization.
  • Check the baseUrl to ensure it points to the correct GitLab instance, especially if using a self-hosted GitLab server.

Links

Discussion