cancel
Showing results for 
Search instead for 
Did you mean: 

Get the query parameters from HTTP Request trigger

I want to get the query parameters from HTTP Request trigger.

for use the query parameters to some actions.

 

Like:

- https://xxx/?Key=A1&Value=100

 

Currently:

- the request body data can use as JSON data.

- the HTTP Request trigger can use some methods, GET/PUSH/POST/PATCH/DELETE.

 

Therefore:

- I want to use the query parameters of HTTP Request

Status: Under Review

Thank you for the suggestion, we will work with the Logic apps team on this.

Comments
Level 10

I want to send a HTTP Request with the Query Parameter in the URL from Web browser.
to run the flow and get a value as html. with no-code, no-JSON.

Flow Staff
Status changed to: Under Review

Thank you for the suggestion, we will work with the Logic apps team on this.

Level 10

Hi @Stephen

Thank you for UNDER REVIEW of this idea :

Get the query parameters from HTTP Request trigger
Level: Powered On

In a very basic way, this functionality is (as of today) present in Flow. See:

 

https://powerusers.microsoft.com/t5/General-Flow-Discussion/HTTP-request-trigger-MS-Flow/td-p/83574

 

BUT I am having trouble figuring out how to recognize multiple query-parameters. In my scenario I want to pass fields for 'itemID', 'email' and 'column'. But I cannot seem to find proper documentation that exceeds the declaration of just one query-parameter/path-parameter.

 

Provided that Flow is capable of recognizing multiple parameters, all I'd need is the proper delimiter.

 

 

itemID/{itemID} & email/{email} & column/{column} <-- tried this with ; , / and & as delimiters

Does somebody know what the right delimiter might be?

 

Edit: I have figured it out. The idea is not to pass query-parameters, but exactly what Flow called it in the first place: a relative path. This is the correct way to do it:

 relativePath: ID/{itemID}/Email/{Email}/Column/{Column}

 

You will then find ".../ID/{itemID}/..." in your Flow's URL. replace '{itemID}' with your value when calling the Flow and it will work. For instance: ".../ID/123/Email/abc@xyz.com/Column/MyColumn..."

>