Hi ​@CodyH, great to see you in the Community! Thank you for taking the time to ask your question. I am looking into what we might be able to share in terms of real life examples. In the meantime I hope this is helpful. There's more than just uploads.  Events can be sent when assets are edited (metaproperties/versions), pre-archived, archived, or deleted.

Hi ​@CodyH,

A real life example could be a use case that we just implemented for one of our customers using Bynder. 

1. When metadata is changed on an asset within Bynder, that fires a webhook (SNS message) to a defined endpoint with Json data about the asset in its latest state.
2. The endpoint in this case is our own “SNS Proxy” that we have built in order to filter out irrelevant messages to the receiving PIM system.
3. So, in this case, if the asset metadata contains a value in the metaproperty field “Article Number”, the “SNS Proxy” forwards the webhook to the PIM system (Inriver) that either creates or updates an image resource entity connected to that particular article/product.
4. Vice versa, the PIM could fire a webhook to a middleware whenever metadata is applied on an article, thus enabling the DAM to subscribe to product related metadata based on an article number, avoiding that people manually applies metadata on the same assets in two different systems.  

Just to mention a recent use case.

Regards,

Kare