What Is a Webhook? A Plain-English Explanation for Automation Builders

A practical field guide from Automation Ace.

What Is a Webhook? A Plain-English Explanation for Automation Builders

A webhook is an automated notification that one app sends to another app when something happens. Instead of your automation tool repeatedly asking "did anything change?" (polling), the source app proactively sends a message to a URL you provide the moment the event occurs. Think of it as the difference between calling a restaurant every 10 minutes to ask if your table is ready, and giving them your phone number so they can call you the moment it is.

Webhooks are the mechanism behind every "instant" trigger in Zapier and Make. When Stripe sends a payment confirmation, when Typeform delivers a completed survey response, when Shopify notifies you of a new order — these are all webhook calls. The source app sends an HTTP POST request to a unique URL that your automation tool provides, containing a JSON payload with the event data. Your automation tool receives that payload and immediately kicks off the workflow.

How a Webhook Actually Works

The technical flow is straightforward: your automation tool (Zapier or Make) generates a unique webhook URL — a web address that only your workflow listens to. You copy that URL and paste it into the source app's webhook or notification settings. From that moment on, every time the specified event occurs in the source app, it sends an HTTP POST request to your URL carrying a JSON body with the event details. Your automation tool receives the request, parses the JSON, and makes the data available as fields you can map into subsequent steps.

The JSON payload is the data package that travels with the webhook call. It is a structured set of key-value pairs that describes the event. A Stripe payment webhook might include fields like amount, currency, customer_email, payment_status, and invoice_id. Your job as the automation builder is to map those fields to the right places in your workflow. Understanding how to read and use JSON payloads is the single most important skill for working with webhooks — for more detail on this, see the article on webhook and API integration consulting. For a comparison of webhooks with traditional API calls and how each fits into automation workflows, see APIs vs. webhooks explained.

Webhooks vs. Polling: When Speed Matters

Standard Zapier triggers that do not use webhooks work by polling — Zapier checks the source app every 1–15 minutes (depending on your plan) for new records or changes. This means there can be up to a 15-minute delay between an event happening and your Zap running. For many workflows, this delay is acceptable. For others — like responding to a new lead or confirming a payment — a 15-minute delay is too long.

Webhook-based (instant) triggers eliminate that delay. The moment the event occurs in the source app, the webhook fires and your automation runs within seconds. The tradeoff is that webhook triggers require the source app to support outgoing webhooks, and they require a small amount of configuration in the source app to point the webhook at your Zapier URL. Not every app supports webhooks — for those that do not, Zapier's polling triggers remain the only option. See the comparison article on Zapier polling triggers vs. instant triggers for a detailed breakdown of when each approach makes sense.

For a deeper look at timing, polling, and reconciliation, see push vs pull automation and what webhooks can do that APIs can't.

Common Webhook Use Cases in Business Automation

• Payment confirmation routing: Stripe fires a webhook when a payment succeeds. Zapier or Make receives the payload, extracts the customer and invoice data, updates the CRM, sends a receipt, and creates a fulfillment task — all within seconds of the charge completing.
• Form submission processing: A Typeform or Webflow form sends a webhook on each submission. The automation receives the response data, creates a lead record, routes the lead based on answers, and sends a confirmation email.
• CRM event triggers: HubSpot, Salesforce, and Pipedrive all support outgoing webhooks for deal stage changes, contact updates, and new records — enabling near-real-time downstream automation.
• Custom app integration: If you have a custom internal app or a niche tool that is not in Zapier's app directory, it can almost certainly send webhooks to Zapier's generic "Webhooks by Zapier" trigger, making it compatible with the entire Zapier ecosystem.

A webhook is not a feature you configure once and forget. It is a live connection between two systems. If the source app changes its webhook payload structure, your automation receives different fields than expected — and may break silently. Monitor your webhook-based automations and document the payload structure so you know what to expect.

Prefer code? You can also receive webhooks with Cloudflare Workers.

Setting Up a Webhook in Zapier

In Zapier, the "Webhooks by Zapier" app provides both a "Catch Hook" trigger (receives incoming webhooks) and a "GET/POST/PUT" action (sends outgoing requests to external APIs). To set up a webhook trigger: create a new Zap, choose "Webhooks by Zapier" as the trigger app, select "Catch Hook," copy the generated webhook URL, and paste it into the source app's webhook settings. Then send a test event from the source app to populate the trigger data, and continue building the rest of your Zap. For Make.com webhook patterns, see the article on Make.com webhook automation examples.