GitLab API

GitlabTool
Join our community

Actions905

Overview

This node interacts with the GitLab API to reject a user by their ID. It is useful in scenarios where an administrator needs to programmatically reject a user account in GitLab, for example, to prevent access or remove pending user requests.

Use Case Examples

  1. Reject a user with a specific ID in GitLab to prevent their access.
  2. Automate user management by rejecting users based on certain criteria.

Properties

Name Meaning
Skip Authentication Determines whether to skip the authentication process for the API 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 POST for this operation.
Parameter Schema Defines the path parameter 'id' which is the ID of the user to reject.
Request Body Schema Schema for the request body, not used in this operation (null).
Request Path The API endpoint path template for rejecting a user, including the user ID placeholder.
Path Parameters Collection of path parameters, specifically the 'id' of the user to reject.

Output

JSON

  • response - The JSON response from the GitLab API after rejecting the user, typically containing status or confirmation details.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the user ID provided in the path parameters is valid and exists in the GitLab instance.
  • Verify that the API key credential has sufficient permissions to reject users.
  • Check the baseUrl to ensure it points to the correct GitLab instance.
  • If skipping authentication, ensure the API endpoint allows unauthenticated requests, otherwise the request will fail.

Links

Discussion