cancel
Showing results for 
Search instead for 
Did you mean: 

Parsing HTTP response Body to extract XML parameters

Current HTTP activity in flow is very limited in usability as it doesn't provide means to extract attributes from response body. And passing entire response body to other web request or other activity is so to speak useless. So there should be means provided to extract parameters from three most typical http response types:

1) From XML as Xpath

2) From JSON in simple Javascript expression for navigating body structure

3) From text as simple regex (like in transport rules in Exchange)

 

That would make flow 10x more usable and give it competitive advantage over IFTTT. Most datasources don't support swagger yet, and making swagger proxies requires much effort and infrastructure. Support for above scenarios would allow pass parts of responses from one web requests as parameters to other web requests giving people plenty of new scenarios available on Flow.

 

[Moderator's Note] Clarified this is for XML - JSON is supported today. Regex is suggested here: https://powerusers.microsoft.com/t5/Flow-Ideas/Support-for-regex-either-in-conditions-or-as-an-actio...

Status: Completed

You can now use the xml() expression to parse XML content and the xpath() expression to select a particular XML node. You can read more about using expressions in flow here: https://flow.microsoft.com/blog/use-expressions-in-actions/

Comments
Super User

Disregard.