Welcome to our Microsoft Flow template archive created by Manuel Gomes and with contributions from other people.
This list contains some of the templates that we find useful. Microsoft also has a list so you can check both to find something useful for you.
Total number of templates: 8
Last update: Feb 8, 2020
Jump to the section:
- Microsoft Forms
- Data Types
Add a buffer after the meetings
Adds a 15-minute buffer as soon as you create a new appointment.
Move all emails to a folder that arrive after working hours
If you receive an email between the defined working hours, it’s moved to a folder until the next Power Automation picks it up, during working hours, and transfers it back.
Move back the emails to the inbox at the start of the day
At the beginning of the day, move all emails that arrived outside working hours and move them back to the Inbox.
Parse choice elements
Parse multi-choice element to insert into SharePoint
This template provides a full Flow that gets the information from Microsoft Form and parses it so that we can insert it into a SharePoint choice column. I wrote an article explaining all the processes so, if you have any questions, you can check it here.
Access Excel Using a Custom Path
How to go around the limitation where an Excel can’t be accessed with a Dynamic Path. This template works as a “function” so you can import it and use it in multiple Flows.
Convert timestamp into a date
This template provides a formula that you can convert a timestamp to date and not much more. We’ve only focused on demonstrating the overall workflow and how can you use it. The template can be used, for example, when integrating with APIs that, usually, return timestamps.
Note: that this template is only to demonstrate the formula’s usage, so please adjust it to your needs. Also, you’ll see in Microsoft’s documentation description of timestamps as objects like ‘2019-10-28T10:10:10Z’. Intentionally I’m calling these Dates and keep the UNIX concept of the timestamp to avoid confusion.
Example of a Get Trigger
This template provides a simple Flow that demonstrates how to call a Request trigger using the Get method. To be able to test it, you need to add your destination Flow’s URL, but you can check the Parse Information section for an example. I wrote an article explaining all the processes so, if you have any questions, you can check it here.
Parse UTM Parameters
This template provides a full Flow that gets a URL and parses the UTM values into individual variables. I wrote an article explaining all the processes so, if you have any questions, you can check it here.
Parse UTM Parameters With Request Trigger
This template provides a full Flow that gets a URL and parses the UTM values into individual variables. The template is similar to the one above but uses the Request trigger so that we can re-use the logic in other Flows. If you don’t know how to call a request Flow, please check the Request Trigger section for an example. I wrote an article explaining all the process so, if you have any questions, you can check it here.
How to use the templates
You can use my step-by-step tutorial in how importing and exporting works. It’s super easy with only some minor things to take in consideration.
You can also check our articles on Microsoft Flow to learn more about the tool and know-how to create your own. I encourage you to download the templates and adapt them to your needs. Don’t worry about attribution. It’s not necessary, but I appreciate if you do.
Have one of your own?
Awesome, send it my way via email with a simple explanation of what it does so that I can include it. I’ll attribute submitted templates, so please include any information you want to be displayed. I’ll test them first to ensure quality and that they don’t do anything strange. I’ll only post them if I find that there’s something worthwhile that others can benefit. It can also take me a while depending on the workload that I have at the time, but I promise to look at all of them.
Don’t submit any template:
- That depends on private APIs
- that collect information from the user of any sort.
- Needs another template or flow to run.
Please also submit only templates that you created, and you have permission to share. I cannot be considered responsible for any provided template being proprietary. Please contact me if you find any violation of the terms described below, and I’ll remove it immediately.
The templates in this archive have been tested as of the date each was added to splash.pm for compatibility with the then-current versions of Microsoft’s Flow. Please feel free to use these templates and adapt them to fit your specific needs.
However, please keep in mind that splash.pm and its team, cannot and do not guarantee that the template will remain compatible with future updates. Moreover, the templates linked on this page are provided free of charge and as-is without any express or implied warranties including implied warranties of merchantability, fitness for a particular purpose, and non-infringement. The SplashPM Team makes no specific promises about the templates, the particular functions of the templates, or their reliability, availability, or ability to meet your needs. Also, the SplashPM Team will not be liable to you for any lost profits or other consequential, special, indirect, or incidental damages arising out of or in connection with your use of the template.