GitLab API icon

GitLab API

Gitlab
Join our community

Actions917

Overview

This node operation updates the Squash TM integration settings for a specific GitLab project using the GitLab API. It is useful for automating the configuration of Squash TM integration in GitLab projects, such as enabling or modifying integration parameters programmatically.

Use Case Examples

  1. Automatically update Squash TM integration settings for a project when a new project is created.
  2. Modify Squash TM integration parameters in bulk for multiple projects via workflow automation.

Properties

Name Meaning
Skip Authentication Determines whether to skip authentication for the API request.
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 The HTTP method to use for the request, defaulting to PUT for this operation.
Path Parameters The path parameters for the API request, specifically the project ID to identify which project's Squash TM integration to update.

Output

JSON

  • response - The JSON response from the GitLab API after updating the Squash TM integration settings.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the project ID provided in path parameters is valid and exists in the GitLab instance.
  • Verify that the API key used has sufficient permissions to update project integrations.
  • Check the baseUrl is correctly set to the GitLab instance URL if using a self-hosted GitLab.
  • Common error messages include 401 Unauthorized (invalid or missing API key), 404 Not Found (invalid project ID), and 400 Bad Request (invalid request body). Resolving these involves correcting credentials, project ID, or request payload respectively.

Links

Discussion