GitLab API

GitlabTool
Join our community

Actions905

Overview

This node operation deletes a member from a specific GitLab project using the GitLab API. It is useful for managing project memberships by removing users who should no longer have access to the project. For example, a project administrator can use this node to revoke access for a user who has left the team or no longer requires project permissions.

Use Case Examples

  1. Removing a user from a project to revoke their access.
  2. Automating membership cleanup when a user leaves an organization.

Properties

Name Meaning
Skip Authentication If set to true, the node will skip the authentication process for the API request.
Authentication The authentication method used for the API request, typically an API key credential for GitLab.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method The HTTP method used for the API request, default is GET but DELETE is used for this operation.
Query Parameters Optional query parameters for the delete operation, including skip_subresources and unassign_issuables.
Path Parameters Required path parameters specifying the project ID and the user ID of the member to delete.

Output

JSON

  • success - Indicates whether the member was successfully deleted.
  • statusCode - HTTP status code returned by the API.

Dependencies

  • GitLab API authentication token or API key credential

Troubleshooting

  • Ensure the project ID and user ID are correct and exist in GitLab.
  • Check that the API authentication token has sufficient permissions to delete project members.
  • If the deletion fails, verify the query parameters skip_subresources and unassign_issuables are correctly set as booleans or omitted.
  • Common error messages include 404 Not Found if the project or user does not exist, and 403 Forbidden if the token lacks permissions.

Links

Discussion