Webhook
A webhook works like a reverse API: instead of polling every few minutes, the provider sends a callback when an event occurs (new order, new commit, new form submission).
Secure webhooks with signatures (HMAC) and idempotent handlers. Build workflows in n8n, Make, or Zapier. Compare with cron jobs when you want time-based execution instead of event-driven triggers.
Key characteristics
- Uses event-driven communication where systems push data in near real time between services.
- Is central to automation when you want immediate flow triggers without polling.
- Requires signature validation, idempotency, and good logging for robust operations.