HTTP Custom Action in SharePoint and OneDrive

This seems a little bit of a stretch in my opinion for a basic function.  Especially when we already make significant investments in higher tiered licensing packages like E5.  I'm all for monetizing services, but it just seems like there are better ways to distinguish Flow services and capabilities. 

I've been working to kill a 3rd party that provides similar capabilities, but this just wiped that out.  To give the same capabilities (just a silly HTTP call for workflows) to our users would cause us to quadruple the investment that we are making in our 3rd party tool.  Or maybe I'll dust off some SPD2013 capabilities for a while when this goes into effect.

I'd rather see it take on something like an Azure Function type model where you pay for what you use other than forcing users to pay for a "Cable" model of 100's of "premium" channels that you'll never watch when you only really want the one channel.

Also, you kinda already did a good job of "distinguishing" between services if you look at your pricing page https://flow.microsoft.com/en-us/pricing/

Dont get greedy.