GitLab API

GitlabTool
Join our community

Actions1000

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 events that may have failed or need to be reprocessed. For example, if a webhook delivery failed due to a temporary network issue, this operation can be used to resend the event without recreating the hook or project.

Use Case Examples

  1. Resend a webhook event log for a project hook to troubleshoot webhook delivery issues.
  2. Retry sending a specific hook event log after fixing the receiving server.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the request (boolean). Defaults to false.
Authentication The authentication method used for the request, defaulting to GitLab API key authentication.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method The HTTP method to use for the request, defaulting to GET. Options include GET, POST, PUT, DELETE, HEAD, PATCH.
Path Parameters The path parameters required for the API call, including project ID, hook ID, and hook log ID.

Output

JSON

  • response - The response from the GitLab API after resending the hook event log

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the project ID, hook ID, and hook log ID are correctly provided and exist in GitLab.
  • Verify that the authentication credentials are valid and have sufficient permissions to resend hook events.
  • Check the base URL to ensure it points to the correct GitLab instance, especially if using a self-hosted GitLab server.
  • Common error messages may include 404 Not Found if the IDs are incorrect, or 401 Unauthorized if authentication fails.

Links

Discussion