GitLab API

GitlabTool
Join our community

Actions1000

Overview

This node operation retrieves the services (integrations) configured for a specific GitLab project by making a GET request to the GitLab API endpoint `/api/v4/projects/{id}/services`. It is useful for scenarios where you need to programmatically access or audit the integrations set up on a GitLab project, such as CI/CD services, monitoring tools, or other third-party integrations.

Use Case Examples

  1. Fetch all integrations for a GitLab project to display their status in a dashboard.
  2. Automate auditing of project services to ensure compliance with organizational policies.

Properties

Name Meaning
Skip Authentication If set to true, the node will skip using authentication for the API request.
Authentication Specifies the authentication method to use, defaulting to GitLab API key authentication. Hidden if Skip Authentication is true.
baseUrl The base URL of the GitLab instance to which the API request is sent, defaulting to https://gitlab.com.
Method The HTTP method used for the API request, defaulting to GET. Other methods like POST, PUT, DELETE, HEAD, PATCH are available but typically GET is used for this operation.
Path Parameters The path parameter 'id' specifies the project ID for which the services are being retrieved.

Output

JSON

  • services - The list of services (integrations) configured for the specified GitLab project.

Dependencies

  • Requires GitLab API key credential unless Skip Authentication is enabled.

Troubleshooting

  • Ensure the project ID provided in the path parameters is valid and accessible with the provided authentication.
  • If authentication is skipped, the API request may fail due to lack of permissions.
  • Check the baseUrl to ensure it points to the correct GitLab instance, especially if using a self-hosted GitLab server.
  • Common error messages include 401 Unauthorized (authentication issues), 404 Not Found (invalid project ID), and 403 Forbidden (insufficient permissions).

Links

Discussion