Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with the Gitea API to list webhooks configured for a specific organization. It is useful when you want to retrieve and manage the hooks that trigger on events within an organization hosted on a Gitea instance. Typical use cases include auditing existing hooks, monitoring webhook configurations, or integrating webhook data into workflows.

For example, you might use this node to fetch all hooks for your development organization's repositories to verify their setup or to synchronize webhook information with another system.

Properties

Name Meaning
Org The name of the organization whose hooks you want to list.
Page The page number of results to return (1-based). Useful for paginating through many hooks.
Limit The maximum number of hooks to return per page (page size).

Output

The node outputs JSON data representing the list of webhooks for the specified organization. Each item in the output array corresponds to a webhook object containing details such as its ID, URL, events it listens to, active status, and other metadata as provided by the Gitea API.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with a Gitea instance.
  • The node expects the base URL of the Gitea server to be configured in the credentials.
  • The Gitea API must be accessible from the n8n environment where this node runs.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Incorrect organization name may result in empty results or errors.
    • Pagination parameters (page and limit) set incorrectly could lead to unexpected result sizes or no data.
  • Error messages:

    • Authentication errors typically indicate invalid or expired API tokens; reconfigure credentials.
    • "Organization not found" or similar errors suggest verifying the organization name spelling and existence.
    • Rate limiting errors from the API require waiting or adjusting request frequency.

Links and References

Discussion