cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Mick282
Helper III
Helper III

application/x-www-form-urlencoded content type error using when a HTTP request is received

Hi

 

I'm using a webhook created by Unbounce forms. The problem with the webhook is that it sends the payload with a content type of application/x-www-form-urlencoded. I'm now getting this weird error :

 

 

{
  "error": {
    "code": "InvalidRequestContent",
    "message": "The input body for trigger 'manual' of type 'Request' must be of type JSON, but was of type 'application/x-www-form-urlencoded'."
  }
}

 

 

A sample payload of what is submitted is below:

 

 

{
  "$content-type": "application/x-www-form-urlencoded",
  "$content": "<a base 64 encoded content>",
  "$formdata": [
    {
      "key": "page_url",
      "value": "url of the form"
    },
    {
      "key": "page_name",
      "value": "name of the page"
    },
    {
      "key": "page_id",
      "value": "id of the page"
    },
    {
      "key": "variant",
      "value": "a"
    },
    {
      "key": "data.json",
      "value": "The JSON object containing the field values of the form"
    },
    {
      "key": "data.xml",
      "value": "XML version"
    }
  ]
}

 

 

When I initially setup the HTTP request is received trigger it seems to take the webhook and schema correctly but as I'm adding items to it, it throws the error that it needs fixing. A snippet of the whole flow is below:

 

image.png

 

What I first do is select the data.json value in the array and parse JSON

 

image.png

 

The expression in the Content field is:

 

triggerBody()?['$formdata'][4]

 

Basically I'm selecting the data.json value in the formdata array.

 

I then parse the full JSON value.

image.png

 

The expression in the content is:

 

json(body('Parse_data.json')?['value'])

 

 

It seems to submit and flow correctly during an initial test of the webhook and submission of the unbounce form but any future submissions throws the error:

 

 

{
  "error": {
    "code": "InvalidRequestContent",
    "message": "The input body for trigger 'manual' of type 'Request' must be of type JSON, but was of type 'application/x-www-form-urlencoded'."
  }
}

 

 

Any help would be greatly appreciated.

1 ACCEPTED SOLUTION

Accepted Solutions
v-bacao-msft
Community Support
Community Support

 

Hi @Mick282 ,

 

Do you mean that the body output by the trigger is the sample you provided?

Then this part of the content cannot be used in Parse JSON, because its type is clearly application / x-www-form-urlencoded and not JSON.

You need to extract $ formdata first and then parse it.

Please check the attachment and import it as a new Flow.

 

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

9 REPLIES 9
v-bacao-msft
Community Support
Community Support

 

Hi @Mick282 ,

 

Do you mean that the body output by the trigger is the sample you provided?

Then this part of the content cannot be used in Parse JSON, because its type is clearly application / x-www-form-urlencoded and not JSON.

You need to extract $ formdata first and then parse it.

Please check the attachment and import it as a new Flow.

 

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Hi @v-bacao-msft ,

 

Thanks for sending through the zip file. Quick question. If I use the apply to each, how do I extract the value from key : data.json?

 

Basically that's the only section of the formdata array that I'm interested in.

 

It seems to be caused by an issue with the trigger itself which is the When a HTTP request is received.

 

It won't even register the flow run when I do a test submission

 

Hi @Mick282 ,

 

If you created the Flow using the .zip file I provided, you need to replace the trigger with When a HTTP request is received.

And configure the parameters included in the previous Flow in the trigger.

Then configure the trigger body in Compose. Here I guess that the body output by the trigger is the sample you provided, so a specific method is provided.

 

Regarding extract the value from key: data.json, I'm afraid I don't understand what you mean. Parse JSON has parsed out the data contained in $formdata, you only need to use Dynamic content to get the attribute value directly.

 

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

I am having the same issue with this. I have tried your method and it works fine until you add an action that actual does something e.g. CDS List Records. If you don't add an action you can assign a variable and pull the data you require out of the formdata. If you then add an action the flow doesn't even show as running. 

I have sent the data via Postman and without the action it fires fine. With the action it returns the below error message.

 

{
    "error": {
        "code""InvalidRequestContent",
        "message""The input body for trigger 'manual' of type 'Request' must be of type JSON, but was of type 'application/x-www-form-urlencoded'."
    }
}
 
