Custom Connector created from Postman Collection works in 'Test Operation' but not when loaded into a live Flow

[ak123bcd]

Hi ,

I am trying to perform an HTTP Request using a Postman Collection as a custom connector in Flow.

The collection imports successfully and when I click Test Operation, the full HTTP Response comes back in xml as expected.  I am using No Auth.

I create and connect to the connector successfully, but then when I load it into a live flow the response returns as a random string of characters - what looks to be encrypted JSON?

All the collection does is make a simple HTTP Request, and I only switched to trying to use a custom Postman connector because the default HTTP Request action in Flow was also returning this encrypted JSON.  

How can it work fine when tested but not in actual flow creation?

Any advice?

Thanks,

[v-alzhan-msft]

Hi @ak123bcd ,

Could you please share a screenshot of the configuration of your flow?

Could you please explain more details about the error message?

Best regards,

Alice       

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

[ak123bcd]

Hi Alice,

My custom connector is imported from a Postman Collection.  In Postman the request works fine and I can download an XML file.

As you can see in the screenshot below, when I test the custom connector using the 'Test Operation' button during creation/editing, the request is successful and I can see the XML data in the response. 

However, when I then load the connector into a New flow, using the same headers and body, as seen below:

The response comes back in the format seen below.  I'm not exactly sure what format this is, I thought maybe Base64 or encrypted Json?  I can use the xml() expression to convert it to xml, but the output is then just plain text with no tags, meaning I cannot use the data.

I notice that I have some extra authorization headers in the Test Operation request (seen below), but I have also tried adding this header to the request when I create the flow and I still get the same response format above.  Also, I am selectin No Auth when creating the custom connector so I would have thought this would be unnecessary.

Any help would be much appreciated.

Thanks!

ak1

[ak123bcd]

Bump  @v-alzhan-msft