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

Win free tickets to the Power Platform Conference | Summer of Solutions

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**

Celebrating the June Super User of the Month: Markus Franz

Markus Franz is a phenomenal contributor to the Power Apps Community. Super Users like Markus inspire others through their example, encouragement, and active participation.    The Why: "I do this to help others achieve what they are trying to do. As a total beginner back then without IT background I know how overwhelming things can be, so I decided to jump in and help others. I also do this to keep progressing and learning myself." Thank you, Markus Franz, for your outstanding work! Keep inspiring others and making a difference in the community! 🎉  Keep up the fantastic work! 👏👏 Markus Franz | LinkedIn  Power Apps: mmbr1606  

Copilot Cookbook Challenge | Week 1 Results | Win Tickets to the Power Platform Conference

We are excited to announce the "The Copilot Cookbook Community Challenge is a great way to showcase your creativity and connect with others. Plus, you could win tickets to the Power Platform Community Conference in Las Vegas in September 2024 as an amazing bonus.   Two ways to enter: 1. Copilot Studio Cookbook Gallery:  https://aka.ms/CS_Copilot_Cookbook_Challenge 2. Power Apps Copilot Cookbook Gallery: https://aka.ms/PA_Copilot_Cookbook_Challenge   There will be 5 chances to qualify for the final drawing: Early Bird Entries: March 1 - June 2Week 1: June 3 - June 9Week 2: June 10 - June 16Week 3: June 17 - June 23Week 4: June 24 - June 30     At the end of each week, we will draw 5 random names from every user who has posted a qualifying Copilot Studio template, sample or demo in the Copilot Studio Cookbook or a qualifying Power Apps Copilot sample or demo in the Power Apps Copilot Cookbook. Users who are not drawn in a given week will be added to the pool for the next week. Users can qualify more than once, but no more than once per week. Four winners will be drawn at random from the total qualifying entrants. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once. If they are drawn multiple times, another user will be drawn at random. Prizes:  One Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value, does not include travel, lodging, or any other expenses) Winners are also eligible to do a 10-minute presentation of their demo or solution in a community solutions showcase at the event. To qualify for the drawing, templates, samples or demos must be related to Copilot Studio or a Copilot feature of Power Apps, Power Automate, or Power Pages, and must demonstrate or solve a complete unique and useful business or technical problem. Power Automate and Power Pagers posts should be added to the Power Apps Cookbook. Final determination of qualifying entries is at the sole discretion of Microsoft. Weekly updates and the Final random winners will be posted in the News & Announcements section in the communities on July 29th, 2024. Did you submit entries early?  Early Bird Entries March 1 - June 2:  If you posted something in the "early bird" time frame complete this form: https://aka.ms/Copilot_Challenge_EarlyBirds if you would like to be entered in the challenge.   Week 1 Results:  Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1.  @Mathieu_Paris 1.   @SpongYe 2.  @Dhanush 2.   @Deenuji 3.  n/a3.   @Nived_Nambiar  4.  n/a4.   @ManishSolanki 5.  n/a5.    n/a

Your Moment to Shine: 2024 PPCC’s Got Power Awards Show

For the third year, we invite you, our talented community members, to participate in the grand 2024 Power Platform Community Conference's Got Power Awards. This event is your opportunity to showcase solutions that make a significant business impact, highlight extensive use of Power Platform products, demonstrate good governance, or tell an inspirational story. Share your success stories, inspire your peers, and show off some hidden talents.  This is your time to shine and bring your creations into the spotlight!  Make your mark, inspire others and leave a lasting impression. Sign up today for a chance to showcase your solution and win the coveted 2024 PPCC’s Got Power Award. This year we have three categories for you to participate in: Technical Solution Demo, Storytelling, and Hidden Talent.      The Technical solution demo category showcases your applications, automated workflows, copilot agentic experiences, web pages, AI capabilities, dashboards, and/or more. We want to see your most impactful Power Platform solutions!  The Storytelling category is where you can share your inspiring story, and the Hidden Talent category is where your talents (such as singing, dancing, jump roping, etc.) can shine! Submission Details:  Fill out the submission form https://aka.ms/PPCCGotPowerSignup by July 12th with details and a 2–5-minute video showcasing your Solution impact. (Please let us know you're coming to PPCC, too!)After review by a panel of Microsoft judges, the top storytellers will be invited to present a virtual demo presentation to the judges during early August. You’ll be notified soon after if you have been selected as a finalist to share your story live at PPCC’s Got Power!  The live show will feature the solution demos and storytelling talents of the top contestants, winner announcements, and the opportunity to network with your community.  It's not just a showcase for technical talent and storytelling showmanship, show it's a golden opportunity to make connections and celebrate our Community together! Let's make this a memorable event! See you there!   Mark your calendars! Date and Time: Thursday, Sept 19th Location: PPCC24 at the MGM Grand, Las Vegas, NV 

Tuesday Tip | Accepting Solutions

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   To enhance our collaborative environment, it's important to acknowledge when your question has been answered satisfactorily. Here's a quick guide on how to accept a solution to your questions: Find the Helpful Reply: Navigate to the reply that has effectively answered your question.Accept as Solution: Look for the "Accept as Solution" button or link, usually located at the bottom of the reply.Confirm Your Selection: Clicking this button may prompt you for confirmation. Go ahead and confirm that this is indeed the solution.Acknowledgment: Once accepted, the reply will be highlighted, and the original post will be marked as "Solved". This helps other community members find the same solution quickly. By marking a reply as an accepted solution, you not only thank the person who helped you but also make it easier for others with similar questions to find answers. Let's continue to support each other by recognizing helpful contributions. 

Reminder: To register for the Community Ambassador Call on June 13th

Calling all Super Users & User Group Leaders   Reminder: To register for the Community Ambassador Call on June 13th—for an exclusive event for User Group Leaders and Super Users! This month is packed with exciting updates and activities within our community.   What's Happening: Community Updates: We'll share the latest developments and what's new in our vibrant community.Special Guest Speaker: Get ready for an insightful talk and live demo of Microsoft Copilot Studio templates by our special guest.Regular Updates: Stay informed with our routine updates for User Groups and Super Users.Community Insights: We'll provide general information about ongoing and upcoming community initiatives. Don't Miss Out: Register Now: Choose the session that fits your schedule best.Check your private messages or Super User Forum for registration links. We're excited to connect with you and continue building a stronger community together.   See you at the call!  

Users online (12,337)