GitLab API icon

GitLab API

Gitlab

Actions880

Overview

This node operation allows updating the Pipelines Email service integration for a specific GitLab project by sending a PUT request to the GitLab API endpoint `/api/v4/projects/{id}/services/pipelines-email`. It is useful for managing project service configurations programmatically, such as enabling or modifying email notifications for pipeline events in GitLab projects.

Use Case Examples

  1. Updating the Pipelines Email service settings for a GitLab project to customize email notifications for CI/CD pipeline events.
  2. Automating the configuration of project integrations in GitLab as part of a DevOps workflow.

Properties

Name Meaning
Skip Authentication Option to skip API authentication for the 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 request is sent.
Method HTTP method used for the API request, default is GET but for this operation it is PUT.
Path Parameters Parameters included in the request path, specifically the project ID to identify which project's Pipelines Email service to update.

Output

JSON

  • id - The ID of the GitLab project for which the Pipelines Email service is updated.
  • serviceStatus - Status or response details of the updated Pipelines Email service integration.

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the project ID provided in the path parameters is valid and accessible with the authenticated user.
  • Verify that the API key credential has sufficient permissions to update project service integrations.
  • Check the base URL to confirm it points to the correct GitLab instance.
  • If skipping authentication, ensure the endpoint allows unauthenticated requests, otherwise the request will fail with an authentication error.

Links

Discussion