What is a webhook?
A webhook is an automatic message sent from one system to another when a specific event occurs — a form submitted, a payment received, a job completed. The first system sends the details to a web address the second system provided, immediately, without being asked. Webhooks are the mechanism behind most instant automation, and knowing what they are helps when something breaks.
The short definition
A webhook is an automatic message sent from one system to another when a specific event occurs.
The first system sends the details to a web address the second system provided, immediately, without being asked.
The everyday comparison
There are two ways for system B to learn that something happened in system A.
Polling — B asks A every few minutes whether anything has changed. Like checking your letterbox on a schedule. Wasteful, and delayed by however long the gap is.
A webhook — A tells B the moment it happens. Like the postman ringing the bell.
Webhooks are why an enquiry can produce an instant text rather than one that arrives twelve minutes later.
Where you encounter them
Mostly without knowing it. When you connect two tools and one offers a "webhook URL" field, that is this mechanism.
Typical uses in a service business:
- Website form submitted, so the CRM creates a record immediately
- Call missed, so a text sends within seconds
- Payment received, so onboarding starts
- Job marked complete, so a review request goes out
Why speed matters here
For most of these, immediacy is the whole product.
A missed-call text arriving in three seconds keeps the customer. The same message at fifteen minutes usually does not, because they have already called someone else.
That difference is often the difference between a webhook and a polled integration, which is why it is worth knowing the word.
How they fail
Expired credentials or changed addresses. The receiving end moved and the sender was not updated.
The receiving system was down when the message was sent. Some senders retry; many do not, and that event is simply lost.
A platform update changed the format and the receiving end no longer understands it.
All of these are silent. Nothing alerts you, and the first sign is usually a quiet month.
What this means practically
You do not need to build or understand the technical detail. You do need to know that these connections exist, that they fail without announcing it, and that the only reliable defence is testing.
Submit a real enquiry through your own site every month and confirm everything downstream happened.
The one security note
A webhook address is effectively a private door into your systems. It should not be shared publicly or pasted into places it does not belong.
Where it sits
The integration work behind these connections is part of the build and workflow design in the BayouEdge packages, from $2,500 setup.
Frequently asked questions
What is the difference between a webhook and polling?
Polling means one system asks another every few minutes whether anything changed. A webhook means the first system tells the second the moment it happens — instant rather than delayed.
Why does that difference matter?
For things like missed-call text-back, immediacy is the product. A text in three seconds keeps the customer; the same message fifteen minutes later usually does not.
How do webhooks fail?
Expired credentials, a changed address, the receiving system being down when the message was sent, or a platform update changing the format. All silent — the first sign is a quiet month.
Do I need to understand the technical detail?
No. You need to know these connections exist, that they fail without announcing it, and that testing a real enquiry through your own site monthly is the only reliable defence.