I cannot change the request type as it is coming from an external system, so is there a way to force Automate to accept it.
 
Thanks

Dave
Jronash
Impactful Individual
Impactful Individual

@NAR, I'm experiencing the same behavior.  Did you ever come up with a way around this limitation?

Anonymous
Not applicable

I'm going to try to post a very quick summary of how I got this to work, with a Mailchimp webhook triggering a flow, wherein I managed to get an object that was addressable using the keys, despite the form being urlencoded.

 

1. Use HTTP Request trigger with the json schema left blank.

2. input that into Parse Json as follows:
 amh15_0-1622990395143.png

 

Here's the schema that worked for me in the above Parse JSON: 

{
    "type""array",
    "items": {
        "type""object",
        "properties": {
            "key": {
                "type""string"
            },
            "value": {
                "type""string"
            }
        },
        "required": [
            "key",
            "value"
        ]
    }
}
 
This produced an array something like this:
[
  {
    "key""type",
    "value""campaign"
  },
  {
    "key""fired_at",
    "value""2021-06-05 00:33:42"
  },
  {
    "key""data[id]",
    "value""20b9073683"
  },
  {
    "key""data[subject]",
    "value""Catching up"
  },
  {
    "key""data[status]",
    "value""sent"
  },
  {
    "key""data[reason]",
    "value"""
  },
  {
    "key""data[list_id]",
    "value""0d8ea2e4ed"
  }
]
 
3. Apply to each on the resulting array to replace open and close square brackets in the key names with _ and with a blank - because we are not going to be allowed associative arrays, nor square brackets in object names:
amh15_1-1622990700403.png

 

Here is the replace I used: replace(replace(items('Apply_to_each_2')?['key'],'[','_'),']','')

And here's the addProperty I used: addProperty(variables('formdata'),variables('cleaned_key_name'),items('Apply_to_each_2')?['value'])

 

You'll notice addProperty adds the cleaned up key name as a new property to the object tempobj. We then assign the value of tempobj into the original property variable formdata that the loop has built up.

 

You end up with an object looking like this:

 

{
  "type""campaign",
  "fired_at""2021-06-05 00:33:42",
  "data_id""20b9073683",
  "data_subject""Catching up",
  "data_status""sent",
  "data_reason""",
  "data_list_id""0d8ea2e4ed"
}
 
If you had nested arrays, they're no longer nicely nested, but you can still directly access the entire nested structure using the names as you can see above.
 
It's not super elegant and if I had been able to get a parse JSON to properly read the nested array as others have suggested elsewhere, I would have preferred that, but it works!

 

Jronash
Impactful Individual
Impactful Individual

Nice solution, @Anonymous.

 

I'll also mention that the triggerFormDataValue() expression can be very handy in cases like this.  It can grab the value from a specific form field.  For example:

 

triggerFormDataValue('data[id]')

or

triggerFormDataValue('data[subject]')
Anonymous
Not applicable

For some reason I had rejected that route - perhaps I hadn't figured out how to deal with the square brackets or perhaps I thought the syntax looked awkward -  but you're right, that should work, and in fact I'm not sure there's any real advantage in having it in a single object that way I did, as my dynamically created properties don't pop up in the Dynamic Content UI (Flow has no idea at edit time what they will be), so the syntax of my approach seems no better in the end.

Leaving the schema blank was actually what I needed, thanks!

Helpful resources

Announcements

Super User of the Month | Drew Poggemann

