Call Azure Function App from Microsoft Flow (Part III)

In Part I of this post, we created an Azure Function that handles the auth and also applies some business logic.

In Part II, we created a custom data connector that will allow us to get data from a web service.

In this post, we will iterate through a SharePoint list and call the Azure Function from a Flow to update the ‘Status’ field based on the results of the call to the Azure Function.

Open the flow tool by going to
https://flow.microsoft.com

Create a new Flow by selecting +New and then +Scheduled–from blank.

Give your new Flow a name, and select the schedule (how often it will run.)

Select the SharePoint icon, then select ‘Get Items’.

Select the site and the list. Optionally, you can create an OData filter to only act on items that meet conditions. This might greatly improve the performance of your Flow. For example, imagine a list containing thousands of list items. If you only need to act on a few items, then filter the list before you get the items. Not after!

Next, add an “Apply to Each” action and select “value” List of Items as the thing to iterate through.

Next click on “Add an Action” inside the Apply to Each block. Start typing the name of the action from the custom data connector that was created for your Flow. It should find the connector

Click on your connector. You will then be prompted to add provide the fields for the web service query. In the screenshot below, we click on the jobId parameter and then tell it to get the value from the list item “Job Opening Number”. Repeat this step for each of the parameters.

The final parameter for an Azure Function is the code that will allow you to call the web service. This is found in the Azure Function properties on portal.azure.com.

Get the code by clicking on “Get function URL”. Copy the part that says “code=”.

Then paste the code into your Flow…

Finally, you can update your list item based on the result of the call your web service…

That’s it! In this series we have done the following:

  1. Created an Azure Function that calls a custom web service and applies some business logic before returning a response
  2. Created a custom data connector that wraps our Azure function and allows for easy integration into a Flow (or PowerApp)
  3. Created a Flow that iterates through items in a SharePoint list and sets a status field based on the response from our Azure Function

How Can We Help? Find out how Lone Peak Software can help you with Azure development.

%d bloggers like this:
search previous next tag category expand menu location phone mail time cart zoom edit close