SOAP Request activity not working

Im currently trying to use the soap activity but i keep running into problems. Tried some work arounds am stuck and dont know how to continue. will appreciate any help.

  1. tried with the actual URL, after clicking “GET” I get this error


  1. downloaded the wsdl file and used that instead
    The problem now is I only have 1 argument field when there should be multiple argument, when I click “invoke” it shows the error below

In SOAPUi , the request works and it shows the correct number of arguments, how can i apply this to the UiPAth soap request activity?

Hello @jack.chan ,

Can you try using https://your_service_url?wsdl

Hi AndyMenon, I am having the same issue and tried https://your_service_url?wsdl, but no luck so far. Any idea?

Hi @jack.chan and @zol,

The Soap Request from UiPath.WebAPI.Activities is a hit and a miss depending on how the API was designed.

Option 1 If your WSDL from the url does not work in SOAP request, you can try coping the WSDL xml text to a file and use the location of the file. It might still fail when you try with the wsdl file from a file location.

Option 2 Use UiPath Library and used the New Service options to add WSDL from your URL. Services can mostly parse WSDLs where SOAP Request fails. What it does is that it goes to the endpoint your provide and gets all possible operations and their namespaces and imports them to your project / Library. Then within the UiPath library, you can make custom workflows for each of your operations.

Option 3 If Option 1 and Option 2 both don’t work for you, go to the trusty old HTTP Request activity. Why? HTTP request activity can use xml/text as payload. All you have to then do is prebuild an XML using template strings (a file with placeholders). You replace the placeholders after reading the text file and you will end up having a string which can be desearalized (Deserialse XML)

Use a template of the XML structure. Read it as a text file. Use String.Replace to populate the parameter values/Placeholders and repeat it as many times as required. Then use Option 3 as HTTP request can take string as body and can parse the bodyformat as text/xml.

Ingest the text/xml as payload/body text in your HTTP request.

Option 4
If Option 3 also fails then it is time for PowerShell to do the heavylifting. Similar to Option 3, build up the xml and use
$res=Invoke-WebRequest -Method:post -uri $URL -Headers $headers -Body $body -ContentType “text/xml”

Do also go through this video from @Cristian_Negulescu UiPath Tutorial for SOAP and XML (Create and Deserialize XML) | UiPath SOAP request - YouTube from where I learnt about the option 1 and 2.

Thank you @jeevith

for me, due to time constraints i downloaded SoapUI and used uipath to automate it to call my SOAP requests. But i will definitely try your suggestions next time