With QBank's updated webhooks, the integration possibilities have become even better and smarter. By enabling multiple tools to communicate and share data you can build automatized workflows throughout your digital assets lifecycles. Learn how it works!
Webhooks are a common way for different applications to communicate with each other. Not only does it enable communication, but it allows one system to notify another of an event that has taken place in the respective system. Even better, the other system can answer. Webhooks can be set up from one system to another, or it can be set up for both systems to enabling communication in both directions.
In short, you can describe a webhook as a signal that is sent whenever a specific event occurs in the system, which should cause a related response in the system that receives the signal. QBank implements the standard webhook features a long with a few QBank adaptions. Webhooks, as the name implies, work over the web, so the applications must be able to send and/or receive HTTP(S) communication.
When do you need Webhooks?
To build an efficient digital asset lifecycle, integrations are necessary. Thanks to QBank being a scalable solution, you can add integrations as you go, which enables growing with your DAM tool. Integrations need to be efficient, automatized and smart, and that’s when webhooks becomes relevant. Whenever you want to build an integration between systems that require constant synchronisation or quick updates, the only practical solution is to use webhooks. If another application wants to know whenever an asset is uploaded in QBank, the only reliable solution for this is to have QBank tell the application whenever that happens.
Are webhooks always the best solution?
An alternative method for applications to communicate is to use "polling", which basically means that an application asks another application if a certain event has occurred (in opposite to being told when it happened). There are certain times where polling is an alternative to webhooks, for example if an application is interested in knowing how many assets were uploaded to QBank in the last 24 hours. It might then be better to ask (polling) QBank for this information once every 24 hours, instead of having QBank (through a webhook) inform the system each time an asset is uploaded.
Talk to a DAM expert about it!
If you would like a demonstration of QBank or more in-depth questions about webhooks, you are welcome to request a demo with a DAM Expert.
