Power Platform Community Forum Thread Details

This is a great start and I'm looking forward to seeing what you do with data from each Action.

It would be tempting to turn this into a full-blown programming language and I'm pretty sure you're not aiming at this market. I'm keen to see how you represent 'data' extracted from Actions and how this can be used in later steps.

For example, for our company we want to create a flow that integrates receiving an email from a supplier (in this case a lead for our office space), extract the relavent details (Opportunity Name, Timeframe, Contact Phone/Email), send an SMS to the sales person, create a CRM Opportunity, Update a spreadsheet (for lead tracking) and send an introduction email.

There are lots of ways to do this, but most require deep understanding/progremming of CRM or some other toolset.

If we can use Flow for this, then we can create our own processes, integrating systems without having to get our programmers involved - releasing them for the heavy lifting work.

Categories:

Using connectors

Data manipulation/parsing is not super easy to do in Flow right now. I believe some simple "transform" actions may be on the horizon, but that would largely be mapping one object onto another. Extracting an object from an email would need to be accomplished by code running somewhere.

But given your scenario, this would be the only step that requires heavy-lifting from some programmers. If you'd interested in pursuing it, I'd start by looking at custom API support here: https://azure.microsoft.com/en-us/documentation/articles/powerapps-register-custom-api/

Basically, a lightweight web endpoint would need to be stood up that can take an email as input and return the fields needed for the rest of the Flow. You likely wouldn't even need to worry about authentication/authorization on this endpoint as it wouldn't need to persist any information.