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.