They are very simple to set up – all you need to do is provide a URL, select when and where you want that URL to receive data about events on your list, and it will be sent to the URL you have specified as the events take place
Wikipedia defines a WebHook as a “method of augmenting or altering the behaviour of a web page, or web application, with custom callbacks. These callbacks may be maintained, modified, and managed by third-party users and developers who may not necessarily be affiliated with the originating website or application”.
Here are some examples of how WebHooks function:
- Each time another blogger reblogs one of your posts, be informed about offshoot discussions on other blogs that emanated from your original post so that you can share on them yourself as well as receive more inbound links to your blog/website from the discussion
- set ‘trigger word(s)’. If a post or comment is made that contains one or more triggers such as name, website, genre, etc., the WebHook notifies the user
WebHooks are simple to implement and can be integrated and implemented everywhere. You can point a WebHook at a site that will call other WebHooks – it might then process the data, record it, redistribute it to multiple other WebHooks.
- Using Webhooks with IFTTT.com (marcus-povey.co.uk)
- Why content shareability matters (thecontentlab.icrossing.com)
- Developers Want Realtime (leggetter.co.uk)