Definition
A message one app sends automatically to another the moment something happens, such as a lead qualified or an appointment booked. Instead of asking “anything new?”, the receiving system is told right away.
Being told instead of asking
There are two ways for one system to learn what happens in another. It can ask every few minutes, “any new leads?”, which is slow and wasteful. Or the other system can tell it the moment something happens. That second way is a webhook: an automatic web request, usually an HTTPS POST with a JSON body, sent to an address you choose when an event occurs. It is how most tools feed Zapier, Make or your own systems in real time, without anyone pressing export.
A concrete example
Brightline Agency wants every qualified lead in its CRM within seconds, with a message in its team chat. Its qualification tool sends a webhook to a scenario in Make or a zap in Zapier, with a body like this one (simplified):
{"event": "lead.qualified", "name": "Sarah K.", "phone": "+447700900123", "source": "instagram"}
The automation creates the contact, posts the message and assigns an owner. Nobody copies anything by hand, and nobody waits for a nightly export.
Doing it safely
- Check the signature. A signed webhook carries a code computed from the body and a secret shared with the sender. Verify it before trusting the data; Meta signs its own webhooks this way.
- Answer fast, then do the work. Senders expect a quick success response and may retry, or give up, if you’re slow.
- Expect duplicates. A retried event can arrive twice: use its ID to ignore repeats.
- Use HTTPS, and keep secrets out of the URL.
Webhooks in WhatSetter
WhatSetter sends signed webhooks when a lead is qualified or not, an appointment is booked, a message is received, a number disconnects or a tag is added. Because each one is signed, your system can check that it really came from WhatSetter before acting on it. Zapier and Make connect through them on the way out, and through forms on the way in. For everything else, there is a REST API and an MCP server. See integrations & API.