This tutorial is the follow-up of the previous one. Make sure your follow the steps described in the previous blog post.
A couple of days ago the Microsoft Flow team published a blog post describing the new Custom API experience.
Basically you could already create your custom action as long as you had a RESTFull api that could be described in a Swagger file; importing the Swagger file generated the “custom action”. But for many people, Postman is the tool to test & generate REST calls. One of the new feature is that we can now export a Postman collection and re import it in the Custom api UI.
Let’s illustrate how this works.
Export the PostMan Collection we created in the previous blog:
Go to the Custom API menu:
Click Create Custom API
Import the exported Postman collection file:a generic swagger file will be generated:
Do no specify any authentication. and click on Create API.
The new Custom API should be visible in the list of Custom APIs:
Now let’s get back to your CallingWorkflow : you can either modify it or work on a copy of it. Let’s copy it by clicking on the Save as option :
Save it as Calling Workflow(Custom API)
In this Flow remove the HTTP action and replace it with the new one (FlowcallFlow):
Fill-in the last 3 fields with flow variables (data coming from the SharePoint list)
Click on Done.
Add a new item in the SharePoint list and you will see that the CalledFlow will be invoked.
Compared to the previous approach, the benefit here is that we have a reusable component and that end users should only fill-in the 3 fields. I know that the other fields should be invisible to end users, I’ll try to find out how to achieve it. The reason is we can’t describe query parameters as part of the path in Swagger,we have to declare those explicitly as query parameters.