cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
KevinMS
New Member

Custom connector action with x-www-form-urlencoded content-type

Hi all,

 

I'm trying to build a custom connector around Twilio's fax API, but I'm having trouble creating a custom action around a POST request with an application/x-www-form-urlencoded content type. The POST request is described in Twilio's documentation here.

 

 

I can get the request to work with curl and in Postman, but with the custom connector, I keep getting a "missing required parameter" error, which makes me think that the request body is still being sent as json rather than the "key=val&key=val" format that the endpoint expects. I tried to set the Content-Type header manually, but no luck. Here is the relevant part of my openapi file. I've tried a few variants of this. Do I have something wrong, or is Flow just unable to handle custom actions with this content type?

 

"post": {
        "responses": {
          "default": {
            "description": "default",
            "schema": {
              "type": "string"
            }
          }
        },
        "consumes": [
          "application/x-www-form-urlencoded"
        ],
        "produces":[
          "application/json"
        ],
        "summary": "Send a fax",
        "description": "Sends a fax",
        "operationId": "SEND_FAX",
        "parameters": [
          {
            "name": "Content-Type",
            "in": "header",
            "description": "Content-Type",
            "required": true,
            "type": "string",
            "default":"application/x-www-form-urlencoded"
          },
          {
            "in": "formData",
            "type": "string",
            "description": "From",
            "name": "From"
          },
          {
            "in": "formData",
            "type": "string",
            "description": "To",
            "name": "To"
          },
          {
            "in": "formData",
            "type": "string",
            "description": "MediaUrl",
            "name": "MediaUrl"
          }
        ]
      }

 

16 REPLIES 16
NathanHowe
New Member

Came across this post because I'm having the EXACT same problem. I'm trying to post to Twilio's fax API and have tried passing the parameters by URL encoding and as JSON, setting the content-type manually and not specifying it at all.  Every single time the Flow fails because the required 'To' parameter is missing.  Works fine in Postman but can't get it working in Flow.

 

Hoping you solved this.  Thanks!

thalesvalias
Frequent Visitor

Same problem here, but with a private app. x-www-form-urlencoded - formDate param seems to be completely ignored by Microsoft Flow 😞

Could solve that by changing the formData parameters to query paramenters.

Anonymous
Not applicable

@thalesvalias  I'm having the same problem. Your suggested solution only works for simple parameters

{
"title":"Test folder"
}

But if you have nested parameters, or an array, it throws a different error:

{
  "project":
      { 
      "ownerIds":["KUAE6EG7"],
      "status":"Red",
      "startDate":"2019-09-31",
      "endDate":"2019-10-07"
       }
}

This is the error I get:

Your custom connector has been successfully updated, but there was an issue converting it to WADL for PowerApps: An error occured while converting OpenAPI file to WADL file. Error: 'Parameter with type='array' is not currently supported at JSON path paths./api/v4/folders/{folderId}/folders.post.parameters[3]'

 

I'm still searching for a solution (In this thread: Custom Connector - error: array not supported in parameter )

Hey, at the end I haven't stick to my previous solution... I just let the params as they originally are, as formData, and it worked normally. The thing is that I was trying to use the Test mechanism from inside the connector, and the test for formData params seems messed up. So I just ignored the tests and used the custom connector on my flow and there it simply worked.

 

But in your case you're using PowerApps, I used MSFlow... so it might be different for you :(. Sorry, I wish I could helped you more.

 


@Anonymous wrote:

@thalesvalias  I'm having the same problem. Your suggested solution only works for simple parameters

{
"title":"Test folder"
}

But if you have nested parameters, or an array, it throws a different error:

{
  "project":
      { 
      "ownerIds":["KUAE6EG7"],
      "status":"Red",
      "startDate":"2019-09-31",
      "endDate":"2019-10-07"
       }
}

This is the error I get:

Your custom connector has been successfully updated, but there was an issue converting it to WADL for PowerApps: An error occured while converting OpenAPI file to WADL file. Error: 'Parameter with type='array' is not currently supported at JSON path paths./api/v4/folders/{folderId}/folders.post.parameters[3]'

 

I'm still searching for a solution (In this thread: Custom Connector - error: array not supported in parameter )


 

Anonymous
Not applicable

Thanks for sharing your workaround. 

Maybe I posted in the wrong forum, I actually am using Flow as well, because of the error message stopping me in the Custom Connector setup, I posted in the powerapps forum. 

 

I'm glad that it worked for you using formData, unfortunately the api I'm connecting to (Wrike) doesn't support that Content Type.

 

Since writing my post I tested in Postman and was successful in sending the request by adding the header Content-Type application/x-www-form-urlencoded - so I went back to the custom connector and added my parameters to the body, when I peek code everything shows up as I believe it should. 

 

And now I am in flow and stuck at the same place as the OP.

Other api, same problem:

In Postman: works fine

In connector test function: works fine too:

 

Swagger-Editor:

paths:
  /auth/token:
    post:
      consumes: [application/x-www-form-urlencoded]
      produces: [application/json]
      parameters:
      - {name: client_id, in: query, required: true, type: string, default: myclient,
        x-ms-visibility: internal}
      - {name: client_secret, in: query, required: true, type: string, default: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx,
        x-ms-visibility: internal}
      - {name: grant_type, in: query, required: true, type: string, default: client_credentials,
        x-ms-visibility: internal}
      - {name: Content-Type, in: header, required: true, type: string, default: application/x-www-form-urlencoded,
        x-ms-visibility: internal}

But using it in PowerApp or Flow, I get status=415 error (wrong Content-Type)

 

It seems, the the microsoft server is changeing the header:

