A really good workflow engine could really improve many corporations in my opinion. Yes, there are solutions like MS Flow (renamed now) and IFTTT, but I think b

A really good workflow engine could really improve many corporations in my opinion. Yes, there are solutions like MS Flow (renamed now) and IFTTT, but I think both services are lacking, especially for debugging problems and their cloud nature is heavily annoying and is no good fit for many corporations. For basic stuff like SIP phone rings and isn't answered -> mail to XY. New, urgent QA process -> inform all relevant participants... there are unlimited use cases. Workflow engines need to be integrated with on premise user management like AD services to really shine. Cloud solutions are penalized here or need to interface Office Online. Of course there are better solutions available, but MS is widespread in this landscape. No code workflows can be really good and dependable. That does NOT mean custom code should be excluded. MS made a custom HTTP request a "premium" feature in Flow. Of course the product can only fail with this approach.