Power Automate VS Logic Apps. Power Automate Cases

Good day to all! In a previous article on Power Automate and Logic Apps , we looked at the main differences between Power Automate and Logic Apps. Today I would like to move on and show interesting opportunities that can be realized with these products. In this article, we'll see a few cases that you can implement with Power Automate.

Microsoft Power Automate


This product provides a wide range of connectors to various services, as well as triggers, for automatic and instant start of flows, due to the occurrence of a certain event. It also supports the launch of threads on a schedule or by button.

1. Automatic registration of calls


One of the cases may be the implementation of automatic registration of calls. The trigger of the stream, in this case, will be the receipt of a mail notification to a specific mailbox, after which further logic is processed:



When setting up the trigger “When a new email arrives”, you can use various filters to determine the required event for the trigger to start:



For example, you can start a stream only for messages with attachments or for messages that have maximum importance. You can also start the stream if the message arrived in a specific folder of the mailbox. In addition, it is possible to filter letters by the desired substring in the subject line.
After the necessary calculations are made and all the necessary information is received, you can create an item in the SharePoint list using substitutions from other actions:



Using this stream, you can easily pick up the necessary mail notifications, parse them into components and create entries in other systems.

2. PowerApps


One of the standard scenarios is sending the object for approval to the approving persons. To implement this scenario, you can make a button in PowerApps and, when you click on it, start the Power Automate stream:



As you can see, in this stream, the starting trigger is PowerApps. A distinctive feature of this trigger is that you can request information from PowerApps inside the Power Automate stream:



It works as follows: when you need to get any information from PowerApps, you click on the “Ask in PowerApps” item. After that, a variable is created that can be used in all actions of this Power Automate stream. It remains only when starting the stream from PowerApps to transfer the value for this variable into the stream.

3. Starting a stream using an HTTP request


The third case I would like to talk about is launching a Power Automate stream using an HTTP request. In some cases, especially true for various integration stories, it is necessary to start a Power Automate stream through an HTTP request, passing various parameters into the stream. This is done quite simply. As a trigger, the action “Upon receipt of an HTTP request” is used: HTTP:



The HTTP POST URL is generated automatically when the stream is first saved. It is at this address that you need to send a POST request to start this stream. As parameters, at startup, you can transfer various information, for example, in this case, the SharePointID attribute is transferred from outside. In order to create a similar input circuit, you need to click on the item “Use a payload example to create a circuit”, then insert an example of JSON which will come into the stream:



After clicking on “Finish”, the JSON scheme of the request text for this actions. Now the SharePointID attribute can be used in all actions of this stream as a substitution:



It is worth noting that the “Upon receipt of an HTTP request” trigger is included in the Premium Connectors section and is available only when you purchase a separate plan for this product.

In the next article, we’ll talk about various cases that can be implemented using Logic Apps.

All Articles