Create a Flow Using a Custom SOAP Connector – Part 3

This is the third and final post in our SOAP Custom Connector  series.  In this article we’ll use the custom SOAP connector we created in parts 1 and 2 of this series, to design a Microsoft Flow that automates conversions using the on-premise version of the Muhimbi PDF Converter. In this three-part series, we’ll cover the …

Creating a Custom Flow SOAP Connector using a Postman collection File – Part 2

In the previous blog, we created a Postman collection which holds our SOAP request and exported the collection as an Postman collection (.json) file. In this blog, you create a custom connector using the Postman collection file which will help us in Converting documents to PDF.

Using SOAP Custom Connectors in Microsoft Power Automate (Flow) – Part 1

This topic is part of a tutorial series on creating and using SOAP custom connectors in Azure Logic Apps, Microsoft Flow, and PowerApps. Why wouldn’t I just use the built-in Flow actions and REST based API of The Muhimbi PDF Converter Services Online, you ask? The reasons are usually regulatory compliance and/or corporate governance. You simply might not be authorised to process your documents on third party systems, no matter how secure the underlying technology is. So, with the “why?” having been covered, lets move-on to the actual steps you’ll be using to get this working.