What Is a Webhook and When to Use One in Automation
Your automation tool says a new order should trigger a message to your team, but the message shows up 15 minutes late, or the tool burns through your monthly task allowance checking for orders that never came.

Your automation tool says a new order should trigger a message to your team, but the message shows up 15 minutes late, or the tool burns through your monthly task allowance checking for orders that never came. The fix is often a webhook, a small piece of plumbing that lets one app tell another app the moment something happens instead of waiting to be asked.
This guide explains what a webhook is in plain terms, how it differs from polling, how to set one up in tools like Zapier, Make or n8n, and when you should not bother with one at all.
What is a webhook, in one paragraph
A webhook is a URL that waits for messages. You give that URL to an app, say your online shop, and tell it which events you care about, such as "new order" or "refund issued". When one of those events happens, the shop sends a short HTTP POST request to the URL with the details in a block of JSON. Whatever owns the URL, usually your automation tool, receives the data and runs the next steps. That is the whole idea. No polling, no schedule, no checking every few minutes.
Webhook vs polling and why the difference costs money
Most no-code automation tools offer two kinds of triggers. A polling trigger asks the other app "anything new?" on a timer. A webhook trigger waits until the other app announces something.
| Polling trigger | Webhook trigger | |
|---|---|---|
| Speed | Every 1 to 15 minutes depending on plan | Usually under 5 seconds |
| Checks when nothing happened | Yes, on every interval | None |
| Setup effort | Log in and pick an account | Copy a URL into the source app |
| Missed events | Rare, the tool catches up | Possible if the receiver is down |
On a free or entry plan, polling intervals of 15 minutes are common. For a booking reminder or a lead alert, that delay matters. On tools that count every operation, like Make, a poll that runs every 5 minutes uses 288 checks a day even if nothing arrives. A webhook uses one operation per real event.
How to set up a webhook step by step
The exact menus vary, but the pattern is the same in every tool I have used. Here it is with an online form as the example.
- Create the receiving end. In your automation tool, start a new workflow and pick the trigger called "Webhook", "Catch Hook" or "Custom webhook". The tool generates a unique URL, something long and random under its own domain.
- Copy that URL. Treat it like a password. Anyone who has it can send data into your workflow.
- Paste it into the source app. In the form tool, find the settings area for integrations or webhooks, paste the URL and choose the event, for example "on new submission".
- Send a test. Submit the form once with fake data. Back in the automation tool, click "listen for data" or "determine data structure" so it learns the field names.
- Map the fields. Now you can use name, email and message as variables in the next steps, such as adding a row to a spreadsheet or sending a chat message.
- Turn the workflow on and submit a second test to confirm the full path works.
The whole thing usually takes about 10 minutes the first time. If you are still deciding which automation tool to build on, our guide to choosing automation tools without overcomplicating it covers the trade-offs between the main platforms.
Reading the data a webhook sends
The first time you see a webhook payload, it looks messy. A typical order event might contain 40 or more fields, nested inside each other: customer, then address, then city. You do not need all of it. Find the five or six fields your workflow actually uses and ignore the rest. Most tools let you click through the sample data to pick fields, so you rarely need to read raw JSON.
The common advice I push back on: webhooks everywhere
You will read that webhooks are always better than polling and that you should switch every trigger you can. I disagree for small setups.
A webhook depends on both sides being available at the exact moment of the event. If your automation tool has a short outage, or you pause the workflow to edit it, many source apps send the event once, maybe retry a few times over an hour, and then give up. That order simply never reaches your spreadsheet. A polling trigger, by contrast, picks up anything it missed on the next run because it looks at the full list of recent items.
So my rule is this. Use a webhook when speed changes the outcome: a lead that goes cold in an hour, a missed call alert, a booking confirmation. Keep polling for things where a 15 minute delay is harmless and completeness matters more, such as a daily sales summary or filing receipts into a spreadsheet. A weekly check that totals in the source app match totals in your sheet catches any gaps either way.
Keeping a webhook safe and reliable
A webhook URL is a public door, so a few habits are worth building early.
- Do not post the URL anywhere public, including screenshots in help forums. Regenerate it if it leaks.
- Use the signing secret if offered. Many apps, including Stripe and Shopify, sign each request with a secret key. Tools like n8n can verify that signature so fake requests are rejected.
- Add a filter step right after the trigger that stops the run if a required field, like an email address, is empty.
- Turn on error notifications in your automation tool so a failed run sends you an email rather than failing silently.
- Write down where each webhook lives. Six months later you will not remember which form posts to which workflow. A plain list with the source app, event and workflow name is enough.
That last point matters more than it sounds. Every webhook is one more connection to keep track of, which is part of the hidden cost of too many tools in a small business.
Frequently asked questions
Is a webhook the same as an API?
Not quite. An API is a set of addresses you call when you want information or want to make a change. A webhook works the other way around: the app calls you when something happens. Many apps offer both, and automation tools use both behind the scenes.
Do I need to know how to code to use a webhook?
No. In Zapier, Make, n8n and similar tools, webhooks are a built-in trigger, and the setup is copying and pasting a URL. Coding only becomes useful if you want to verify signatures by hand or build your own receiver.
What happens if a webhook fails?
It depends on the sending app. Most retry a few times over minutes or hours, then stop and may show the failure in a log. That is why an error alert in your automation tool and an occasional check against the source data are worth setting up.
More in Automation Tools
Automation Tools
Automation Tool Pricing: Tasks vs Operations Explained
A reader wrote to me in September because she had signed up for a plan with 750 tasks a month, built two small workflows, and...
Automation Tools
Choosing a No Code Database for Small Team Automations
Every automation I have helped someone build eventually hits the same wall.
Automation Tools
Scheduling Link Tools and How to Pick One Without Overpaying
The email thread started on Monday. "Does Thursday work?" "Thursday is tight, how about Friday morning?" "Friday I can do after...