GitLab API icon

GitLab API

Gitlab

Actions880

Overview

This node operation allows rejecting a user in GitLab by sending a POST request to the endpoint `/api/v4/users/{id}/reject`. It is useful for administrators who want to reject a user's access or registration in a GitLab instance. For example, an admin can reject a user by specifying the user's ID, which triggers the rejection process via the GitLab API.

Use Case Examples

  1. Reject a user with ID 123 by sending a POST request to `/api/v4/users/123/reject`.
  2. Use this operation to manage user access control in GitLab by programmatically rejecting users.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the request (boolean). Defaults to false.
baseUrl The base URL of the GitLab instance. Defaults to https://gitlab.com.
Method HTTP method to use for the request. Defaults to POST for this operation.
Path Parameters Path parameters for the request, specifically the user ID to reject.

Output

JSON

  • id - The ID of the user that was rejected.
  • message - Response message from the GitLab API regarding the rejection status.

Dependencies

  • GitLab API authentication credential

Troubleshooting

  • Ensure the user ID provided in the path parameters is valid and exists in the GitLab instance.
  • Check that the API authentication credentials are correctly configured and have sufficient permissions to reject users.
  • If the base URL is customized, verify it is correct and accessible.
  • Common error messages may include 404 Not Found if the user ID does not exist, or 403 Forbidden if the credentials lack permission to reject users.

Links

Discussion