What is Webhook?
An automatic notification sent when something happens. Like your app texting another app: 'Hey! Something happened! Do your thing!'
A webhook is a small automatic message that one system sends to another the moment something happens. Instead of constantly asking "has anything new happened?", the system knocks on your door by itself and says "it happened now — do your thing".
Think of waiting for a parcel. Without a webhook you have to go to the letterbox every five minutes to check. With a webhook, the courier rings your doorbell the moment the parcel arrives. You avoid running back and forth, and you get the information exactly when it matters.
Technically, a webhook is a URL (a web address) that you give to another system. When a particular event occurs — for example a customer pays — that system automatically sends a packet of information to your address, and your application can react straight away.
Why are webhooks important for your business?
Webhooks let your systems talk to each other automatically, without anyone having to click. That saves time, reduces human error, and makes things happen in real time instead of after the fact.
For you as a business owner, it means a payment, a new booking, or a completed form can start the right process immediately — a receipt is sent, stock is updated, a salesperson gets a notification. All without anyone watching manually.
Webhooks in practice
Say you run an online shop. When a customer pays via Stripe, Stripe sends a webhook to your system. Your shop gets the signal "payment complete" and can automatically send an order confirmation, reduce stock, and notify your packing team.
Another common example: when someone fills in the contact form on your site, a webhook can immediately add them to your CRM and send a Slack message to the sales team. No manual steps, no delay.
Common questions about Webhook
What does webhook mean?
A webhook is an automatic message one system sends to another the moment something happens. It is like one app knocking on another's door to say something important just occurred.
What is the difference between a webhook and an API?
With a regular API you ask a system for data when you need it. A webhook is the opposite: the system contacts you on its own when something happens. An API is you calling; a webhook is being called.
Are webhooks secure?
Yes, when set up correctly. You usually verify that the message really came from the right sender using a secret key, and everything is sent over encrypted HTTPS. That stops outsiders sending fake notifications.
Related terms
Serverless
There are still servers — you just do not need to worry about them. Someone else has the headache. You have the app.
API
Application Programming Interface. Think of a waiter who takes your order (request) and brings the food (data) from the kitchen (server).
Cache
Stored data that loads instantly instead of being fetched again. Often the reason your site feels fast — or why changes do not show up.
CDN
Content Delivery Network — copies of your site spread around the world so it loads quickly wherever your visitors are.
Cloud
Someone else's computers. Servers in massive data centres you rent instead of own — AWS, Google Cloud, Azure.
Database
Where all your data lives — users, orders, everything. Lose the database and you lose everything, which is why we back it up.