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

In our previous post in this series, we created a Postman collection which held our SOAP request, and we exported the collection as a Postman collection (.json) file.

In this post, we will create a custom Power Automate (Flow) connector using a Postman collection file, which we will use to convert documents to PDF using our own privately hosted back-end.

In this three-part series, we’ll cover the following topics:

  1. Creating a SOAP custom Connector using Postman (part 1).
  2. Creating a custom Connector using a Postman collection file and Integrating it with Microsoft Power Automate (this post).
  3. Creating a Flow that can consume the SOAP Service (part 3).

Before we begin, please make sure the following prerequisites are in place:

  1. A Postman collection file and Power Automate (Microsoft Flow) subscription.
  2. Optional: An image to use as an icon for your custom connector.

With the prerequisites in place, we move on to Step 1.


Step 1: Sign in to your Power Automate account and click Data > Custom Connectors on the left sidebar.


Step 2: Click ‘New custom connector’ and again on Import a Postman collection.

Enter a name for the custom connector, then navigate to the Postman collection that we downloaded in part 1, and choose continue.

The wizard imports the collection, then converts it to an OpenAPI definition named generatedApiDefinition.swagger.json.


Step 3: The General information page opens.  Review the information that was imported from the Postman collection, including the host and the base URL for the API. The connector uses the host and base URL with port number included (The PDF Converter services use port 41734 by default) to determine how to call the API.

Step 4 : On the Security page, under Authentication type, choose “No authentication”.


Step 5: Review the Definition with reference to the screenshot below.


Step 6: Now that you have configured the connector, you need to click on  “Create connector” (in the ribbon at the top of the page), so you can test your new connector and make sure it’s working properly.

  • On the Test page, choose “New connection”.
  • Enter the WSDL URL “http://<PublicIP>:41734/Muhimbi.DocumentConverter.WebService/?wsdl“
  • Enter the SOAP request in the Body parameter (refer to step 4, in this article).
  • Click on “Test operation”. The connector then calls the API and you should get a response with Status 200, which includes ConvertResponse below:

In the next blog we will use our custom connector with Microsoft Power Automate (Flow).

3 thoughts on “Creating a Custom Flow SOAP Connector using a Postman collection File – Part 2

  1. Hello I have used your article to create custom connector using postman collection file. I am getting ‘The remote name could not be resolved:’ when testing the operation. Any ideas what could be the reason?

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s