GitLab API

GitlabTool
Join our community

Actions1000

Overview

This node operation allows users to approve a specific deployment within a GitLab project by making a POST request to the GitLab API endpoint `/api/v4/projects/{id}/deployments/{deployment_id}/approval`. It is useful in scenarios where automated workflows need to programmatically approve deployments as part of a CI/CD pipeline or deployment management process.

Use Case Examples

  1. Automatically approve a deployment after successful tests in a CI/CD pipeline.
  2. Trigger deployment approval based on external conditions or manual triggers within an automation workflow.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request, useful for public or unauthenticated API calls.
Authentication Select the authentication method, typically an API key credential for GitLab.
baseUrl Base URL of the GitLab instance, defaulting to https://gitlab.com.
Method HTTP method to use for the request, default is POST for this operation.
Path Parameters Parameters to specify the project ID or URL-encoded path and the deployment ID to approve.

Output

JSON

  • status - HTTP response status code indicating the result of the approval request.
  • data - Response data from the GitLab API about the deployment approval.

Dependencies

  • GitLab API authentication token or API key credential

Troubleshooting

  • Ensure the project ID and deployment ID are correctly specified and exist in the GitLab instance.
  • Verify that the authentication token has sufficient permissions to approve deployments.
  • Check the base URL if using a self-hosted GitLab instance instead of gitlab.com.
  • Common error: 401 Unauthorized - indicates missing or invalid authentication credentials.
  • Common error: 404 Not Found - indicates the project or deployment ID does not exist or is inaccessible.

Links

Discussion