Showing results for 
Search instead for 
Did you mean: 
Resolver I
Resolver I

custom connector works in test but returns error when used in flow

In one of my older flows last year I tried using a custom connector to get a JSON file with no problems at that time.
Recently I´ve tried to use the same connector in a new cloudflow but I get an error.

During Test within connector details everything works fine and I get data as expected (obtaining JSON).

The problem is that if used in a cloud flow following error is shown:

 " body should be String but it is Object."

thanks a lot

Thanks a lot for your answer
Any help would be highly appreciated

Community Support
Community Support

Hi @Hancha ,


I think when putting {} into the "body" in your postman definition which you upload to create the connector might be the scenario hence you can check by leaving it blank which should it as "null" which is an object.


During import of the json response in custom connector, a json definition should have got created. The Swagger editor should show you the definition of the part which failed as follow or similar to it :


=> GlobalValues: {type: string, description: GlobalValues]


Try changing it to:

=> GlobalValues: {type: array, items{}, description: GlobalValues]



Hi @pre ,

I tried checking all the above but it did not solve the problem...

Helpful resources

Power Automate News & Announcements

Power Automate News & Announcements

Keep up to date with current events and community announcements in the Power Automate community.

Community Calls Conversations

Community Calls Conversations

A great place where you can stay up to date with community calls and interact with the speakers.

Power Automate Community Blog

Power Automate Community Blog

Check out the latest Community Blog from the community!

Top Solution Authors
Top Kudoed Authors
Users online (4,026)