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

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / HTTP Request - SOAP Re...
Power Automate
Unanswered

HTTP Request - SOAP Request 404, but works in Postman

(0) ShareShare
ReportReport
Posted on by 11

I'm using an HTTP action to call a SOAP request that I have working in Postman, but the HTTP action is giving me a 404...

 

I've triple checked the URL is the same, and I've copy/pasted the envelope XML body, so I'm not sure why postman can hit that endpoint, but Power Automate is getting a 404.

 

I've also tried creating a custom connector, and I get the same 404. I know that endpoint is there... what else can I change to get this working??

 

peteryee78_0-1621607406281.png

(working version in Postman)

 

peteryee78_1-1621607426497.png

(postman headers)

peteryee78_2-1621607454817.png

(Power Automate 404 failure)

Categories:
I have the same question (0)
  • powercorner Profile Picture
    477 on at

    Hello @peteryee78 ,

     

    I dont know if you have written the endpoint yourself, but this guy here explains the whole process of how you deal with soap endpoints in Power Automate Flow. Helped me out in the past aswell. Three parts:

     

    https://clavinfernandes.wordpress.com/2019/11/01/soap-custom-connectors-in-microsoft-flow/

    https://clavinfernandes.wordpress.com/2019/11/06/create-a-custom-connector-using-postman-collection-file-and-integrate-it-with-microsoft-flow/

    https://clavinfernandes.wordpress.com/2019/11/12/create-a-flow-using-the-soap-connector/

     

    As far as I know Rest calls are working well with the http connector. The Soap approach is lil different. 

     

    Tell me if it helped you!


    With regards

    Kevin

     

     

  • peteryee78 Profile Picture
    11 on at

    Thanks @powercorner , I have looked at that article series and have tried those steps. The custom connector also fails with the same 404 though. I built the working version in Postman, and exported it (to version 2), then I had to get a commandline program to convert that to Postman V1 for import as a custom connector (which has worked for me on other API connectors), but no dice. Beginning to this this is a network problem? Could they be shutting out the MS servers somehow?

  • powercorner Profile Picture
    477 on at

    do you have any documentation on that api? maybe they are excluding some ip's or something? I rather see that problem at the api side then at the http connector 😕 

     

    but the 404 is still strange...

     

    Do you have a contact to the api developers?

  • peteryee78 Profile Picture
    11 on at

    Yes, I've reached out, and I have a .pdf outlining the basics. Their initial reaction was "If it works in Postman, it's not our problem", but I'm hoping they can take a look and see if there are any networking issues involved. Thanks for the help!

  • powercorner Profile Picture
    477 on at

    You are welcome @peteryee78! I am always happy to help in any way 🙂 

    Kudos welcome 😉

     

    With regards

    Kevin 

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

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Leaderboard > Power Automate

#1
David_MA Profile Picture

David_MA 251 Super User 2026 Season 1

#2
Haque Profile Picture

Haque 239

#3
Expiscornovus Profile Picture

Expiscornovus 220 Most Valuable Professional

Last 30 days Overall leaderboard