Building a Modern SharePoint Solution: Part 8 – Sending a Tweet from Microsoft Flow

In my previous post, I showed you how to set up multiple approvals in a workflow. This post is going to continue along the requirements I set out in part 1 of this series.  I’ll be walking through sending a tweet from a Microsoft Flow.  It’s pretty straightforward.  Microsoft even has it as a template I believe, but I still wanted to illustrate how to do it because this is actually part of a bigger flow and an item in a solution’s requirements.  We’ll be continuing on from where I left off in part 8 of this series, but the steps I have here can be picked up and added to any flow you will be working on.

Posts in this series:

• Preparing SharePoint
• Integrating PowerApps as a Custom List Form
• Customizations All List Form PowerApps Should Have
• Setting a SharePoint People Picker Field Programmatically in PowerApps
• Cascading Drop-down Lists and People Picker in PowerApps
• Create a Flow to be Started Manually
• Creating a Multiple Approver Microsoft Flow
• Sending a Tweet from Microsoft Flow
• Starting a Microsoft Flow from a PowerApp

Sending a Tweet from Microsoft Flow

I have already added the necessary branch to my flow from the communications approval (see last post).  The steps to send out the tweet are pretty straight forward:

1. Click on Add Action.
2. Type Twitter into the search function.
3. Select Twitter – Post a tweet.

4. If this is your first time adding the connector you will be prompted to sign in.  Do so with the appropriate credentials.
5. Once you have made the connection the Twitter post action will show up.  Use the Twitter description of your list item from the Dynamic Content.

6. The last step we are going to add is a notification to all parties once the tweet has been added.  But first, we are going to ensure it did.  Add another condition after the tweet
7. Click on “Edit in advanced mode” cause we are going to be using an expression here
8. Add the expression: @empty(body(‘Post_a_tweet’)[‘TweetId’], ”).  This expression is checking to see if the ID of the Tweet returned from the connector is empty or not.

9. Then add a notification to the branches indicating if the tweet was successful or not (I won’t cover that since I showed you how to email in my previous post).

I know you won’t be able to make out much, but just to give you an idea of how large something straightforward can be, here’s a screenshot of the complete flow (approvals and all).

Last step in this solution is to actually start the workflow from the form.

Thanks for reading!!