GitLab API icon

GitLab API

Gitlab

Actions917

Overview

This node interacts with the GitLab API to perform operations related to the User resource, specifically the 'postApiV4UserSupportPin' operation. It sends a POST request to the '/api/v4/user/support_pin' endpoint to manage the user's support pin. This can be useful in scenarios where automated workflows need to update or manage user support pins in GitLab, such as in user management or support ticket automation.

Use Case Examples

  1. Automatically update a user's support pin when certain conditions are met in a workflow.
  2. Integrate GitLab user support pin management into a larger DevOps automation pipeline.

Properties

Name Meaning
Skip Authentication Determines whether to skip authentication for the request.
Authentication Specifies the authentication method to use, defaulting to GitLab API key authentication.
baseUrl The base URL for the GitLab instance to which the API requests are sent.
Method The HTTP method to use for the request, defaulting to POST for this operation.
Parameter Schema Schema for the parameters of the request, used internally and hidden from the user.
Request Body Schema Schema for the request body, used internally and hidden from the user.
Request Path The API endpoint path for the operation, fixed to '/api/v4/user/support_pin' and hidden from the user.

Output

JSON

  • response - The JSON response from the GitLab API after posting the user support pin.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the GitLab API key credential is correctly configured and has the necessary permissions to post user support pins.
  • Verify the baseUrl is correct and accessible from the environment where the node runs.
  • Check that the HTTP method is set to POST as required by the operation.
  • If the API returns an error, review the response message for details such as authentication failure, permission issues, or invalid request body.

Links

Discussion