GitLab API icon

GitLab API

Gitlab
Join our community

Actions917

Overview

This node integrates with the GitLab API, specifically supporting the Slack trigger operation via the GitLab API v4 endpoint. It allows users to send HTTP requests to GitLab's Slack trigger endpoint, which can be used to trigger Slack notifications or actions based on GitLab events. This is useful for automating communication workflows between GitLab and Slack, such as notifying a Slack channel about GitLab pipeline statuses or merge requests.

Use Case Examples

  1. Trigger a Slack notification from GitLab when a pipeline completes.
  2. Send custom data to GitLab's Slack trigger endpoint to automate Slack messages based on GitLab events.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request.
Authentication Type of authentication used for the request, hidden unless Skip Authentication is false.
baseUrl Base URL for the GitLab instance, defaulting to https://gitlab.com.
Method HTTP method to use for the request (GET, POST, PUT, DELETE, HEAD, PATCH).
Parameter Schema Schema defining the parameters for the postApiV4SlackTrigger operation, hidden from UI.
Request Body Schema Schema defining the request body for the postApiV4SlackTrigger operation, hidden from UI.
Request Path API endpoint path for the Slack trigger operation, fixed to /api/v4/slack/trigger.

Output

JSON

  • response - The JSON response returned from the GitLab Slack trigger API call.

Dependencies

  • GitLab API authentication credentials

Troubleshooting

  • Ensure the GitLab API credentials are correctly configured and have the necessary permissions to access the Slack trigger endpoint.
  • Verify the baseUrl is correct and accessible, especially if using a self-hosted GitLab instance.
  • Check that the HTTP method matches the expected method for the Slack trigger endpoint, typically POST.
  • If skipping authentication, ensure the endpoint allows unauthenticated access, otherwise requests will fail.

Links

Discussion