Overview
This node acts as a trigger for Gitea events, starting an n8n workflow whenever specific events occur in a Gitea repository. It listens to webhook POST requests from Gitea and routes the incoming event data to different outputs based on the event type.
Common scenarios where this node is beneficial include automating workflows triggered by repository activities such as creating issues, pushing commits, managing pull requests, or handling releases. For example, you could use it to automatically notify a team chat when a new issue is created or to trigger CI/CD pipelines when code is pushed.
Properties
| Name | Meaning |
|---|---|
| Activate Unmatched Output | Whether to send events that do not match any enabled event output to a dedicated "unmatched" output. |
| Event Outputs | Select which Gitea event types should have dedicated outputs. Events not selected can be routed to unmatched if enabled. Options include: Create, Delete, Fork, Push, Issues, Issue Assign, Issue Label, Issue Milestone, Issue Comment, Pull Request, Pull Request Assign, Pull Request Label, Pull Request Milestone, Pull Request Comment, Pull Request Review Approved, Pull Request Review Rejected, Pull Request Review Comment, Pull Request Sync, Pull Request Review Request, Wiki, Repository, Release, Package, Status. |
Output
The node outputs JSON data representing the webhook payload received from Gitea. The structure of the json output field includes:
body: The full body of the webhook request containing event details.headers: HTTP headers sent with the webhook, including metadata like event type.query: Any query parameters included in the webhook URL.
Outputs are split into multiple main outputs corresponding to each enabled event type. If the event does not match any enabled output and the unmatched output is activated, the event data is sent to the unmatched output.
No binary data is produced by this node.
Dependencies
- Requires a publicly accessible webhook URL configured in Gitea to receive event POST requests.
- No external API keys or credentials are required within the node itself, but proper webhook setup in Gitea is necessary.
- The node depends on n8n's webhook infrastructure to receive and process incoming HTTP requests.
Troubleshooting
- Webhook Not Triggering: Ensure the webhook URL provided by n8n is correctly set up in the Gitea repository settings and that the server running n8n is reachable from Gitea.
- Events Not Routed Correctly: Verify that the desired event types are enabled in the "Event Outputs" property. If an event is not enabled and unmatched output is disabled, the event will be ignored.
- Unexpected Empty Outputs: If no outputs receive data, check if the incoming event header
x-gitea-event-typematches one of the enabled event types exactly. - Permission Issues: Make sure the Gitea instance allows sending webhooks to external URLs and that firewalls or proxies do not block the requests.