GitLab API

GitlabTool
Join our community

Actions1000

Overview

This node operation performs a POST request to the GitLab API endpoint `/api/v4/topics/merge` to merge topics. It is useful in scenarios where you want to consolidate multiple topics into a single one within a GitLab instance, such as cleaning up or organizing project topics.

Use Case Examples

  1. Merging two or more topics in a GitLab project to unify related discussions or tags.
  2. Automating topic management in GitLab repositories via n8n workflows.

Properties

Name Meaning
Skip Authentication Determines whether to skip authentication for the API request.
Authentication Specifies the authentication method to use if authentication is not skipped.
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 POST for this operation.
Parameter Schema Defines the schema for the request body parameters required to merge topics.
Request Body Schema Schema for the request body, typically containing the details of the topics to merge.
Request Path The API endpoint path for merging topics, fixed as `/api/v4/topics/merge`.

Output

JSON

  • response - The JSON response from the GitLab API after merging topics, containing details about the merged topics or operation status.

Dependencies

  • GitLab API authentication credential

Troubleshooting

  • Ensure the baseUrl is correctly set to your GitLab instance URL; otherwise, the request will fail.
  • If authentication is required and skipped, the API call will likely fail with an authentication error.
  • Verify that the request body matches the expected schema for merging topics; invalid or incomplete data will cause errors.
  • Common error messages include 401 Unauthorized (authentication issues), 400 Bad Request (invalid parameters), and 404 Not Found (incorrect endpoint or resource).

Links

Discussion