Unanswered

HTTP Request - SOAP Request 404, but works in Postman

(0) Share

Report

Posted on by peteryee78

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??

(working version in Postman)

(postman headers)

(Power Automate 404 failure)

Categories:

Using connectors

I have the same question (0)

All responses (5)

Answers (0)

powercorner 477 on at

Like (0)

Report
Copy link

Link copied!

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

Was this reply helpful? Yes No
peteryee78 11 on at

Like (0)

Report
Copy link

Link copied!

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?

Was this reply helpful? Yes No
powercorner 477 on at

Like (0)

Report
Copy link

Link copied!

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?

Was this reply helpful? Yes No
peteryee78 11 on at

Like (0)

Report
Copy link

Link copied!

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!

Was this reply helpful? Yes No
powercorner 477 on at

Like (0)

Report
Copy link

Link copied!

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

With regards
Kevin

Was this reply helpful? Yes No