New URL Trigger - HTTP request (manual)

(0) Share

Report

Posted on by Nuiii

As I can see this message, I got many webhook that send the query string parameter along with the trigger link.

And now I'm trying to change the URL to new URL provided in the flow, but when the flow trigged, the queries not parsed in the trigger outputs.

this is my example https://defaultc613c614xxxxxxxxxx.f8.environment.api.powerplatform.com:443/powerautomate/automations/direct/workflows/43ac6b5ad27c4d7698697d0b0f59f246/triggers/manual/paths/invoke?api-version=1&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=JSWR4NuaIMWd5PATluxUdxxxxxxxx&id=' + [$Title] + '&agendatype=' + [$SessionType] + '&arbround=

Can anyone help

Thank you,

Categories:

Building flows

I have the same question (7)

All responses (9)

Answers (1)

Verified answer

Expiscornovus 33,183 Most Valuable Professional on at

Like (1)

Report

Hi @Nuiii,

I can reproduce your issue. I have the same experience with a couple of my flows as well. It simply doesn't pick up the query parameters, while it was doing that before that change.

I would suggest to reach out to Microsoft about this (I am doing the same thing), to double check if this is an issue or expected behaviour of this new change.

Happy to help out 😁

I share more #PowerAutomate and #SharePointOnline content on my Blog, LinkedIn, Bluesky profile or Youtube Channel

3 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

prakruthi 2 on at

Like (0)

Report
I have not tried this but, from what I've read and understood on this -

Queery parameters are not automatically parsed into dynamic content here. You'll need to access them explicitly using expressions within your flow. i.e., To retrieve a specific query parameter, you can use an expression like :

triggerOutputs()['queries']['parameterName'], replacing parameterName with the actual name of your query parameter.

For testing - manually trigger the flow and inspect your triggerflows(), yourFlowURL?param1=value1&param2=value2.

Please do let me know if this works.

Was this reply helpful? Yes No
Nuiii 65 on at

Like (0)

Report

Hi Expiscornovus,

Thank you for your suggestion,

I just open the ticket to MS today and let see what they could help on this issue.

Hi prakruthi,

I would say, in the new trigger URL that MS provided, any query parameter will not be parse to the flow it just stays in the headers part.

Was this reply helpful? Yes No
Suggested answer

simondisk 5 on at

Like (1)

Report

On reddit people are also discussing this.

https://www.reddit.com/r/MicrosoftFlow/comments/1n30aov/comment/nbrecqs/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

When I tried to open a ticket with Microsoft in admin.powerplattform.microsoft.com, I got presented a known issue:

Problem-ID 5532852: Updates to HTTP or Teams webhook trigger flows

[..]

Known Issue
Query parameters are not shown in the output when using a new URL. If this causes a blockage, you can continue using the old URLs. This will be resolved by early October.

[..]

so lets hope, that by early October this will be fixed

Known Issue Query...

1 people found this reply helpful.

Was this reply helpful? Yes No
Nuiii 65 on at

Like (0)

Report

Hi simondisk,

Thank you for your sharing, let's hope that they can fix the issue.

Was this reply helpful? Yes No
Expiscornovus 33,183 Most Valuable Professional on at

Like (1)

Report

Hi @Nuiii,

In my development environment the queries have started to appear again in the outputs of the trigger action.

Do you see the same thing in your setup?

Happy to help out 😁

I share more #PowerAutomate and #SharePointOnline content on my Blog, LinkedIn, Bluesky profile or Youtube Channel

Was this reply helpful? Yes No
Nuiii 65 on at

Like (1)

Report

Hi @Expiscornovus,

Yeah, I can see the queries as a selection from the output trigger action.

I just talk with MS Support on Monday; they said the issue should be fix by 24/9.

Or maybe you can follow this MS work item Power Platform admin center (this link is direct to this issue info)

Thank you for your update.

Was this reply helpful? Yes No
Nuiii 65 on at

Like (1)

Report

Hi everyone,

This is a good news update from MS, the new URL trigger issue on HTTP request has been solved.

The queries passing through the power automate as normal.

Hope you guys got this fixed as well.

Thank you,

Was this reply helpful? Yes No
RK-22101458-0 2 on at

Like (0)

Report

Any idea on how to identify if you have any flows using the deprecated trigger URL?

Was this reply helpful? Yes No