cancel
Showing results for 
Search instead for 
Did you mean: 

Add the From field on the action “Send Approval email”

Add the From field on the action “Send Approval email” like the "Send email" Action

Status: Completed

You can now customize who the Approval appears from - read more here: https://flow.microsoft.com/blog/button-types-more/

Comments
Level: Powered On

@comSensLost I would definitely prefer "do-not-reply" over the Flow author's address.  It makes sense to me that a Flow connector would use the context of the person who actually initiates the Flow, not the author.  This is something that exist in other workflow tools.

Level: Powered On

We are also having the same issue. We have an email that is updating a ticketing system, the ticketing system picks up the from address in the email, and instead of the name of the user who created the list item, its putting the name of the author of the

 

Flow in the From field of the email. Any updates or notification of the status of the ticket comes to the author instead of the user who had created the item. This is a big issue.

 

 

Level: Powered On

It would be great to have the ability to specify the sender for Modern Approval emails.

 

Currently these approvals are sent from Microsoft Flow <maccount@microsoft.com>. Users who are not aware of this address will suspect that the email is either junk or spam, which could potentially cause them to delete or ignore the approval.

 

Flow.jpg

 

 

Level: Power Up

Absolute must-have. It's ridiculous the person creating a flow is the sender of e-mails that he/she may have nothing to do with.

Anonymous
Not applicable

Hi

 

When we create approval flow using MS flow "start an approval process" option to approve/ reject the request, "From" adress in approval emails by default is "Microsoft Flow <maccount@microsoft.com>".

 

I would suggest to add "From" field to this option, so that email can be sent from trusted source and users should be able to open the email considering it an Organizational email.

 

In our scenario, this requirement seems very important as user might not open emails coming from "Microsoft Flow <maccount@microsoft.com>".