Send an email with options UserEmailAddress returning blank

[Anonymous]

Hi all,

I have a weird issue. I have the simplest of all Flows set up

Trigger: manually trigger a flow

Send an email with options (Approve, Reject)

When the receiver approves or rejects I just want to capture their email. 

So I have a variable set to the UserEmailAddress from the "Send email with options" action. But it's returning blank.

I set a condition on the response, so if response = "Approve" send an email and that is working fine, so Flow is able to capture the response, but not the email address. Can anyone successfully capture the responder's email address?

I basically just need to know who is actually responding to the email, and document that.

Before you say "you should just use approvals" - I need to include an html table in the body of the email. 

Before you tell me to try markup - I have, it doesn't render in the Teams "approval" notification, and also doesn't seem to be very friendly in terms of dynamic column sizing. 

So this is (to my knowledge) my only option. 

[savelazq]

Hi,

I have an example on how to capture the approver’s email and be directly sent to the recipient as a response.

You can still make your flow work without using variable; however, you can use variable if you want to.

Please look at the example provided below

Within the body of the email click to Add an Expression (fx blue icon)

Type this line: 

body('Start_and_wait_for_an_approval')?['responses'][0]['responder']['email']

Example of e-mail received

Regards,

Sam

-------

Community Support Team _ Sam Velazquez

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

Hi Sam thanks for this but I'm specifically avoiding the "approval" actions because I need to include an html table and that does not work in that action

So I need this to work with the "Send an email with options" action. Can you test that action and see if you are able to get the responder's email?

[darshanamin26]

Hi,

Thanks for you response. Would you please send us more details about your flow would be great if you send us screenshot for your flow.  

Regards,

Darshan

-------

Community Support Team _ Darshan Amin

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

Here is the run, notice that the variable is empty:

And here is the configuration

Can you try recreating this flow? Are you able to extract the responder's email address in any way??

[darshanamin26]

Hi, 

I run the same flow and it seems working for me, I'm able to see responder's email address as well as email from flow. attaching the screenshot for the reference

Regards,

Darshan

-------

Community Support Team _ Darshan Amin

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

Ok, I have no idea why mine is not working then...

The UserEmailAddress doesn't even show in the action:

[Anonymous]

Ok, I have narrowed it down a little further. It looks like the buttons in the preview DO work, but in the body they do not. 

See below: the buttons under "your input is required" work, but the buttons in the body don't. For specific reasons I NEED these body buttons to work. 

If you run the flow and try to use the buttons in the body of the email, does it work?

[darshanamin26]

Hi, 

I checked the flow again and button on the body part of the email seems working for me as well. Opening a support case with outlook team seems a good option to get more assistance on this issue.  

Regards,

Darshan

-------

Community Support Team _ Darshan Amin

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

Hihi,

Was this ever solved, I'm running into this exact same issue and I'm not sure what is the solution.

[Anonymous]

Hey, no I think it has to do with email security settings. I think my org has some html blocking settings or something, which meant that this just would never work for us. 

[skillsy]

Thanks for posting @Anonymous  and just adding to this that I have set the three yes/no fields on the "Send email with options" to HTML: Yes , Hide HTML: No and HTML Confirm: No. and I get all nulls returned other than the selectedOption which is not optimal. It looks buggy rather than a security setting somewhere as I can't see a use case for not returning a name if internal user replied.

[AnkitN]

Hi @skillsy ,

Were you able to get the cause/solution why "UserEmailAdress" is coming null.

[Anonymous]

@Anonymous , @darshanamin26 , @savelazq 
Facing the same problem, getting the userid and useremailaddress as null. Did anyone found a solution for this?

[VictorIvanidze]

Hello,

I've just tested. The same behavior: the buttons under "your input is required" work , but do not work the blue buttons under "Select one of options below to respond".

[Anonymous]

Still no resolution for me on this. 

Had to resort to Teams Approval action and no HTML table in the body - which is a huge let down. 

[jhoff80]

This exact issue is breaking my intended automation as well.  The buttons in the preview work, but the HTML buttons in the message body don't.  Which unfortunately means that people who use their phones or a browser window to check their email and try to respond will break the flow.

[SimonHudson]

I'm seeing exactly the same issue. I'm going to try it on another tenant that is not locked down to try to eliminate anything on the permissions and security side.

[kat_rock]

I know the original post is quite old now, but for anyone else having the same issue, I raised a ticket with Microsoft and they confirmed the issue @Anonymous  reported is still a problem in Sep-2023: i.e. you can only get the user's details if the user clicks the buttons in the preview/message card. If the user clicks the buttons in the html version of the email you can only get the user's selection, you will not get any other details like their email address. Microsoft say this is 'by design'.

I've asked them if there is a workaround but I don't have high hopes.

So it is still not possible to emulate the Power Automate approvals process and use html formatting. Seems your only options are sending your users a very suspicious (but secure) Approvals email or a nicely formatted (but unsecure) html email with options.

[Eraser67]

Any hopes for this issue ?