GitLab API icon

GitLab API

Gitlab

Actions917

Overview

This node interacts with the GitLab API to manage Jira Connect subscriptions via the specified API endpoint. It supports making HTTP requests to the GitLab API, particularly focusing on the operation to create Jira Connect subscriptions by sending a POST request to the /api/v4/integrations/jira_connect/subscriptions path. This node is useful for automating integration management between GitLab and Jira, such as subscribing to Jira Connect events programmatically.

Use Case Examples

  1. Automate the creation of Jira Connect subscriptions in GitLab to streamline issue tracking integration.
  2. Use the node to programmatically manage GitLab-Jira integration settings as part of a CI/CD pipeline.

Properties

Name Meaning
Skip Authentication Option to skip authentication when making the API request.
Authentication Type of authentication used for the API request, defaulting to GitLab API key authentication.
baseUrl Base URL of the GitLab instance to which the API requests are sent.
Method HTTP method used for the API request, default is GET but can be POST, PUT, DELETE, HEAD, or PATCH.
Parameter Schema Schema defining the parameters for the POST operation to create Jira Connect subscriptions.
Request Body Schema Schema defining the structure of the request body for the POST operation.
Request Path API endpoint path for creating Jira Connect subscriptions.

Output

JSON

  • response - The JSON response from the GitLab API after creating or managing Jira Connect subscriptions.

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the GitLab API key credential is correctly configured and has sufficient permissions to manage Jira Connect subscriptions.
  • Verify the baseUrl is correctly set to the GitLab instance URL if using a self-hosted GitLab server.
  • Check that the request body matches the expected schema for creating Jira Connect subscriptions to avoid validation errors.

Links

Discussion