A webhook sends a notification to another system when a configured event occurs. It can help start a workflow without the receiving system repeatedly asking whether anything changed.
The notification is only one part of the process. A reliable integration still needs to validate the event, handle duplicates and perform the intended action safely.
Webhook versus API polling
Polling repeatedly requests information to check for changes. A webhook pushes a notification when the sending system recognises the event.
The choice depends on the supported capabilities and operational requirements. Some workflows combine notifications with a later API request for authoritative details.
What does the notification contain?
The payload depends on the provider. It may include event information, identifiers or a snapshot of a record.
Do not assume it contains every field or the latest final state. Read the provider's contract and establish whether further verification is required.
How is authenticity checked?
Providers may support signatures or other verification methods. The receiver should apply the relevant documented approach before trusting the message.
A publicly reachable endpoint should not treat every incoming request as an authorised business event.
Can notifications arrive twice?
Delivery systems can retry, and a receiver may encounter duplicates or delayed events. Design the action so repeated delivery does not create repeated unwanted effects.
Use appropriate identifiers and state checks. “We received a message” is not the same as “this action has not already happened”.
What happens when delivery fails?
The provider's retry and retention rules matter. The receiving workflow also needs monitoring and a recovery process.
Avoid relying solely on an unseen notification. Important operational actions should leave evidence that someone can inspect.
How should a webhook workflow be tested?
Test normal delivery, duplicates, invalid messages and temporary failures. Verify the outcome in the destination system.
Define who responds when the process stops working. A technically successful endpoint is useful only if the overall business action completes reliably.
Further reading
For reference, see the supporting documentation. Explore related explanations of API, Marketing automation, Customer relationship management.
A practical example
Illustrative example: a confirmed booking event triggers an internal preparation task. The receiver verifies the notification and checks the booking identifier before creating the task, so a retried event does not produce several identical assignments.
Why it matters
Webhooks support responsive integration. Verification, duplicate handling and monitoring turn notifications into dependable workflows.
