Webhooks, the most fundamental building block
Once you understand webhooks, you understand modern automation. Without them, nothing works.
What a webhook is
A URL on your side, to which another system sends a message when something happens.
Example: someone buys at Stripe. Stripe wants to let you know. Instead of you constantly polling "has anyone just bought?", you configure a webhook: "When someone buys, send me a POST message at https://myapp.com/api/stripe-webhook". Stripe then calls you on its own, you don't have to poll.
The difference from an API
An API is a door you knock on. You ask: "Give me the last 10 orders." The system answers.
A webhook is the other way around: the other system knocks on your door. "There was an order, here are the details." You don't ask anything.
API = pull. Webhook = push.
Why this matters
Before webhooks, automations had to "poll", asking every 5 minutes whether something changed. That was slow, expensive and unreliable.
With webhooks everything happens in real time. New order, instant notification. New email, instant action. The difference is tangible.
How Zapier/n8n use webhooks
Both Zapier and n8n have "Webhook Trigger" nodes. They work like this:
- You create a new workflow with webhook trigger.
- The system gives you a unique URL (e.g. https://hooks.zapier.com/abc123...).
- You enter that URL in the other system as "webhook endpoint" (Stripe, Brevo, GitHub, somewhere).
- Each time the other system triggers, your workflow starts.
What you need to test
Reliability. Webhooks are sometimes lost. Good systems have retry logic.
Security. Webhooks are public URLs. If someone guesses or intercepts them, they can trigger your workflow. Hence: webhook secrets. The other system signs the message, you verify the signature is valid.
Payload format. JSON is the standard. But not every system sends data the same way. You have to understand the structure.
Minimal example: Stripe purchase, Slack message
- n8n: new workflow, trigger = webhook, copy URL.
- Stripe: dashboard, webhooks, add endpoint, paste URL, enable event "checkout.session.completed".
- Make a test purchase.
- n8n shows you the event. You see customer name, amount, product.
- Add a second node: Slack, "Post Message", with dynamic variables from the webhook payload.
- Go live.
That's 15 minutes of work. And scales from 1 to 10,000 purchases without extra effort.
Going further
With these four lessons you have the basics. Anyone who wants to go deeper now goes to Level 4, where memory, MCP and the leap to a real AI operator come in.