webhook
An HTTP POST sent by one system to a URL on another system when an event occurs — push, not poll.
Definition
A webhook is an HTTP POST that one system sends to a URL on another system when something happens — a new lead in HubSpot, a payment in Stripe, a message in Slack. The receiver is usually an automation platform (n8n, Make, Zapier) or a custom endpoint. Webhooks are push-based, which makes them faster and cheaper than polling, but they require the receiver to be reachable, idempotent, and tolerant of replays.
When to use
Use a webhook when you want near-real-time reaction to an event in another system, and the source system supports outbound HTTP. Otherwise fall back to polling.
See also
- idempotency — A property of an operation where calling it twice has the same effect as calling it once.
- retry — Re-attempting a failed operation, usually with exponential backoff and a maximum attempt count.
- n8n — Open-source workflow automation tool with 400+ integrations, self-hostable, fair-code licensed.
- Make.com — SaaS workflow automation platform (formerly Integromat), 1500+ integrations, visual scenario builder.
Mentioned in
- How to fix Make Maximum execution timeout 40 minutes with error handlers
- How to fix the Make HTTP module 40-second timeout error
- How to fix Zapier "Response payload size exceeded maximum allowed payload size (6291556 bytes)" error
- How to run n8n in queue mode with Redis and worker containers on Docker
- How to sync HubSpot deals to a Notion database with Make.com
- How to work around Make's 40-minute scenario hard limit
- SaaS Webhook Catalog: 30 Vendors, 1,119 Events, One Index
- Self-hosting n8n on a $5 DigitalOcean VPS: complete 2026 setup walkthrough
- The n8n Nodes Catalog: a complete, machine-readable reference