GitLab API

GitlabTool

Actions1000

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, effectively managing user access control.

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 automate user rejection workflows in GitLab administration.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the request.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method HTTP method to use for the request, default is GET but POST is used for this operation.
Path Parameters Parameters to be included in the request path, specifically the user ID to reject.

Output

JSON

  • id - The ID of the user that was rejected.
  • message - Response message confirming the rejection or providing error details.

Dependencies

  • GitLab API authentication (an API key credential)

Troubleshooting

  • Ensure the user ID provided in the path parameters is valid and exists in the GitLab instance.
  • Verify that the API credentials have sufficient permissions to reject users.
  • Check the base URL to ensure it points to the correct GitLab instance.
  • Common error messages may include authentication failures or invalid user ID errors, which can be resolved by correcting credentials or user ID.

Links

Discussion