GitLab API

GitlabTool
Join our community

Actions905

Overview

This node interacts with the GitLab API to update a group member's information using the PUT method on the endpoint `/api/v4/groups/{id}/members/{user_id}`. It is useful for managing group memberships in GitLab, such as changing a member's access level or other membership details. Practical examples include automating group member updates in CI/CD pipelines or administrative workflows.

Use Case Examples

  1. Updating a user's access level in a GitLab group.
  2. Automating membership changes in a GitLab group as part of a user management system.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request.
Authentication Type of authentication used, defaulting to GitLab API key authentication.
baseUrl Base URL for the GitLab instance, default is https://gitlab.com.
Method HTTP method to use for the request, default is GET but PUT is used for this operation.
Parameter Schema Defines the required path parameters and request body schema for the operation.
Request Body Schema Schema for the request body payload to update the group member.
Request Path API endpoint path for the operation.
Path Parameters Collection of path parameters including group ID and user ID to specify which member to update.

Output

JSON

  • id - The ID of the updated group member.
  • username - The username of the updated group member.
  • access_level - The access level assigned to the group member.
  • expires_at - Expiration date of the membership if set.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the group ID and user ID path parameters are correctly set and valid.
  • Verify that the API key credential has sufficient permissions to update group members.
  • Check that the request body conforms to the expected schema for updating a group member.
  • Common errors include 404 Not Found if the group or user does not exist, and 403 Forbidden if the API key lacks permissions.

Links

Discussion