'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Call an On-Premises SOAP Web Service from Power Automate
Question details
The user needs to send a SOAP request to an on-premises SharePoint 2016 web service via Power Automate, but is unsure how to handle XML formatting.
- Product
- Power Automate
- Device & OS
- not provided
- Scenario
- Integrating cloud-based Power Automate workflows with legacy on-premises SharePoint 2016 SOAP endpoints.
- Observed behavior
- The standard 'Send an HTTP Request to SharePoint' action appears specifically designed for JSON/REST, leaving uncertainty on how to format SOAP/XML calls and handle on-premises authentication.
Verify that you have an On-Premises Data Gateway correctly installed and configured to bridge your cloud Power Automate environment with your local SharePoint 2016 server.
Consult Microsoft Learn and the Power Platform Community
Because SOAP and XML implementations for on-premises SharePoint require specific header configurations and custom connector setups, consulting specialized forums is the most reliable path.
Power Automate natively favors JSON and REST APIs. Implementing SOAP requests to on-premises environments involves complex authentication, XML parsing, and data gateway routing. Specialists in Microsoft communities can provide tailored XML schemas and custom connector guidance for your exact endpoint.
Navigate to the Microsoft Learn Q&A platform and search for existing threads regarding 'Power Automate SOAP XML'.
Go to the official Power Platform Community forums and post your specific SharePoint 2016 SOAP endpoint requirements in the 'Power Automate' section.
When asking for help, include the WSDL of your SOAP service, your current On-Premises Data Gateway setup, and the exact XML envelope you are trying to send.
Use standard HTTP Action with XML Headers
You can manually configure the 'Send an HTTP Request to SharePoint' or premium 'HTTP' action to process raw XML instead of JSON.
Enhance Your Daily Productivity with WPS Office
While you troubleshoot complex Power Automate integrations, WPS Office can serve as a robust, lightweight, and free alternative to Microsoft Office for all your document processing needs.
- 1. Download the Installer: Visit the official WPS Office website and download the free installer for your operating system.
- 2. Install WPS Office: Run the setup file and follow the on-screen instructions for a quick, lightweight installation.
- 3. Open Your Documents: Launch the application and seamlessly open, edit, and save your existing Microsoft Office files without formatting loss.
Frequently Asked Questions
Can the 'Send an HTTP request to SharePoint' action handle XML and SOAP?
Yes, but you must bypass its default JSON behavior by manually setting the 'Accept' and 'Content-Type' headers to 'text/xml' and supplying the raw SOAP envelope in the body field.
Do I need an On-Premises Data Gateway for SharePoint 2016?
Yes. Because Power Automate is a cloud-based service, connecting it to any on-premises server like SharePoint 2016 requires an On-Premises Data Gateway to securely route the requests.
Are there native SOAP connectors in Power Automate?
Power Automate natively favors REST API and JSON. For SOAP services, you typically need to create a Custom Connector defining the SOAP-to-REST mapping, or use standard HTTP actions with raw XML payloads.
