←  All terms
W
APIs & Integrations

Webhook

A webhook automatically sends data to another system over HTTP when an event occurs.

A webhook enables systems to exchange data automatically in response to specific events, without requiring the receiving system to poll continuously for changes. When an event is triggered, the source sends an HTTP request with the relevant payload to a predefined endpoint. Reliable implementations depend on clear data contracts, secure authentication, robust error handling, and observable delivery and retry behavior. The concept is closely related to API and Process Automation.

Read more

API

Process Automation

Serverless Function

REST API

FAQ

Webhook

What are webhooks typically used for in practice?
Typical uses are notifications for form submissions, payments, or content changes that feed into process automation and third-party systems. A webhook can, for example, pass an inquiry into a CRM. For heavier processing, a serverless function works well as an intermediate layer so that receipt is acknowledged quickly.
What happens when a webhook fails or arrives twice?
Senders often retry failed deliveries, which can lead to duplicates. The receiver should therefore process events idempotently and log errors. Without monitoring, lost events often surface late, for instance when data between systems starts to diverge. A queue additionally decouples receipt from processing.
How are webhooks protected against forged requests?
The receiver verifies the origin of every request, for example through a signature or a shared secret, and accepts only encrypted connections. Without verification, anyone could send forged data to the endpoint. Limited permissions, timestamps against replayed requests, and logging are part of the safeguards as well.
How does a webhook differ from an API request?
With an API request the receiver actively asks, while a webhook reports on its own as soon as an event occurs. Polling causes unnecessary requests and delay, whereas webhooks deliver promptly. In return, the receiver needs a reachable endpoint and must cope with outages and duplicate deliveries.