GitLab API icon

GitLab API

Gitlab
Join our community

Actions880

Overview

This node operation allows updating the 'Emails on Push' integration settings for a specific group in GitLab via a PUT request to the GitLab API. It is useful for automating the configuration of email notifications triggered by push events in GitLab groups, which helps teams stay informed about repository changes.

Use Case Examples

  1. Automatically update email notification settings for a GitLab group when a new project is created.
  2. Integrate with a CI/CD pipeline to adjust email push notifications based on deployment environments.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request, useful for public or unauthenticated endpoints.
Authentication Specifies the authentication method to use, defaulting to GitLab API key authentication.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method HTTP method to use for the request, default is GET but PUT is used for this operation.
Path Parameters Parameters to be included in the request path, specifically the 'id' of the GitLab group to update.

Output

JSON

  • response - The JSON response from the GitLab API after updating the Emails on Push integration settings.

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the 'id' path parameter is correctly set to the target GitLab group ID; otherwise, the API call will fail.
  • If authentication is skipped, verify that the endpoint supports unauthenticated access, or the request will be rejected.
  • Check that the baseUrl is correct and accessible, especially if using a self-hosted GitLab instance.
  • Common error messages include 401 Unauthorized (authentication issues), 404 Not Found (invalid group ID), and 400 Bad Request (invalid request body).

Links

Discussion