GitLab API icon

GitLab API

Gitlab
Join our community

Actions917

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, if a user registration needs to be denied or revoked, this operation can be used to perform that action programmatically within an n8n workflow.

Use Case Examples

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

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 authentication.
baseUrl The base URL of the GitLab instance to which the request is sent, defaulting to https://gitlab.com.
Method The HTTP method used for the request, defaulting to GET but set to POST for this operation.
Parameter Schema Schema defining the path parameter 'id' which is the ID of the user to reject.
Request Body Schema Schema for the request body, which is null for this operation (no body required).
Request Path The API endpoint path template used for the request, specifically /api/v4/users/{id}/reject.
Path Parameters Collection of path parameters including 'id' which specifies the user ID 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 authentication credential

Troubleshooting

  • Ensure the user ID provided in the path parameters is valid and exists in the GitLab instance.
  • Verify that the API authentication credentials are correctly configured and have sufficient permissions to reject users.
  • Check the baseUrl to ensure it points to the correct GitLab instance if using a self-hosted GitLab server.
  • Common error messages may include 404 Not Found if the user ID does not exist, or 403 Forbidden if the authentication lacks permission to perform the reject operation.

Links

Discussion