Webhook
Automatic alert between systems
A webhook is a way for one system to automatically notify another the moment a certain event occurs, such as a new order or payment. Instead of constant polling, the system sends the data itself, in real time. This lets applications connect and trigger actions in each other.
How a webhook works
With a webhook, you set an address (URL) in one system to which it should send messages. When a watched event occurs, the system immediately sends data about what happened to that address. The receiving application processes the message and carries out the linked action, for example creating a record or sending a notification.
A webhook is often mentioned alongside an API, but it works the other way around. With a classic API, the application asks and waits for an answer. A webhook, by contrast, sends data on its own the moment there is something to report. It is therefore also called a “reverse API” and fits anywhere you need to react in real time.
What webhooks are used for
Webhooks are the glue that connects individual tools behind the scenes. Thanks to them, systems hand off information automatically and without manual re-entry. That saves time, reduces errors, and makes it possible to build smooth, automated processes across different applications.
In practice you’ll meet them, for example, with payment gateways that notify an e-shop after payment, or when connecting orders with accounting or a CRM. A webhook triggers the reaction exactly when the event happens, so everything follows on immediately.
- A payment gateway notifies the e-shop of a successful payment.
- A new order automatically creates a record in the CRM.
- A submitted form triggers an email or notification.
- A change in one tool is reflected in another in real time.
Want to connect and automate your systems?
See our custom developmentFrequently asked questions
What is the difference between a webhook and an API?
With an API, the application requests the data itself when it needs it. A webhook works the other way around: it sends the data automatically the moment an event occurs. An API is therefore suited to requesting information, a webhook to reacting instantly to a change.
Do I need a developer for a webhook?
On the side that receives and processes the webhook, yes; you usually need to set up a place for the data to arrive. Many ready-made tools and automation platforms, however, support webhooks and can be connected without extensive development.
Is the data sent through a webhook secure?
When set up correctly, yes. The data travels over a secure HTTPS connection, and the receiving end can be protected with verification so only an authorized system accepts the message. Security depends on the quality of the implementation on both sides.