Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with the Gitea API to manage organization webhooks. Specifically, the "Org Delete Hook" operation deletes a webhook from a specified organization by its ID. This is useful for automating the cleanup or management of organization hooks in Gitea repositories, such as removing outdated or unnecessary webhook integrations.

Practical examples include:

  • Automatically removing a webhook when an integration is no longer needed.
  • Cleaning up hooks during organization restructuring or migration.
  • Managing hooks programmatically as part of CI/CD workflows.

Properties

Name Meaning
Org The name of the organization from which the webhook will be deleted.
Id The numeric ID of the webhook to delete within the specified organization.

Output

The node outputs JSON data representing the response from the Gitea API after attempting to delete the webhook. Typically, this will confirm successful deletion or provide error details if the operation failed.

No binary data output is expected from this operation.

Dependencies

  • Requires an API key credential for authenticating with the Gitea instance.
  • The node expects the base URL of the Gitea server to be configured in the credentials.
  • Network access to the Gitea API endpoint /api/v1 is necessary.

Troubleshooting

  • Common issues:

    • Invalid organization name or webhook ID may cause the deletion to fail.
    • Insufficient permissions for the API key can result in authorization errors.
    • Network connectivity problems to the Gitea server will prevent the request.
  • Error messages and resolutions:

    • 404 Not Found: The specified webhook ID does not exist in the given organization. Verify the ID and organization name.
    • 401 Unauthorized or 403 Forbidden: The API key lacks permission to delete hooks. Ensure the API key has appropriate scopes.
    • Network errors: Check network connectivity and Gitea server availability.

Links and References

Discussion