GitLab API

GitlabTool
Join our community

Actions905

Overview

This node operation updates a user's information in GitLab via the GitLab API. It is useful for scenarios where you need to modify user details such as name, email, or other profile attributes programmatically. For example, an admin could automate updating user profiles in bulk or integrate user management into a larger workflow.

Use Case Examples

  1. Updating a user's email address in GitLab.
  2. Changing a user's access level or profile information via an automated process.

Properties

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

Output

JSON

  • id - The unique identifier of the user.
  • username - The username of the user.
  • email - The email address of the user.
  • name - The full name of the user.
  • state - The state of the user (e.g., active, blocked).
  • created_at - The timestamp when the user was created.
  • updated_at - The timestamp when the user was last updated.
  • other_properties - Additional user properties returned by the GitLab API after update.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the user ID provided in the path parameters is valid and exists in GitLab.
  • Verify that the API key used has sufficient permissions to update user information.
  • Check the base URL to ensure it points to the correct GitLab instance.
  • Common error messages include 401 Unauthorized (invalid or missing API key), 404 Not Found (user ID does not exist), and 400 Bad Request (invalid request body). Resolving these involves correcting credentials, verifying user ID, and ensuring the request body matches the expected schema.

Links

Discussion