What is Webhook?
A webhook is a notification from software to software: as soon as an event occurs in one system - new enquiry, paid invoice, booked appointment - it immediately sends the data to a stored address of another system. The difference from a classic API query is the direction: with an API, your system actively asks ("anything new?"); with a webhook, the source reports by itself. Push instead of pull.
Precisely this direction makes webhooks the backbone of automation: without them, every tool would have to poll all the others by the minute - laborious, error-prone and still always a beat too late. With webhooks you get a chain of trigger and reaction: form submitted, webhook fires, CRM creates the contact, the first reply goes out - within seconds, without a human touching anything. Automation platforms and agent workflows consist at their core of exactly such chains.
The honest part: webhooks are infrastructure, not magic. They need a receiving end that accepts the message, safeguards so that not just any sender can trigger actions, and a plan B for failed deliveries - reputable providers retry automatically. Set that up properly once, and you get the building block that turns individual tools into a workflow that runs on its own.
Why does Webhook matter?
The difference between a webhook and periodic polling is the difference between seconds and hours - and with enquiries, that very gap decides the deal: speed-to-lead simply cannot be achieved without an event-driven chain, because any polling automation is structurally too late. When choosing tools today, do not just ask whether there is an API - ask which events the system can report of its own accord.
Webhook in practice
- 01A consultancy connects its contact form to CRM and notifications via webhook: new enquiries are in the system within seconds and the sales team is alerted immediately - instead of checking the inbox three times a day.
- 02A payment provider reports every paid invoice to the accounting software via webhook - the status flips to "paid" automatically, and nobody reconciles bank statements by hand any more.
- 03A no-show protection uses the booking tool's webhook: if a customer cancels, the event fires and the automation immediately offers the freed slot to the waiting list.
From the journal
- Connecting tools: when an integration is enough and when it hides the problemConnecting two tools is an afternoon's work these days. Whether it helps is decided before that: an integration moves data, it does not make decisions. If the rule about who does what and when is missing, the connection only speeds up the confusion. Here is how to tell the two cases apart in five minutes.
- Make or buy for AI projects: when purchasing beats buildingBuilding it yourself sounds like control, independence and a perfect fit. The data tells a different story: purchased AI solutions reach production roughly twice as often as internal builds - and the market swung sharply towards buying in 2025. When building is still the right call, and how to decide properly.
