Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with the Gitea API to retrieve details about a specific webhook configured on a repository. It is useful when you want to programmatically fetch information about a particular hook, such as its configuration or status, without manually checking the repository settings in the Gitea web interface.

Practical examples include:

  • Automating audits of repository webhooks.
  • Integrating webhook data retrieval into CI/CD pipelines.
  • Monitoring and managing hooks across multiple repositories.

Properties

Name Meaning
Owner The owner (user or organization) of the repository.
Repo The name of the repository.
Id The unique identifier of the webhook to retrieve.

Output

The node outputs JSON data representing the webhook's details as returned by the Gitea API. This typically includes properties such as the webhook's URL, events it listens to, active status, and other configuration parameters.

No binary data output is produced by this node.

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 will cause authentication failures.
    • Incorrect repository owner or name may result in "not found" errors.
    • Providing an invalid hook ID will lead to errors indicating the hook does not exist.
    • Network connectivity problems can prevent API calls from succeeding.
  • Error messages and resolutions:

    • 401 Unauthorized: Check that the API key is valid and has sufficient permissions.
    • 404 Not Found: Verify the owner, repo, and hook ID are correct.
    • Network Error: Ensure the Gitea server URL is reachable from n8n and no firewall blocks the request.

Links and References

Discussion