Let's POWER Automate

From no-code to low-code

Menu
  • Expressions
  • Filters
  • General
  • Triggers
  • Application specific solutions
    • Dataverse
    • Excel
    • Forms
    • Planner
    • Outlook
    • SharePoint
    • Teams
  • Resources
  • Get help with flow
Menu

Allow users to manage emails content outside of Power Automate

Posted on August 28, 2022August 28, 2022 by Tom

“I’d like to give users the possibility to manage their own emails that’ll be sent by a Power Automate flow, can I do it without sharing the flow?”


Every Power Automate flow that you build has some fixed parts. The trigger is connected to a fixed location, many of the actions are using fixed locations, emails have a fixed text… But in some situations building a fixed flow can make it very complicated – that’s why you should use configuration lists. Not only will configuration lists make your flow simpler, but they’ll also allow users to modify the flow behaviour.

You can have a configuration list to simplify approval flows, or you can have a configuration list with emails. And that’s the topic of this post – how do you allow users to edit emails content without accessing the flow?

Create configuration list with the emails

As already mentioned, you’ll need a SharePoint configuration list with at least 3 columns – the email unique identifier (Title), email subject (Single line of text), and email text (Multiple lines of text with rich text enabled).

The main trick is that the rich text fields use the same HTML format as emails do. You can define the full email including formatting in the field and then use it as the email body.

Power Automate users manage emails

Once you have the configuration list do a lookup in your flow and send the email.

Add some placeholders

But there’s one more step to take. If you used just the defined email text, you’d lose one of the most valuable functionalities – using dynamic contents in the emails. Since the email can contain some dynamic parts, you might need a few placeholders.

Placeholder is a fixed string that’ll mark a location for a dynamic content. I prefer defining placeholders with ##, e.g. ##Name## to mark the location of the name.

The placeholders must be a fixed list! Users can’t create their own placeholders as every placeholder must be handled in the flow with the replace(…) expression.

Instead of using the email text directly, replace all the placeholders with dynamic contents, e.g.

replace(items('Apply_to_each')?['EmailText'],'##Name##', outputs('Compose'))
Power Automate users manage emails

After the expressions replace all the placeholders, it’ll send the customised email with the correct values.

Summary

Configuration lists are one of the most powerful concepts when you build a flow. Not only can they make your Power Automate flow simpler, you can use them to allow users to change part of the flow without touching the flow, e.g. to manage emails wording. Use the multiple lines of text column with enabled rich text editor, define a few placeholders, and let users to manage the emails by themselves.


Do you struggle with the various expressions, conditions, filters, or HTTP requests available in Power Automate?

I send one email per week with a summary of the new solutions, designed to help even non IT people to automate some of their repetitive tasks.

All subscribers have also access to resources like a SharePoint Filter Query cheat sheet or Date expressions cheat sheet.

Zero spam, unsubscribe anytime.

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Do you know what to do, but not how to do it?

Get The Ultimate Power Automate expressions cheat sheet and translate your thoughts into flows with ease!


NEW! Master the HTTP requests to SharePoint with a new cheat sheet!

Do you struggle with the various expressions, conditions, filters, or HTTP requests available in Power Automate?

I send one email per week with a summary of the new solutions, designed to help even non IT people to automate some of their repetitive tasks.

All subscribers have also access to resources like a SharePoint Filter Query cheat sheet or Date expressions cheat sheet.

Zero spam, unsubscribe anytime.

Hello and welcome!

My name is Tom and I'm a business process automation consultant and Microsoft MVP living in the Czech Republic. I’ve been working with Microsoft technologies for almost 10 years, currently using mainly Power Automate, SharePoint, Teams, and the other M365 tools.

I believe that everyone can automate part of their work with the Power Automate platform. You can achieve a lot by "clicking" the flows in the designer, but you can achieve much more if you add a bit of coding knowledge. And that's what this blog is about.

To make the step from no-code Power Automate flows to low-code flows: using basic coding knowledge to build more complex yet more efficient flows to automate more of your daily tasks.

  • Use Power Automate to forward Outlook events upon registrationJanuary 29, 2023
  • Why the condition is false for the same numbers (Power Automate)January 25, 2023
  • How to forward event invitation to other calendar (Power Automate)January 22, 2023
  • Run ‘For selected item’ flow from non-default environment (Power Automate)January 18, 2023
  • Hide button in SharePoint list after Power Automate flow startedJanuary 15, 2023

Power Automate blogs worth visiting

Damien Bird
Dennis (Expiscornovus)
Paul Murana

©2023 Let's POWER Automate | Theme by SuperbThemes