GitLab API icon

GitLab API

Gitlab

Actions880

Overview

This node operation allows resending a specific hook event log for a project in GitLab. It is useful for developers or DevOps engineers who want to retry sending webhook event data to an external service when the initial delivery failed or needs to be reprocessed. For example, if a webhook event was not received correctly by a third-party system, this operation can resend that event to ensure synchronization.

Use Case Examples

  1. Resend a webhook event log for a project hook to troubleshoot webhook delivery issues.
  2. Retry sending a failed webhook event to an external CI/CD system integrated with GitLab.

Properties

Name Meaning
Skip Authentication Determines whether to skip the authentication process for the API request.
baseUrl The base URL of the GitLab instance to which the API request is sent.
Method The HTTP method used for the API request, defaulting to GET but can be POST, PUT, DELETE, HEAD, or PATCH.
Path Parameters The parameters required in the API path to identify the project, hook, and specific hook event log to resend.

Output

JSON

  • statusCode - The HTTP status code returned by the API after attempting to resend the hook event log.
  • body - The response body from the API, which may contain details about the resend operation or error messages.

Dependencies

  • GitLab API authentication token or credentials

Troubleshooting

  • Ensure the project ID, hook ID, and hook log ID are correctly specified and exist in the GitLab instance.
  • Verify that the authentication credentials are valid and have sufficient permissions to access the project hooks.
  • Check the base URL to ensure it points to the correct GitLab instance, especially if using a self-hosted GitLab server.

Discussion