GitLab API icon

GitLab API

Gitlab

Actions880

Overview

This node operation allows users to authorize project import relations in GitLab via the API endpoint `/api/v4/projects/import-relation/authorize`. It is useful for automating the authorization process when importing projects and managing project relationships in GitLab. Typical use cases include integrating GitLab project import authorization into CI/CD pipelines or administrative automation workflows.

Use Case Examples

  1. Automate authorization of project import relations in GitLab to streamline project migration processes.
  2. Use in a workflow to programmatically authorize project imports when syncing projects between GitLab instances.

Properties

Name Meaning
Skip Authentication Option to skip API authentication for the request.
Authentication Select the authentication method to use for the API request, defaulting to GitLab API key authentication.
baseUrl Base URL of the GitLab instance to which the API request is sent, defaulting to https://gitlab.com.
Method HTTP method to use for the API request, defaulting to GET.
Parameter Schema Hidden property for the parameter schema of the API request, used internally.
Request Body Schema Hidden property for the request body schema of the API request, used internally.
Request Path Hidden property specifying the API endpoint path `/api/v4/projects/import-relation/authorize` for this operation.

Output

JSON

  • statusCode - HTTP status code returned by the API request.
  • responseBody - The JSON response body from the GitLab API after authorizing the project import relation.

Dependencies

  • GitLab API key credential for authentication unless skipping authentication is enabled.

Troubleshooting

  • Ensure the GitLab API key credential is valid and has sufficient permissions to authorize project import relations.
  • If skipping authentication, verify that the GitLab instance allows unauthenticated requests for this endpoint.
  • Check the baseUrl is correctly set to the target GitLab instance URL.
  • Common errors include 401 Unauthorized (invalid or missing API key) and 403 Forbidden (insufficient permissions).
  • Verify the HTTP method is set to POST as required by the operation.

Links

Discussion