GitLab API icon

GitLab API

Gitlab

Actions917

Overview

This node interacts with the GitLab API to retrieve user information via the API v3 endpoint. It is useful for scenarios where you need to fetch details about the authenticated user from GitLab, such as in automation workflows that require user profile data or permissions verification.

Use Case Examples

  1. Fetching the current user's profile information from GitLab to personalize workflow actions.
  2. Retrieving user details to log or audit API usage within an automation process.

Properties

Name Meaning
Skip Authentication Determines whether to bypass authentication for the request.
Authentication Specifies the authentication method to use, defaulting to GitLab API key authentication.
baseUrl The base URL of the GitLab instance to which the API requests are sent.
Method The HTTP method used for the API request, defaulting to GET.
Parameter Schema Hidden property for the parameter schema of the getApiV3User operation.
Request Body Schema Hidden property for the request body schema of the getApiV3User operation.
Request Path The API path for the getApiV3User operation, set to /api/v3/user.

Output

JSON

  • id - The unique identifier of the user.
  • username - The username of the user.
  • email - The email address of the user.
  • name - The full name of the user.
  • state - The state of the user account (e.g., active, blocked).
  • avatar_url - URL to the user's avatar image.
  • web_url - URL to the user's GitLab profile page.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the GitLab API key credential is correctly configured and has sufficient permissions to access user information.
  • Verify the baseUrl is correct and accessible from the network where the node runs.
  • If skipping authentication, be aware that the API may reject the request or return limited information.
  • Common error messages include authentication failures (401 Unauthorized) and resource not found (404) if the API path is incorrect.

Links

Discussion