Project EST – Part 03 – Logic App

As described in part 1 and part 2, my Schedule Tweets solution doesn’t look that bad. But one important component is still missing: sending the tweets…

To Flow or not to Flow…

At first I thought about sending the tweets via Microsoft Flow. But then I had to find out some things:

• Flow is not unlimited and has its own licensing model … was personally new to me … but it is also not my business
• with the flow contained in O365 you get a maximum of 2000 executions per month
• I want to check my list several times per hour … starting a check every 15 minutes means = 4 x 24 x 30 = 2880 Runs
• the restriction that Premium connectors cannot be used in the Free Tier
• this is probably not the last flow … so I would like to have some room to maneuver.

So we had to find another solution…and because Flow in the background is only based on Logic Apps…then we take the…

Well, of course … Logic App

Thanks to the Consumption Model I can do what I want in the Logic App…it is regularly charged against my Azure Subscription…and there are no limits anymore.

So here we go. First create a Logic App and then start the Logic App Designer.

The basic structure was clear quite quickly…I periodically check the list elements and receive the info and then process the elements accordingly:

Now some conditions had to be queried and branches had to be established:

• first only the list elements that have not yet been sent are processed –> a check is carried out for the Boolean value of “Sent”
• then only those elements are further processed that have a send date in the past or are now sent
• then the corresponding graphic attachment must be read for each current element
• the tweet must be sent
• Finally, the “Sent” value in the SharePoint list must be set to “true
• 
  

All in all, it looks like this.

And the tweets are already working… To be on the safe side here again the code of my Logic App