A webhook is a message one app sends to another the moment something happens. The sending app posts a small packet of data, usually in JSON format, to a web address that the receiving app gives it. Unlike a normal API call, the receiver does not keep asking for updates. It simply waits for the message to arrive.
Also called: Web hook, HTTP callback, Outgoing webhook
A prospect books a demo in your scheduling tool. The tool posts a message to a webhook URL in your automation platform. The message might look like this:
{
"event": "meeting.booked",
"email": "priya@example.com",
"company": "Example Ltd",
"start": "2026-11-10T10:00:00Z"
}
Your workflow reads those fields, finds or creates the contact, updates the deal stage and alerts the account executive. All of it starts within seconds of the booking.
Most SaaS tools can send webhooks, even when they have no ready-made integration with your CRM. That makes webhooks the usual glue between niche tools: billing, product analytics, scheduling, support. They are also faster than polling, because nothing waits for the next check.
The catch is that a webhook URL is a public address. Anyone who finds it can send data to it, so the receiver should verify each message before acting on it.
Related terms
See the full B2B marketing glossary
Webhook-driven workflows on cloud or self-hosted n8n, with logging and alerts.
Go to page →Catch-hook Zaps and app connections built and documented.
Go to page →Someone to own your webhooks, integrations and run logs every month.
Go to page →Tell us which tools you use and where leads or data get stuck. We will suggest the first three automations worth building.
We reply within one business day.