web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

Welcome to the Power Platform Communities
News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / HTTP 400 and/or BadGat...
Power Automate
Answered

HTTP 400 and/or BadGateway (http request to Dynamics CRM)

(0) ShareShare
ReportReport
Posted on by ZePowerDiver 279 Most Valuable Professional

I'm trying to build a flow that will eventually return data from CRM based on a user query. All works well in my browser, but when I try to integrate in a Flow it fails. So I dropped the filter out of the equation and only went to select data from a OOB entity (accounts in this case).

When I test it, I get an error http 400 !!

 

HTTP REQUESTHTTP REQUESTHTTP RETURN CODE 400!!!HTTP RETURN CODE 400!!!

 

So, I added my next step right away, which is to provide a response back to the calling app of the body obtained in the first step..

If I test this, the flow doesn't even execute as I get a Bad Gateway error at the run popup window!

 

ADD RESPONSE IN FLOWADD RESPONSE IN FLOWBADGATEWAY!!!!BADGATEWAY!!!!

help appreciated!

Categories:
Using connectors
  • Verified answer
    ZePowerDiver Profile Picture
    ZePowerDiver 279 Most Valuable Professional on at

    It's funny how you end up finding a solution to an issue.. just when you dropped the towel and sent out the question in the world!!

     

    I ended up going in the run history to see if I could see details about the bad gateway.. and that's where I fumbled the following details regarding the error 🙂

     

    2019-02-06_12-33-27.jpg

     

    Bottom line, in the connection definition I had used the "CRM" site address and in the http request I used the API call URL

     

    2019-02-06_12-40-32.jpg

     

    when in fact I had to make sure the resource URI was/is the API one!!

     

    2019-02-06_12-39-59.jpg

     

    Case closed!

  • Verified answer
    NicolasK Profile Picture
    NicolasK Microsoft Employee on at

    Glad you found a solution, but your analysis is not completly correct. 

    The important thing is that each URL is the same. It does not matter if it is the API url or the main one, as long as they are identical.

    So you can have https://xxxx.crm.dynamics.com in both connection definition and action URL, and it will work perfectly too.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Welcome to the Power Platform Communities

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the July Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
11manish Profile Picture

11manish 231 Super User 2026 Season 2

#2
David_MA Profile Picture

David_MA 217 Super User 2026 Season 2

#3
Mohsin Ali Profile Picture

Mohsin Ali 170

Last 30 days Overall leaderboard

Featured topics

Known issue with browser automation in Power Automate for Desktop on Google Chrome 146 and 147
Share your ideas and struggles with building Power Automate flows!
Survey: Power Automate mobile app
How to Ask for Help with Your Power Automate Workflow
Start and wait for an approval action
Restore a deleted flow
List of actions cheat sheet for Power Automate Desktop
Welcome to the Power Automate forum!

Product updates

Microsoft Power Platform Community release plans