It's 11:47 PM. Karim just sold 14 orders today. And right now he's copying them. One by one. Into a spreadsheet.
Meanwhile, Amine's phone buzzed three times tonight. Not from customers. From his store. "Order #2514 — delivered." "Order #2515 — shipped." "2 new orders before midnight."
Amine was asleep.
Both men run e-commerce stores in Algeria. Same platforms, same products, same customers. The only difference? Amine's store talks to him. Karim's store makes him do the talking.
That difference has a name: webhooks. And it's the reason one back office runs itself while the other runs a man's whole life.
A webhook is a tiny messenger your store sends the moment something happens. Order created? Your store taps your automation tool on the shoulder. Order cancelled? Same tap, different message. The new DZBuild Webhooks add-on does exactly this — it pushes every order event to n8n, Make, Zapier, or your own server, the second it happens.
Below: what webhooks actually are, the nine events your store can send, and four ways to use them. One of those four pays for the whole plan by Friday. We'll get there.
⚙️ What a Webhook Actually Is (60 Seconds, No Jargon)
Imagine your store is a restaurant kitchen and your automation tool is the waiter. Without webhooks, the waiter stands outside, peeking through the window every few minutes: "Anything ready?" Mostly no. Sometimes yes — but late.
With webhooks, the kitchen rings a bell the moment a dish is ready. The waiter only moves when there's something to carry.
Same thing in e-commerce:
- The old way: you (or your tool) poll the store, refresh the dashboard, re-check the orders page.
- The webhook way: the store rings the bell itself, instantly, with the full order data attached.
No delay. No missed orders. No refreshing at midnight. Just events, delivered straight to the tools you already use.
📊 Why Automation Wins (The Numbers Are Rude)
If you're still skeptical about automation, the data is not polite about it:
- 94% of workers say repetitive tasks eat their day. 88% say automation makes them more productive (Zapier).
- Small businesses that automate save 10–15 hours per employee, per week. That's a whole working day — returned. Twice.
- Automation adopters grow 2.1–2.4x faster than competitors who do everything by hand (McKinsey).
- The typical small business spends $347/month on automation tools and saves $14,200 in labor and error costs. A 41:1 return.
In Algeria, the stakes are even higher. COD rejections, WhatsApp-first customers, orders arriving at all hours. Your store already lives on your phone. The real question isn't "does automation help?" It's "who answers the customer at 11:47 PM — you, or the machine?"
Look at what changes, moment by moment:
| The moment | Without webhooks | With webhooks |
|---|
| 11:47 PM — an order lands | You're asleep. The customer waits. | WhatsApp confirmation goes out instantly |
| Morning | You copy 20 orders into sheets by hand | The sheet already has them |
| An order ships | The customer calls: "where is my parcel?" | Tracking number is already in their WhatsApp |
| A customer's 5th order arrives | Nobody notices | A VIP message fires automatically |
→ Start your free 3-day trial and activate Webhooks tonight — your first automated flow can be live in under an hour.
🔔 The Nine Events Your Store Can Send
DZBuild fires a webhook at every step of an order's life. Here's the full menu — and what each event lets you build:
| Event | Fires when | Your automation could… |
|---|
order.created | A customer places an order | Send a WhatsApp confirmation within seconds |
order.confirmed | You (or your team) confirm it | Alert the courier, update the stock sheet |
order.processing | The order is being prepared | Create a packing task in your team board |
order.shipped | It's out the door | Send the tracking number and delivery company |
order.delivered | The parcel was accepted | Ask for a review, add loyalty points |
order.cancelled | It was cancelled or rejected | Add the customer to a win-back list, flag the address |
order.returned | It came back | Start the recovery script, log the reason |
webhook.verify | You connect a new endpoint | Prove your URL is alive (automatic handshake) |
webhook.test | You press the test button | Confirm everything works before real orders |
Seven events follow an order through its whole life. The last two exist so you never have to wonder "is this thing even on?"
And each event carries the full order payload: order number, status, payment and delivery type, customer name and phone, wilaya, commune, subtotal, shipping, discount, total, promo code, tracking number, delivery company — plus every item in the cart.
That's not a notification. That's a database row, delivered to your door.
→ Activate Webhooks from your DZBuild dashboard — it takes about two minutes.
📱 Automation Idea #1: WhatsApp on Autopilot
Algerian customers live on WhatsApp. They expect answers in minutes, not hours. And the numbers justify it: WhatsApp messages get 95–98% open rates — versus 20–25% for email.
Here's what that means with webhooks. The moment order.created fires, your automation tool messages the customer:
"Hi Karima 👋 Order #2514 is confirmed. We'll call you soon to arrange delivery."
Then order.shipped fires — and a second message goes out with the tracking number and delivery company. Then order.delivered fires — a thank-you, plus a gentle request for a review.
Three messages. Zero typing. The customer feels looked after from the first second, and you didn't lift a finger. That's the whole idea: webhooks don't replace your customer service. They replace the boring 80% of it.
📈 Automation Idea #2: The Spreadsheet That Fills Itself
Every Algerian seller knows the ritual. Open the orders page. Copy the name. Copy the phone. Paste the wilaya. Paste the total. Multiply by 20 orders. Every single day.
With the DZBuild Webhooks add-on, your Google Sheet fills itself. Every order.created event lands as a new row: name, phone, wilaya, commune, total, payment type. Your accounting sheet. Your COD follow-up sheet. Your courier manifest. All updated the second the order happens — while you're having lunch.
The 20-minute daily routine becomes a 20-minute weekly review. You don't do less work. You do the part that actually needs a human.
🧠 Automation Idea #3: Your CRM, Without Typing
Retention is where Algerian stores win or die — keeping a customer costs 5–25x less than finding a new one. But most retention systems fail for one boring reason: nobody has time to update them.
Webhooks update them for you:
- 🔔
order.delivered → your loyalty sheet adds points. A customer's 5th order triggers a "VIP" WhatsApp broadcast automatically.
- 🛑
order.cancelled → the customer lands on your win-back list, rejection reason logged. Three days later, a gentle re-contact goes out — only to the right people.
- 📦
order.returned → the address gets flagged, the refund script starts, and the courier list gets updated. No more shipping twice to a serial rejecter.
The list you used to maintain at 2 AM now maintains itself. DZBuild sends the event. Your tool does the remembering.
🚀 Automation Idea #4: The Boss's Pocket
This one's the fun one. Your phone buzzing with everything that matters — and silent about everything that doesn't.
- 💰 Every sale → a Telegram or push notification: "2,400 DZD — new order in Algiers." A tiny dopamine hit. And an early fraud radar.
- 📋 Every
order.shipped → a task appears in your team's board: "Call the courier, confirm pickup."
- 📊 Every morning at 9 AM → one message with yesterday's totals: "23 orders, 187,500 DZD, 2 cancellations." Computed from the sheet that filled itself.
You stop opening the dashboard ten times a day. DZBuild opens you instead. That's the shift, and you feel it in the first week.
🛡️ Security: How DZBuild Keeps the Pipe Trustworthy
"Just POST my order data to some random URL" sounds terrifying. Fair. Here's how the add-on handles it — no trust required:
- Every request is signed. Three headers travel with each event:
X-DZ-Token, X-DZ-Timestamp, and X-DZ-Signature — an HMAC-SHA256 hash built from your secret, the timestamp, and the raw body. Your tool verifies the sender. A fake request fails the check.
- Stale events get rejected. The docs recommend refusing anything older than 5 minutes. Replay attacks: dead.
- Handshake first. A new endpoint receives nothing real until it answers a
webhook.verify event with HTTP 200. Only then does it flip from Pending verification to verified.
- Your secret appears once. Lose it? Regenerate it — and the old one stops working immediately.
In plain words: you're not poking a hole in your store. You're installing a door that only your automation tool has a key to.
🔁 Reliability: Built for 3 AM, Not for Demos
Automations die at 3 AM. That's a law of the universe. So DZBuild's delivery pipeline assumes failure and plans around it:
- Five retries, growing gaps. Roughly 1 minute, then 5 minutes, 30 minutes, 2 hours, 12 hours. Your server hiccups — the event just tries again.
- Auto-disable after 10 straight failures. A dead endpoint gets switched off instead of silently losing orders forever. Fix the URL, re-enable, and the failure counter resets.
- A delivery log of the last 50 events per endpoint. Status, attempts, HTTP code, error, date. When something fails, you see exactly where.
That's the difference between a toy and a tool. The toy works when everything is fine. The tool tells you when it isn't. Want to see it for yourself? The whole thing is free to try for 3 days — build one flow and watch the delivery log light up.
→ Try DZBuild Webhooks free — no credit card needed for the trial
🏁 Setup: From Zero to Automating in Five Steps
- Activate the add-on: Dashboard → Add-ons → Webhooks. (Needs the Unlimited plan or higher — you can start with the free trial and upgrade in one click.)
- In n8n, Make, or Zapier, create a Webhook trigger and copy its URL.
- Paste the URL into DZBuild, tick your events ("New order" comes pre-selected), and click Add.
- Save the signing secret shown on screen. Once. Seriously — it appears exactly once.
- Wait for the handshake. DZBuild sends
webhook.verify; your URL answers 200; you're verified. Then hit Send test event and watch it land.
n8n users get a bonus: the "Copy verification code (advanced)" button drops a ready-made Code node into n8n with your secret pre-filled — signature verification without writing it by hand.
Never touched n8n? It's a free, open-source automation tool that runs on your own machine. Make and Zapier are the same idea in the cloud. You don't need to be a developer. You need one afternoon.
💰 Plans & Limits: What You Get
| Plan | Price (DZD/month) | Webhooks |
|---|
| Free | 0 | Locked |
| Pro | 1,000 | Locked |
| Unlimited | 2,500 | 1 endpoint |
| Enterprise | 5,500 | Up to 3 endpoints |
One endpoint already covers everything in this post — all seven order events go to a single URL. Enterprise adds three, for merchants who run separate tools for sales, support, and accounting.
An honest note, too: add-ons check your plan at activation. Upgrade, activate, build — and even if you downgrade later, the add-on keeps running. DZBuild's 3-day trial starts you on the full Pro experience, one click from Unlimited.
🎯 The Math: A 2,500 DZD Employee Who Never Sleeps
Remember Karim and Amine from the top? Let's close their story.
Karim spends two hours a day on copy-paste and follow-up. That's 60 hours a month — 40,000–60,000 DZD of his own time, spent on work a machine does better and faster.
Amine pays 2,500 DZD a month for Unlimited. His webhooks send the WhatsApp messages, fill the sheet, update the CRM, and buzz his pocket. Those same 60 hours? They go to products, ads, and suppliers.
The 94% figure from earlier was never about big companies. It's about Karim. It's about you. The question was never "can your store automate?" It's "when do you stop being the machine?"
Build the store that works while you sleep.
The DZBuild Webhooks add-on turns every order event into an automatic action — WhatsApp messages, CRM updates, a back office that runs itself. → Start your free 3-day trial and wire up your first automation today.
