GiteaInstall

Overview

This node interacts with the Gitea API to delete a specific webhook from a repository. It is useful when you want to programmatically remove hooks that trigger external services or workflows upon repository events, such as pushes or pull requests. For example, if a webhook is no longer needed or was configured incorrectly, this node can automate its removal without manual intervention in the Gitea UI.

Properties

Output

The node outputs JSON data representing the response from the Gitea API after attempting to delete the webhook. Typically, for a successful deletion, the output may be empty or contain confirmation details depending on the API's response. No binary data is produced by this operation.

Dependencies

• Requires an API key credential for authenticating with the Gitea instance.
• Needs the base URL of the Gitea server configured in the credentials.
• Depends on the Gitea REST API being accessible and the user having permission to delete hooks on the specified repository.

Troubleshooting

• Common issues:
  • Invalid or missing API credentials will cause authentication failures.
  • Incorrect owner, repo, or hook ID values will result in errors indicating the resource was not found.
  • Insufficient permissions for the authenticated user to delete hooks.
• Error messages:
  • "Not Found" or "404" indicates the specified hook does not exist or the repository/owner is incorrect.
  • "Unauthorized" or "401" means the API key is invalid or lacks required scopes.
  • "Forbidden" or "403" suggests the user does not have rights to delete hooks on the repository.
• Resolutions:
  • Verify and update the API credentials.
  • Double-check the owner, repository name, and hook ID inputs.
  • Ensure the API token has appropriate permissions on the Gitea server.

Links and References

• Gitea API Documentation - Delete a Repository Hook
• Gitea Webhooks Overview