Webhook

What it is

With an ordinary API, your system has to ask: “Any new orders?” — every minute, every hour — and most of the time the answer is no. A webhook turns that around. You give the other system a web address, and whenever the event you care about occurs, it sends a short message to that address with the details: which order, what amount, from whom. Your side receives it and does whatever comes next.

Almost every modern service offers webhooks: payment gateways confirm a payment, shops announce a new order, WhatsApp Business delivers an incoming message, form tools pass on a submission, and workflow platforms such as n8n both receive and send them. A webhook is not a full integration by itself; it is the trigger that starts one.

Why it matters for a growing business

Webhooks are what make automation feel instant. A customer pays through bKash, Nagad or a card gateway and the order is confirmed and the warehouse notified in the same minute — not when someone next refreshes a screen. An incoming WhatsApp enquiry can create a lead, assign it to a salesperson and send an acknowledgement before the customer has put the phone down.

They also reduce load and cost: instead of a system polling another thousands of times a day to find a handful of changes, it receives exactly the events that matter. The one discipline they require is handling failure — if the receiver is down when the message arrives, the sender should retry, and the receiver should recognise duplicates.

How AutoProbaho uses it

AutoProbaho uses webhooks as the triggers of most automations it builds: payment confirmations updating an order in a custom ERP, e-commerce orders flowing into stock and dispatch, WhatsApp and Facebook messages opening tickets or leads, and form submissions starting an approval. Every webhook endpoint is secured, logged and monitored so that a missed event is noticed and replayed rather than lost.