Understand how webhooks work in n8n -- what they are, when to use them, and how they fit into workflow design.
A webhook is an HTTP callback: an external system sends an HTTP request to a URL you control, and that request triggers an action. Unlike polling (where n8n checks a service periodically), webhooks deliver data instantly when an event occurs.
In n8n, the Webhook node creates a URL endpoint that starts a workflow execution whenever it receives an HTTP request.
Use a webhook trigger when:
Use a polling trigger instead when the external service does not support webhooks or when you need to check for changes on a schedule.
Test vs Production URLs. Every Webhook node has two URLs. The test URL only works while you are listening in the editor. The production URL works when the workflow is active. External services must use the production URL.
Response modes. You control when and what the webhook sends back to the caller: immediately (fast acknowledgment), after the workflow finishes, or at a specific point using a Respond to Webhook node.
Security. n8n supports Basic Auth, Header Auth, and JWT Auth directly on the Webhook node. For production deployments, always enable authentication.
For full configuration details including HTTP methods, parameters, response modes, and patterns, see the Webhook Node Reference.
Related tips: Webhook Mastery, Security Best Practices
I build production n8n and Cloudflare automation for teams — the same engineering behind HarperFlow. Fixed-price, escrow-protected, US-based.