Are there any templates available to add HTML to email sent using Microsoft Flow? Ie. A bar across the top of the email, a company logo at the top of the email, etc.
You should be able to write simple HTML language in the Send an Email action Body field, when the Is HTML is set to Yes:
As a reference:
HTML format for Approval Email is currently not supported.
Please check the following thread for more details:
Is there a way to add html code to display date or time in the email that is sent from Flow?
I have been able to insert a logo, but not been able to insert a current date or time to be sent out with the email. I have already set the "Is HTML" to Yes.
You'll need the UTCnow() function to get the current time (and date). this can then be added into the body of the email.
On a similar note, I've been creating some 'better' looking emails by composing them in outlook, sending them to myself then right click 'view source', copy all the html and then paste it in the 'body' box. This will replicate the email as seen in outlook. It might not be the most efficient coding but its quick and easy to do.
If required, you can insert dynamic content into the html code to make the email display info specific to the flow, i.e. a list ID number or submitter's name...
@Anonymous I've tried using the UTCnow() function but it just prints "UTCnow()". Do I need to include anything else to make it know I am calling a function?
Ahhhh I see. Thank you! I didn't even see the expression function earlier. It worked using this
I managed to get HTML to work in the "Send approval email" in flow, try the below...
All i did was add "Speakmarks to the start of the message/email in flow"....
Look at how the approval email came through...
This does not work for approval emails (start an approval email which is sent) as no drop down for HTML and nothing in the settings for that step either. I would have expected that this could be applied to all email templates that Flow sends so currently it is lacking this addition of functionality. 😞
This doesnt work for approval flow. . I am struggling to find a way to have HTML tags working in my flow to make Emails look cleaner. Any luck anyone?
HTML isn't an option for the approval emails, but the details section of an approval supports markdown. Details and samples are available here.
Seems a bit of a mystery why it has taken so long for someone to comment on this about markdown. Planning to put it to the test today as my workaround was to use Send email with options format but unfortunately the email templates for that are not as nice as the approval emails
The error message doesn't seem to be related to the markdown, but instead it's complaining about a field that "doesn't exist". I'd verify if this field has a value, and if so, create another small flow just for testing this field.
Hmmm strange as I added the values from the dynamic content at the same time as trying to draft table, so they are available.
I tried removing some and it triggered the approval email but it does not come in table format, instead I have bullets?
Hmm. Apparently there's a relatively new bug that is preventing markdown from rendering in all environments. I just did a test myselft, and the tables are working in outlook online but not in outlook 2016. The tables also render correctly in the approvals center in flow. Here is another thread talking about this issue.
I tested at my end with Markdown functionalities. The problem I am seeing now is that the manager receives the email in a formatted way but once the form is approved or rejects, the user is receiving email information in a really ugly formatted way . I dont know if there is a way to fix thi?
I have attached the pictures below. Please guide.
Check out new user group experience and if you are a leader please create your group
May the fourth be with you, join us online!
See the latest Power Automate innovations, updates, and demos from the Microsoft Business Applications Launch Event.
ISV Studio is the go-to Power Platform destination for ISV’s to monitor & manage applications post-AppSource publish.