<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi. A colleague and i have been experimenting and prototyping an implementation for listening for ampq notifications and kicking off mistral workflows as a mistral service. This is for a use case that is different than discussed here, but seems like it might be useful to this use case as well. The service reads a mapping file that lists the notifications to listen for and which workflow to run when that notification is received. Workflows are started using the context of the notification or, if no context is present, the mistral service context. Since we use the message’s security context you can have project scoped workflows that do different things even though they have the same name. The service also passes the notification event type and message payload to the workflow. This allows the workflow to make decisions on what to do based on the message contents and/or the type of event. We just submitted a work in progress patch to mistral: <a href="https://review.openstack.org/#/c/248813/" class="">https://review.openstack.org/#/c/248813/</a>. Please take a look at provide feedback.<br class=""><div class=""><br class=""></div><div class="">thanks,</div><div class="">todd</div></body></html>