{
  "method":"post",
  "queries":{
    "client_id":"myclient",
    "client_secret":"xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
    "grant_type":"client_credentials"
  },
  "headers":{
    "Content-Type":"application/x-www-form-urlencoded"
  },
  "path":"/auth/token",
  "host":{
    "api":{
      "runtimeUrl":"https://europe-002.azure-apim.net/apim/connector-999999999999999999999999999999999999"
    },
    "connection":{
      "name":"/providers/Microsoft.PowerApps/apis/shared_connector-999999999999999999999999999999999999/connections/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
    }
  },
  "authentication":{
    "scheme":"Key",
    "parameter":"*sanitized*",
    "type":"Raw"
  }
}

back to 

 

"Content-Type":"application/json"

 

Anonymous
Not applicable

I was able to get mine working, I ended up putting the whole thing in the URL query.

For my problematic object I added it into the URL sample in PowerApps Custom Connector as:

 

&project=string

Then in Flow, I created a compose action and wrapped it in the following Expression:

string('{ "ownerIds":["KUAE6EG7"],"startDate":"2020-08-06"}')

image.png

 

It is working for now, so whatever re-formatting Flow is doing, forcing it into a string before-hand seems to do the trick for me.

Hi Gonzalo,

 

yes: for your problem this workaround helps changing the url

 

Unfortunately not for me, because

 

"content-type": "application/x-www-form-urlencoded"
is a HTTP Header parameter and not changeable (or addable) with a compose action 

 

rojoshi
Frequent Visitor

I got my API to finally work. Here is what I did:

1. Exported my postman collection

2. Converted the export JSON file into Swagger format

3. Then, in PowerApps Custom Connector, I opened my non-working connector in Edit mode

4. On Test tab, I opened the API in Swagger editor and pasted the Swagger code generated in step 2

5. I tried the API there itself and it returned a valid output

6. The problem here though is that the API only returns True or False values

7. So I had to edit the Swagger code a little bit so as to get a JSON response from the API. Used the link https://swagger.io/docs/specification/2-0/describing-responses/ for updating the Swagger

 

Hope this helps you.

Anonymous
Not applicable

@Frank37 ,

Have you tried adding the header as a "New Policy"? It might be worth a try.

 

  1. Click "New Policy"
  2. Name your policy
  3. Select "Set HTTP header"
  4. Select the Operations (Actions) that require this header
  5. Header name: "content-type"
  6. Header Value: "application/x-www-form-urlencoded"
  7. Action if header exists: "override"
  8. Run policy on: "Request"

 

@Anonymous  Great Idea: it works 👍

This helped me.

Please remember to encode using base64 method

Logic Apps works with and supports other content types, but might require that you manually get the message body by decoding the $content variable.

https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-content-type#other-content-types

How can I add a new policy

Anonymous
Not applicable

While editing your custom connector:

1. Under the Definition tab scroll all the way down

2. The last section is called Policies

3. click +New policy

@Anonymous this helped me but I can't get a successful response when running custom connector in Power App because the request body is always

 

"body": ""

 

instead of

 

"body": {}

 

or

 

"body": {
   "pagination": {
    "pageNumber": 1,
    "pageSize": 999
  }
}

 


How can I pass in a proper request body from Power Apps to custom connector?

Have talked about this problem extensively herehere, and here.

Helpful resources

Announcements

Celebrating the May Super User of the Month: Laurens Martens

  @LaurensM  is an exceptional contributor to the Power Platform Community. Super Users like Laurens inspire others through their example, encouragement, and active participation. We are excited to celebrated Laurens as our Super User of the Month for May 2024.   Consistent Engagement:  He consistently engages with the community by answering forum questions, sharing insights, and providing solutions. Laurens dedication helps other users find answers and overcome challenges.   Community Expertise: As a Super User, Laurens plays a crucial role in maintaining a knowledge sharing environment. Always ensuring a positive experience for everyone.   Leadership: He shares valuable insights on community growth, engagement, and future trends. Their contributions help shape the Power Platform Community.   Congratulations, Laurens Martens, for your outstanding work! Keep inspiring others and making a difference in the community!   Keep up the fantastic work!        

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

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. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!    

Welcome to the Power Automate Community

You are now a part of a fast-growing vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun.   Now that you are a member, you can enjoy the following resources:   Welcome to the Community   News & Announcements: The is your place to get all the latest news around community events and announcements. This is where we share with the community what is going on and how to participate.  Be sure to subscribe to this board and not miss an announcement.   Get Help with Power Automate Forums: If you're looking for support with any part of Power Automate, our forums are the place to go. From General Power Automate forums to Using Connectors, Building Flows and Using Flows.  You will find thousands of technical professionals, and Super Users with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Automate community forums. Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered. Galleries: The galleries are full of content and can assist you with information on creating a flow in our Webinars and Video Gallery, and the ability to share the flows you have created in the Power Automate Cookbook.  Stay connected with the Community Connections & How-To Videos from the Microsoft Community Team. Check out the awesome content being shared there today.   Power Automate Community Blog: Over the years, more than 700 Power Automate Community Blog articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on the future of process automation. In the Power Automate Community Blog, you can read the latest Power Automate-related posts from our community blog authors around the world. Let us know if you'd like to become an author and contribute your own writing — everything Power Automate-related is welcome.   Community Support: Check out and learn more about Using the Community for tips & tricks. Let us know in the Community Feedback  board if you have any questions or comments about your community experience. Again, we are so excited to welcome you to the Microsoft Power Automate community family. Whether you are brand new to the world of process automation or you are a seasoned Power Automate veteran - our goal is to shape the community to be your 'go to' for support, networking, education, inspiration and encouragement as we enjoy this adventure together.     Power Automate Community Team

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Tuesday Tip | How to Report Spam in Our Community

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.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Users online (4,135)