web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

Welcome to the Power Platform Communities
News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Custom connectors and ...
Power Automate
Unanswered

Custom connectors and HTTP GET with multiple, repeated Query Parameters

(2) ShareShare
ReportReport
Posted on by Community Power Pla... Microsoft Employee

I’m adding some REST calls to an existing custom connector.  The specific HTTP GET call I want to make is as follows:

 

http://theIPAddress:8080/theProductName/restful/alarms?landscape=0x100000&attr=0x11f56&attr=0x12b4c&throttlesize=250

 

Note the repeating attr values, above (there are two).

 

And here's the Action I've added in Flow:

 

flowQueryParameterDuplicates.png

 

As indicated by the red highlight in this screenshot, Flow seemed to pick up only one of my attr parameters.  Whereas, the URL (above) has multiples.

 

I’ve scoured Google and the Flow Community pages, but I’m not able to find a solution.

 

Anyone have any experience with how to make a Flow Custom connector accept multiple, repeated Query parameters?

 

Categories:
Using connectors
  • manuelstgomes Profile Picture
    manuelstgomes 6,643 on at

    Hi 

     

    There's no defined standard to parse multiple Query Parameters with the same name.

     

    This stackoverflow discusses this in detail.

    https://stackoverflow.com/questions/24059773/correct-way-to-pass-multiple-values-for-same-parameter-name-in-get-request

     

    Basically this depends on the implementation of each platform and Flow may ignore the next occurrence with the same name.

     

    Ideally, you should avoid this.

     

    If I have answered your question, please mark your post as Solved.
    If you like my response, please give it a Thumbs Up.
    ​
    Cheers
    Manuel

  • carlilelance Profile Picture
    carlilelance 353 on at

    There is a "hack" to get around this. If you use the HTTP Action (GET Method) and instead of using the Query fields (they must ALL be blank for this to work), you can put the queries as part of the URI. 

     

    carlilelance_0-1624651528184.png

     

    This allows one to overcome the limitations mentioned by different implementations of multiple query parameters. Another pitfall to avoid is if your queries have spaces in them. You can get around this by creating a variable for the URI string, and passing it in as a variable. 

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Welcome to the Power Platform Communities

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the August Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Mohsin Ali Profile Picture

Mohsin Ali 389

#2
11manish Profile Picture

11manish 345 Super User 2026 Season 2

#3
M Bilal Khan Profile Picture

M Bilal Khan 308

Last 30 days Overall leaderboard

Featured topics

Known issue with browser automation in Power Automate for Desktop on Google Chrome 146 and 147
Share your ideas and struggles with building Power Automate flows!
Survey: Power Automate mobile app
How to Ask for Help with Your Power Automate Workflow
Start and wait for an approval action
Restore a deleted flow
List of actions cheat sheet for Power Automate Desktop
Welcome to the Power Automate forum!

Product updates

Microsoft Power Platform Community release plans