Stockertim Dictionary · Technology · Artificial intelligence
Webhook
Also called webhooks, web hook, HTTP callback
In short
A webhook is a message that one system sends automatically to another's web address the moment an event happens, so a workflow can start at once instead of checking for changes.
- Intermediate
- Technology
- Checked
In detail
A webhook reverses the usual direction of asking. Instead of a workflow tool repeatedly asking a form service whether anything new has arrived, the form service is given a web address, often called the callback or endpoint, and sends a message there as soon as a submission comes in. The message is normally an HTTP POST request carrying details of the event in a structured format such as JSON.
Setting one up means registering the receiving address with the sending system and choosing which events trigger a message. The receiver replies quickly with a success code and does the real work afterwards, because many senders treat a slow reply as a failure and send the message again. Senders that retry on failure can deliver the same event twice, and events can arrive out of order, so receivers record an event identifier and ignore repeats.
Because a webhook address is reachable from the internet, anyone who discovers it can post fake events to it. Common protections are a shared secret used to sign each message, which the receiver checks before acting, plus HTTPS and limits on what the receiving workflow is allowed to do.
Webhooks give near-instant reactions and avoid wasted checks, but they depend on the sender. If the sending system is down or the receiver misses messages, nothing arrives and nothing complains, so many teams pair webhooks with an occasional reconciliation check.
Worked example
Tamarind Events wants new booking forms to reach its planning sheet at once.
- The workflow tool provides a receiving address, which is saved in the form service's webhook settings for the event "new submission".
- A customer submits a booking; the form service posts the details to the address within seconds.
- The workflow checks the signature, records the event identifier and adds a row to the sheet.
- A repeated delivery of the same event is recognised by its identifier and ignored.
Bookings appear in the sheet seconds after submission, without duplicates or a timer checking for changes.
In practice
Workflow builders use webhooks wherever a source system offers them, check message signatures, store event identifiers to drop duplicates, and run a daily comparison against the source to catch any events that never arrived.
Watch out
- A webhook without signature checks lets anyone who learns the address trigger the workflow.
- Silence is ambiguous: no messages can mean no events or a broken connection.
Learn it properly
Official sources
- WebSub · World Wide Web Consortium (W3C)
- API technical and data standards · Government Digital Service
Facts last checked on 9 November 2026.
Education, not advice: the Stockertim Dictionary explains what terms mean. It never recommends buying or selling anything.