GitLab API

GitlabTool
Join our community

Actions1000

Overview

This node operation retrieves the personal access tokens of the authenticated user from the GitLab API. It is useful for scenarios where a user needs to programmatically access or manage their own personal access tokens, such as for automation or integration purposes.

Use Case Examples

  1. A developer wants to fetch their current personal access tokens to verify their scopes and expiration dates.
  2. An automation workflow needs to check the validity of the user's personal access tokens before performing further GitLab API operations.

Properties

Name Meaning
Skip Authentication If set to true, the node will skip using authentication for the request.
Authentication Specifies the authentication method to use, defaulting to GitLab API authentication. Hidden if Skip Authentication is true.
baseUrl The base URL of the GitLab instance to which the API request is sent, defaulting to https://gitlab.com.
Method The HTTP method used for the API request, defaulting to GET.

Output

JSON

  • id - The unique identifier of the personal access token.
  • name - The name of the personal access token.
  • scopes - The scopes or permissions granted by the personal access token.
  • expires_at - The expiration date of the personal access token.
  • created_at - The creation date of the personal access token.

Dependencies

  • GitLab API authentication credential

Troubleshooting

  • Ensure the GitLab API authentication credential is correctly configured and has the necessary permissions to access personal access tokens.
  • If the request fails, verify the baseUrl is correct and accessible.
  • Check that the HTTP method is set to GET as required by this operation.
  • Common error messages may include authentication errors (e.g., 401 Unauthorized) or permission errors (e.g., 403 Forbidden). Resolving these typically involves updating credentials or permissions.

Links

Discussion