GitLab API icon

GitLab API

Gitlab

Actions880

Overview

This node operation allows updating a GitLab group by its ID using the GitLab API. It is useful for scenarios where you need to modify group details such as name, description, or other attributes programmatically within an n8n workflow. For example, automating group management tasks or integrating GitLab group updates into a CI/CD pipeline.

Use Case Examples

  1. Updating the name or description of a GitLab group based on external triggers.
  2. Automating group attribute changes as part of a project setup process.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request, useful for testing or when authentication is handled externally.
Authentication Specifies the authentication method to use, defaulting to GitLab API key authentication.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method HTTP method to use for the request, default is GET but for this operation it is PUT.
Path Parameters Parameters to be included in the request path, specifically the group ID to update.

Output

JSON

  • id - The unique identifier of the updated group.
  • name - The name of the updated group.
  • description - The description of the updated group.
  • visibility - The visibility level of the updated group (e.g., private, internal, public).
  • web_url - The URL to access the updated group on GitLab.

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the group ID provided in the path parameters is correct and exists in the GitLab instance.
  • Verify that the API key used for authentication has sufficient permissions to update groups.
  • Check the base URL to confirm it points to the correct GitLab instance, especially if using a self-hosted GitLab.
  • Common error messages include 401 Unauthorized (authentication issues), 404 Not Found (invalid group ID), and 400 Bad Request (invalid request body). Resolving these involves correcting credentials, verifying group ID, and ensuring the request body matches the expected schema.

Links

Discussion