Glossary · Marketing automation

What is a webhook?

Definition

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

By Vinod Sanadhya, Founder, SignalScaler · Last updated 7 November 2026

A plain example

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.

Why do webhooks matter for B2B and SaaS teams?

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.

Using n8n? Its Webhook node has two addresses. The test URL only listens while you are testing in the editor. The production URL is registered when you publish the workflow. The default maximum payload is 16 MB, which self-hosted users can change (n8n docs, checked 7 Nov 2026). Leaving the test URL in the sending app is one of the most common reasons "the webhook stopped working".
Is it worth automating? Our free automation ROI calculator turns hours saved each week into a monthly figure, so you can decide what to build first.

How do you check a webhook?

  1. List every webhook your tools send. Most apps keep them under Settings, then Webhooks or Integrations.
  2. Confirm each URL points at a live, production workflow, not a test address or a deleted one.
  3. Send a test event and find it in the receiver's run log.
  4. Check verification. Does the receiver check a shared secret, signature or header?
  5. Check retries. If your receiver is down for an hour, does the sender try again, or is the event lost?

Common webhook mistakes

Sources

  1. n8n Docs: Webhook node (test and production URLs, payload size) (checked 7 Nov 2026)

Related terms

Terms that go with webhook

See the full B2B marketing glossary

Where to go next

Glossary · Webhook

Turn manual steps into systems that run.

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.

We use cookies to understand how visitors use this site. Analytics cookies stay off unless you say yes — see our Cookie Policy for details.

Cookie Preferences

Strictly Necessary
Required for the site to function. Always on, cannot be disabled.
Analytics
Helps us understand how visitors use the site (Google Analytics). Off by default.