WebHook is a user-defined HTTP call back which is triggered by specific events. When a trigger event occurs, the source site makes an HTTP request to the URL configured for the webhook. Users can also configure an event on one site to trigger an action on another site.
When a website lets users register their own URLs, they can then customize, extend and/or integrate that website with their own extensions. Webhooks, for users, is a way of receiving real-time information, rather than continually polling for information.
Webhooks are an event based output mechanism. Here are a few ways in which Webhooks can be used;
Push: receiving data in real time
It’s one of the simplest reasons to use WebHooks. As we said earlier, it will deliver data as it happens, rather than polling every few minutes to receive information. Users just have to register webhooks and they will receive data without any hassle.
Pipes: receiving data and passing it on
When a webhook receives real-time event data and triggers an event that is unrelated to the original event. For example, users can create a script that sends out an email and have it triggered by a WebHook every time they upload something of value on the website.
Plugins: processing data and giving something in return
Users can use this type of webhook to let others extend their applications. The idea is having the website/application sending out data via WebHook, also use the response to modify its own data. Basically, when you access an app/website, it will send out a WebHook to another app or site, saying ‘ someone is looking at your site’ and the site will respond with what data to show to the customer or where to redirect them.