cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
KevinMS
Level: Power Up

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"
          }
        ]
      }

 

3 REPLIES 3
NathanHowe
Level: Power Up

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

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
Level: Powered On

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

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

thalesvalias
Level: Powered On

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

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

Helpful resources

Announcements
firstImage

Microsoft Business Applications Virtual Launch Event

Join us for an in-depth look at the new innovations across Dynamics 365 and the Microsoft Power Platform.

firstImage

Watch Sessions On Demand!

Continue your learning in our online communities.

Power Platform 2019 Release Wave 2 Plan

Power Platform 2019 Release Wave 2 Plan

Features releasing from October 2019 through March 2020

thirdimage

Flow Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

fifthimage

Microsoft Learn

Learn how to build the business apps that you need

sixthImage

Power Platform World Tour

Find out where you can attend!

seventhimage

Webinars & Video Gallery

Watch & learn from the Flow Community Video Gallery!

Users Online
Currently online: 72 members 4,512 guests
Please welcome our newest community members: