Introduction to Webhooks

Webhooks are triggered whenever an item is created, updated, or cloned in a specific workspace in Fusion Manage. Once triggered, the information about the item, its URN and descriptor, is sent to an external for further processing. This tutorial uses Zapier, but you’re free to use whatever tool or service that suits you. IFTTT is another popular service.

Put simply, from Wikipedia “A webhook in web development is 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. The term "webhook" was coined by Jeff Lindsay in 2007 from the computer programming term hook.”

The benefits of creating webhooks include:

• Communicating changes to external application. Some integrations rely on pooling Fusion Manage when looking for changes on items or workspaces. Changes such as new items being created, updated, or certain workflow transitions being performed. With webhooks, you can just respond to those changes as needed, as events will be broadcast to your integration.
• Sending out notifications based on events. Depending on the integration, you can create a notification system by e-mail, or to post messages on Slack, or integrate with social media, internal or external. Zapier is powerful in this regard.
• Reducing the amount of scripting to send out events. In some cases, scripting is using to push updated to other s, which is triggered for all items, unconditionally. Since webhooks are only triggered as needed, they’re much faster and less intensive on the system.