Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with the Gitea API to retrieve information about a specific Git hook configured on a repository. It is useful when you want to programmatically access details of a particular webhook set up in a Gitea repository, such as for auditing, monitoring, or integration purposes.

A practical example would be automating the retrieval of webhook configurations to verify their settings or to trigger further workflows based on the hook's properties.

Properties

Name Meaning
Owner The owner (user or organization) of the repository where the hook is configured.
Repo The name of the repository containing the hook.
Id The unique identifier of the Git hook to retrieve.

Output

The node outputs JSON data representing the details of the specified Git hook. This typically includes information such as the hook's configuration, events it listens to, URL, and status. No binary data output is involved.

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 read repository hooks.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials can cause authentication failures.
    • Incorrect owner, repo, or hook ID values will result in "not found" errors.
    • Network connectivity problems to the Gitea server may cause request timeouts.
  • Error messages:

    • 401 Unauthorized: Check that the API key credential is valid and has sufficient permissions.
    • 404 Not Found: Verify that the owner, repository name, and hook ID are correct.
    • 500 Internal Server Error: May indicate server-side issues; retry later or check server logs.

Links and References

Discussion