Forgejo icon

Forgejo

Interact with Forgejo API
Join our community

Actions73

Overview

This node interacts with the Forgejo API to manage webhooks within repositories. Specifically, the 'Delete' operation under the 'Webhook' resource allows users to delete a webhook from a specified repository. This is useful for automating the removal of webhooks that are no longer needed or to clean up repository configurations. For example, a user can delete a webhook by specifying the repository owner, repository name, and the webhook ID to remove the webhook from the repository.

Use Case Examples

  1. Deleting a webhook from a repository when it is no longer needed to stop receiving webhook events.
  2. Automating repository cleanup by removing outdated or unused webhooks across multiple repositories.

Properties

Name Meaning
Owner The username or organization that owns the repository where the webhook exists. This is required to identify the repository context for the webhook deletion.
Repository The name of the repository from which the webhook will be deleted. This is required to specify the exact repository.
Webhook ID The unique identifier of the webhook to be deleted. This is required to specify which webhook to remove.

Output

JSON

  • json - The response from the Forgejo API after attempting to delete the webhook. Typically, this will confirm success or provide error details.

Dependencies

  • Requires an API key credential for Forgejo API authentication to authorize requests.

Troubleshooting

  • Common issues include providing incorrect repository owner, repository name, or webhook ID, which will result in errors from the API indicating the webhook or repository was not found.
  • Authentication errors may occur if the API key credential is missing or invalid, resulting in authorization failures.
  • Network or server errors from the Forgejo API could cause the deletion to fail; retrying or checking API status may help resolve these.

Discussion