As part of a new monthly feature in the Community, we are excited to share that Drew Poggemann is our featured Super User for the month of February 2024. If you've been in the Community for a while, we're sure Drew's name is familiar to you, as he is one of our most active contributors--he's been a Super User for five consecutive seasons!   Since authoring his first reply 5 years ago to his 514th solution authored, Drew has helped countless Community members with his insights and expertise. In addition to being a Super User, Drew is also a User Group leader and a Microsoft MVP. His contributions to our Super User sessions and to the new SUIT program are always welcome--as well as his sense of humor and fun-loving way of sharing what he knows with others.   When Drew is not solving problems and authoring solutions, he's busy overseeing the Solution Architecture team at HBS, specializing in application architecture and business solution strategy--something he's been doing for over 30 years. We are grateful for Drew and the amazing way he has used his talent and skills to help so many others in the Community. If you are part of the SUIT program, you got to hear some great tips from Drew at the first SUIT session--and we know he still has much more to share!You can find him in the Community and on LinkedIn. Thank you for all you do, Drew!

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Our team will be reviewing posts using the new "Copilot Studio" label to ensure we highlight and amplify the most relevant and recent content, so you're assured of high-quality content every time you visit. If you share a post that gets featured in the curated gallery, you'll get a PM in the Community to let you know!The curated gallery is ready for you to experience now, so visit the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community. We can't wait to see what you "cook" up!    

Celebrating a New Season of Super Users with Charles Lamanna, CVP Microsoft Business Applications

February 8 was the kickoff to the 2024 Season One Super User program for Power Platform Communities, and we are thrilled to welcome back so many returning Super Users--as well as so many brand new Super Users who started their journey last fall. Our Community Super Users are the true heroes, answering questions, providing solutions, filtering spam, and so much more. The impact they make on the Communities each day is significant, and we wanted to do something special to welcome them at our first kickoff meeting of the year.   Charles Lamanna, Microsoft CVP of Business Applications, has stressed frequently how valuable our Community is to the growth and potential of Power Platform, and we are honored to share this message from him to our 2024 Season One Super Users--as well as anyone who might be interested in joining this elite group of Community members.     If you want to know more about Super Users, check out these posts for more information today:    Power Apps: What is A Super User? - Power Platform CommunityPower Automate: What is A Super User? - Power Platform Community Copilot Studio: What is A Super User? - Power Platform Community Power Pages: What is A Super User? - Power Platform Community

Super Users 2024 Season One is Here!

   We are excited to announce the first season of our 2024 Super Users is here! Our kickoff to the new year welcomes many returning Super Users and several new faces, and it's always exciting to see the impact these incredible individuals will have on the Community in 2024! We are so grateful for the daily difference they make in the Community already and know they will keep staying engaged and excited for all that will happen this year.   How to Spot a Super User in the Community:Have you ever written a post or asked for help in the Community and had it answered by a user with the Super User icon next to their name? It means you have found the actual, real-life superheroes of the Power Platform Community! Super Users are our heroes because of the way they consistently make a difference in the Community. Our amazing Super Users help keep the Community a safe place by flagging spam and letting the Community Managers know about issues. They also make the Community a great place to find answers, because they are often the first to offer solutions and get clarity on questions. Finally, Super Users share valuable insights on ways to keep the Community growing, engaging, and looking ahead!We are honored to reveal the new badges for this season of Super Users! Congratulations to all the new and returning Super Users!     To better answer the question "What is a Super User?" please check out this article: Power Apps: What is A Super User? - Power Platform CommunityPower Automate: What is A Super User? - Power Platform Community Copilot Studio: What is A Super User? - Power Platform Community Power Pages: What is A Super User? - Power Platform Community

Did You Attend the Microsoft Power Platform Conference in 2022 or 2023? Claim Your Badge Today!

If you were one of the thousands of people who joined us at the first #MPPC Microsoft Power Platform Conference in 2022 in Orlando--or attended the second-annual conference in Las Vegas in 2023--we are excited to honor you with a special community badge! Show your support for #MPPC Microsoft Power Platform Conference this year by claiming your badge!           Just follow this link to claim your badge for attending #MPPC in 2022 and/or 2023: MPPCBadgeRequest    Want to earn your badge for 2024? Just keep watching our News & Announcements for the latest updates on #MPPC24.

Microsoft Power Platform | 2024 Release Wave 1 Plan

Check out the latest Microsoft Power Platform release plans for 2024!   We have a whole host of exciting new features to help you be more productive, enhance delegation, run automated testing, build responsive pages, and so much more.    Click the links below to see not only our forthcoming releases, but to also try out some of the new features that have recently been released to market across:     Power Apps  Power Automate  Copilot Studio   We can’t wait to share with you all the upcoming releases that will help take your Power Platform experience to the next level!    Check out the entire Release Wave: Power Platform Complete Release Planner 

Users online (8,695)