GitLab API

GitlabTool

Actions905

Overview

This node interacts with the GitLab API to retrieve the current user's status via the API v4 endpoint `/api/v4/user/status`. It is useful for workflows that need to check or monitor the status of the authenticated GitLab user, such as verifying user availability or presence information.

Use Case Examples

  1. A workflow that triggers actions based on the user's GitLab status, e.g., sending notifications if the user is marked as 'away'.
  2. An automation that logs or audits user status changes in GitLab for compliance or monitoring purposes.

Properties

Name Meaning
Skip Authentication If set to true, the node will skip using authentication for the request.
Authentication The authentication method 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, defaulting to https://gitlab.com.
Method The HTTP method used for the API request, defaulting to GET.
Parameter Schema Hidden property for the parameter schema of the operation, not user-configurable.
Request Body Schema Hidden property for the request body schema of the operation, not user-configurable.
Request Path The API endpoint path for the operation, fixed to `/api/v4/user/status`.

Output

JSON

  • status - The status information of the authenticated GitLab user as returned by the API.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • If authentication is skipped or credentials are invalid, the node will fail to retrieve user status. Ensure valid GitLab API credentials are provided unless skipping authentication is intentional.
  • Incorrect baseUrl may cause connection errors; verify the GitLab instance URL is correct.
  • Using an unsupported HTTP method other than GET for this operation may result in API errors.

Links

Discussion