Webhook

Part of our topic guide on AI Skills for Business.

A webhook is an automated message one system sends to another the moment something happens — a payment clears, a form is submitted, an order ships. Instead of one system repeatedly asking "has anything changed?", the other system simply pushes the update straight away.

Why it matters

Webhooks are how modern business tools talk to each other without a person copying data between them. Your payment provider tells your accounting software the instant an invoice is paid; your e-commerce platform tells your warehouse system the instant an order comes in. No one is manually checking, exporting or re-keying anything.

For employers, this matters because so much of the daily grind in a data or operations role — chasing whether something has updated, reconciling two systems by hand — is exactly the kind of work a webhook removes. In our experience, the people who get real value from data and AI tools aren't the ones who know the most theory; they're the ones who understand how systems actually connect and where the manual steps still are. That's a capability gap, not a tools gap — most failed data and automation projects stall on people not knowing how to use what's already there, not on missing technology.

For learners, webhooks are a good example of "the new basics": you don't need a computer science degree to understand one, but understanding how systems push and receive data is fast becoming as fundamental as reading a spreadsheet.

How it works

• The trigger — an event happens in the source system: a customer completes checkout, a support ticket is closed, a new row is added to a form.
• The push — the source system sends an HTTP request (almost always a POST request) containing the event details to a URL the receiving system has registered in advance. This URL is often called an "endpoint" or "listener".
• The payload — the request carries the relevant data, usually formatted as JSON, so the receiving system knows exactly what happened and to what record.
• The response — the receiving system processes the data and sends back a simple confirmation (typically an HTTP 200 status) to say it arrived.

The key contrast is with an API request, which the receiving system has to actively make to ask for data ("polling"). A webhook flips that: the sending system does the asking, sending data out as soon as it's ready, so nothing sits waiting to be noticed.