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:

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:

New Member

I completely agree with tszalaj on this one.  The ability to parse the body of an email would be a huge step forward, especially when using emails to create items in SharePoint.  Take for example, a SharePoint based Technical Support Ticketing System.  The ability to pull discrete fields from the email body and inject them into specific fields in a SharePoint list would make for a much more automated system, and cut down on the need for user interaction.  Such a feature would save our company thousands of dollars a year on 3rd party email parsing solutions.

Advocate IV

Newb paraphrase:

I would like to parse a subject line into distinct fields ie Right(Subject, 12) or ...

I had assumed this was already possible, and was redirected to vote this Idea up.


I also would like to see the ability to parse an email body.

And having JSON & XML HTTP responses be available as "dynamic content" would be amazing!

New Member

This is an important feature. I would like this in order to use my website to create list items in Sharepoint by sending a formatted email. Being able to use XML, JSON or regex would all be viable solutions.

New Member

Simmilar to how zapier works would be awesome

Advocate I

It would be ideal if we could just provide the Swagger schema inline. No need to reinvent the wheel here -- just let us provide the Swagger JSON inline rather than requiring an endpoint to serve it.

Not applicable

Email parsing for calendar updates based on consistant/trigger phrases would be amazing.  Like to be ab le to take and update a calendar with dates following a phrase such as "Review scheduled:"

Power Automate
Status changed to: Planned

We currently do have 1) and 2) planned - so if you have an HTTP request you can parse out JSON or XML. We have no plans at this time for arbitrary regex support, I would suggest opening a separate item for that.

New Member

I agree.

Being able to parse email body would make Lazy Approvals very easy.

New Member

Great to see this feature being planned, it will be very useful.