Last time I explained APIs — the restaurant waiter that carries your order to the kitchen. But APIs have a problem: you have to keep asking.
“Is my food ready?”
“Is my food ready?”
“How about now?”
That’s annoying. What if the waiter just came to you when the food was ready?
That’s a webhook.
APIs vs webhooks: the difference
An API is like checking your mailbox. You walk outside. You look inside. Nothing yet. You come back inside. You check again 10 minutes later. Still nothing. You check again. Finally, there’s mail.
A webhook is like getting a notification on your phone when mail arrives. You don’t check. You get told.
Same result — you get your mail. But one wastes your time checking, and the other just tells you when it’s ready.
API = you pull information.
Webhook = information is pushed to you.
How webhooks work in real life
You already use webhooks every day without knowing it.
Your bank app: When you make a purchase, your bank sends a webhook to your phone — that’s the push notification you get instantly. Your phone didn’t ask “did I spend money?” Your bank told it.
Stripe payments: When someone pays you, Stripe sends a webhook to your system. Your system updates the order status. Nobody has to check Stripe every 5 seconds to see if a payment went through.
Shopify orders: When someone places an order, Shopify sends a webhook to your email service, your shipping service, and your accounting software. All at once. Automatically.
GitHub: When someone pushes code, GitHub sends webhooks to your CI/CD pipeline, your Slack channel, and your project management tool.
Every time you get a notification, that’s probably a webhook.
The technical part (don’t worry, it’s simple)
A webhook is just a URL that your app listens to. When an event happens, the sending app sends data to that URL.
Here’s what it looks like:
- You tell App A: “When X happens, send data to this URL: https://your-app.com/webhook"
- When X happens, App A sends a POST request to that URL
- Your app receives the data and does something with it
That’s it. No polling. No checking. No wasted time.
The “payload” is the data that gets sent. Usually JSON — a structured format that your app can read. For example, a payment webhook might send:
| |
Your app reads this and knows exactly what happened. No need to call an API to check.
Why webhooks matter for no-code tools
This is where it gets good.
Zapier uses webhooks to connect apps. When something happens in App A, Zapier receives a webhook, then triggers an action in App B. That’s how you automate things without code.
Make (formerly Integromat) works the same way. Webhooks are the trigger that starts your automation.
n8n — the open-source automation tool — uses webhooks as the starting point for most workflows.
Every automation you’ve ever seen — “when someone fills out a form, send them an email and add them to a spreadsheet” — starts with a webhook.
Without webhooks, there is no automation.
Real examples that’ll save you time
Example 1: New subscriber → welcome email
Someone signs up on your website → webhook fires → email service sends welcome email → CRM adds contact → spreadsheet logs the signup. All automatic. No human involved.
Example 2: New sale → update inventory
Someone buys a product → webhook fires → inventory system updates stock → accounting software logs revenue → shipping system creates label. Done in seconds.
Example 3: AI tool finishes → notify you
You send a document to an AI summarizer → it processes for 5 minutes → webhook fires when done → you get a Slack notification with the summary. No need to keep checking if it’s done.
Example 4: Form submission → AI response
Someone submits a support question → webhook fires → AI generates a response → response gets sent back to the customer. All within seconds.
Common webhook platforms (no code required)
Zapier Webhooks: The easiest way to start. Create a “Catch Hook” trigger, get a unique URL, paste it into the sending app. Zapier handles the rest. Free tier available.
Make (Integromat): More powerful than Zapier, slightly more complex. Great for multi-step automations. Free tier with 1,000 operations/month.
n8n: Open-source and self-hostable. If you’re technical, this gives you full control. Free if you host it yourself.
IFTTT: Simplest option. Good for personal automations (turn on lights when you arrive home, etc.). Free tier available.
The 5-minute webhook setup
Here’s how to set up your first webhook in Zapier:
- Go to Zapier → Create Zap
- Choose “Webhooks by Zapier” as the trigger
- Select “Catch Hook” → Continue
- Zapier gives you a unique URL — copy it
- Go to the app that sends the webhook (Stripe, Shopify, Typeform, etc.)
- Find “Webhooks” or “Integrations” in settings
- Paste the Zapier URL
- Test it — trigger an event in the sending app
- Zapier receives the data
- Add your action (send email, update spreadsheet, etc.)
Done. You’ve automated something without writing a single line of code.
What webhooks won’t do
They’re not real-time. Most webhooks fire within seconds, but there can be delays. If you need sub-second timing, you need something different (like WebSockets).
They can fail. If your receiving server is down, the webhook fails. Most platforms retry a few times, but you need to handle failures gracefully.
They’re one-way. Webhooks send data one way. If you need a back-and-forth conversation, you need an API.
They need a URL. Your app needs to be accessible from the internet. Local servers can’t receive webhooks unless you use a tunneling service like ngrok.
The bottom line
APIs are how you ask for information. Webhooks are how you get notified when something happens.
If you’re building any kind of automation — whether with Zapier, Make, n8n, or anything else — you’re using webhooks. They’re the invisible plumbing that makes everything work.
And now you know how the plumbing works.
What’s the most useful automation you’ve built? I’d love to hear about it.