Power Platform Community Forum Thread Details

We have a flow that is configured to be an API. When calling it from JavaScript code, we pass to it a "filename" parameter using the querystring, like this:

<flowAPIURL> + "&filename=" + strFileName;

We recently got notification from Microsoft that the flow's trigger URL has been updated and we should use the new URL.

Using the old URL, the raw output of the flow trigger step included the “queries” section in the JSON with the "filename" node in it and we grabbed it from there:

Using the new URL, the raw output of the flow trigger step has no “queries” node:

How are we now supposed to pass parameters to API flows?

Thanks

Categories:

Using flows

Hello There,

Microsoft recently updated the structure of HTTP trigger URLs for Power Automate flows. With this change:

• Query string parameters (like ?filename=...) are no longer automatically parsed into the triggerOutputs().queries object.
• This affects flows triggered via JavaScript, Python, Postman, etc., using the new URL format.
• The change is part of a broader update to secure and standardize how data is passed into flows.

Instead of passing parameters in the query string, send them in the JSON body of the request. Here's how:

1. Update Your Flow Trigger

• Open your flow in Power Automate.
• In the “When an HTTP request is received” trigger, define a JSON schema like:

{
  "type": "object",
  "properties": {
    "filename": {
      "type": "string"
    }
  }
}

2. Update Your JavaScript Code
Use a POST request with the parameter in the body:

fetch("<newFlowURL>", {
  method: "POST",
  headers: {
    "Content-Type": "application/json"
  },
  body: JSON.stringify({ filename: strFileName })
});

3. Access the Parameter in Flow
Use:

triggerBody()['filename']

instead of:

triggerOutputs().queries.filename

Some users reported that using the old URL format still populates the queries node. However, Microsoft has marked this behavior as deprecated and it may stop working soon source.

If this helped or could help others in the community, feel free to give it a like or kudo — it helps surface useful answers for everyone!