Webhook Trigger
An event-driven workflow trigger mechanism based on HTTP callbacks. It exposes a URL endpoint to listen for external events and starts the workflow in real time when an external system sends an HTTP POST request. It is suited to scenarios such as real-time notifications and third-party callbacks.
Timeline (last 90 days)
n8n's Webhook Trigger listens for external events by exposing a URL endpoint, and triggers the workflow immediately upon receiving an HTTP request.
The URL of a Webhook Trigger usually needs to be publicly accessible, and locally deployed n8n often needs to expose its service via intranet penetration tools or a reverse proxy.
The Webhook Trigger is an event-driven (passive response) mode, whose advantages are zero latency and zero idle runs, but the precondition is that the external system supports webhook push.
In scenarios that require second-level response (such as instant assignment of customer service tickets and monitoring alerts), the Webhook Trigger is the only choice.
When the external system does not support active push and data can only be obtained through polling, the Cron Trigger should be used rather than the Webhook Trigger.
The Cron Trigger and the Webhook Trigger are complementary tools: the former solves what should be done on schedule, and the latter solves what should be done when something happens.
All Facts (6)
n8n's Webhook Trigger listens for external events by exposing a URL endpoint, and triggers the workflow immediately upon receiving an HTTP request.
50%UnverifiedThe URL of a Webhook Trigger usually needs to be publicly accessible, and locally deployed n8n often needs to expose its service via intranet penetration tools or a reverse proxy.
50%UnverifiedThe Webhook Trigger is an event-driven (passive response) mode, whose advantages are zero latency and zero idle runs, but the precondition is that the external system supports webhook push.
50%UnverifiedIn scenarios that require second-level response (such as instant assignment of customer service tickets and monitoring alerts), the Webhook Trigger is the only choice.
50%UnverifiedWhen the external system does not support active push and data can only be obtained through polling, the Cron Trigger should be used rather than the Webhook Trigger.
50%UnverifiedThe Cron Trigger and the Webhook Trigger are complementary tools: the former solves what should be done on schedule, and the latter solves what should be done when something happens.
50%