GitLab API

GitlabTool
Join our community

Actions1000

Overview

This node performs an HTTP PUT request to update a user in the GitLab system by their user ID. It is useful for scenarios where you need to modify user details programmatically, such as updating user information in bulk or integrating user management into an automated workflow.

Use Case Examples

  1. Updating a user's profile information by specifying their user ID and new data.
  2. Automating user attribute changes in GitLab from an external system.

Properties

Name Meaning
Skip Authentication Determines whether to skip the authentication step for the request.
Authentication Specifies the authentication method to use, defaulting to GitLab API authentication.
baseUrl The base URL of the GitLab instance to which the request is sent.
Method The HTTP method to use for the request, defaulting to PUT for this operation.
Path Parameters The path parameters for the request, specifically the user ID to identify which user to update.

Output

JSON

  • id - The unique identifier of the updated user.
  • username - The username of the updated user.
  • name - The full name of the updated user.
  • state - The state of the user (e.g., active, blocked).
  • avatar_url - URL to the user's avatar image.
  • web_url - URL to the user's GitLab profile page.

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 authentication credentials are correctly configured and have sufficient permissions to update user details.
  • Check the base URL to ensure it points to the correct GitLab instance.
  • Common error messages include 401 Unauthorized (authentication failure), 404 Not Found (user ID does not exist), and 400 Bad Request (invalid request body or parameters). Resolving these involves correcting credentials, verifying user ID, and ensuring request body schema compliance.

Links

Discussion