GitLab API icon

GitLab API

Gitlab
Join our community

Actions917

Overview

This node operation updates the 'Emails on Push' integration settings for a specific GitLab group via the GitLab API. It is useful for automating the configuration of email notifications triggered by push events in a GitLab group. For example, a DevOps engineer can use this node to programmatically enable or modify email notifications for team members when code is pushed to the group's repositories.

Use Case Examples

  1. Updating email notification settings for a GitLab group to ensure team members receive push event alerts.
  2. Automating the configuration of GitLab group integrations as part of a CI/CD pipeline setup.

Properties

Name Meaning
Skip Authentication Determines whether to skip API authentication for the request.
Authentication Specifies the authentication method to use, defaulting to GitLab API key authentication.
baseUrl The base URL of the GitLab instance to which the API request is sent.
Method The HTTP method used for the API request, default is PUT for this operation.
Path Parameters Parameters included in the API 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 for authentication

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, the request may be unauthorized unless the GitLab instance allows anonymous access.
  • Verify that the baseUrl is correct and accessible; incorrect URLs will cause connection errors.
  • Common error messages include 401 Unauthorized (check API key), 404 Not Found (invalid group ID), and 400 Bad Request (invalid request body).

Links

Discussion