web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Email "From" value not...
Power Automate
Suggested Answer

Email "From" value not always assigning

(0) ShareShare
ReportReport
Posted on by
I have a Power Automate flow that triggers when an email arrives in a shared inbox. I then have a condition that checks whether the email has been sent from an internal email address. I am having a problem whereby on some runs of the flow, it's successfully checking the value in the "From" dynamic variable. But in other runs, that same "From" variable seems to be empty, or at the very least, it doesn't seem to be able to check the condition.
 
Successful run:
 
As you can see from a successful run of the flow, it's taken the sending email, determined that it matches one of our internal email domains, and set the condition as True.
 
Unsuccessful run:
 
In the unsuccessful run of the flow, there is no email address showing in the "From" dynamic variable, unlike the first picture. When I check the outputs of the "When an email arrives in a shared mailbox" trigger, however, the body/from value is there in the JSON. It also provides the pop up message as can be seen.
 
On a separate, but related note, whether the sending email address is internal or external, when it is an unsuccessful run, the condition always sets as true, sending it down our 'Internal Only' path.
 
Am I missing something here? Any help would be appreciated. If further information or context is required, I can provide it.
 
Thanks,
I have the same question (0)
  • Suggested answer
    Sunil Kumar Pashikanti Profile Picture
    1,535 Moderator on at
     
    This is a known Power Automate issue. The From dynamic value is not always resolved correctly in shared mailbox triggers, even though the value exists in the trigger JSON. When this happens, conditions may still evaluate as True.

    To fix this, stop using the From dynamic token. Instead, read the sender directly from the trigger outputs using an expression and base your condition on that value. This makes the check reliable and prevents incorrect routing.
     
    Read the sender address directly from trigger outputs, store it in a variable, run your condition against that variable.
    and(
      not(empty(triggerOutputs()?['body/from/emailAddress/address'])),
      contains(triggerOutputs()?['body/from/emailAddress/address'], 'yourdomain.com')
    )
    This works consistently because:
         It reads directly from the trigger JSON
         It does not rely on UI-resolved tokens
     
    Best practices
    Always store important trigger values in a Compose or Variable first
    Avoid using dynamic tokens directly in conditions
    Use triggerOutputs() expressions for reliability
    Log the sender email to run history during testing
    Add a null check before running contains logic
     
    ✅ If this answer helped resolve your issue, please mark it as Accepted so it can help others with the same problem.
    👍 Feel free to Like the post if you found it useful.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the March Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Haque Profile Picture

Haque 612

#2
Valantis Profile Picture

Valantis 344

#3
11manish Profile Picture

11manish 326

Last 30 days Overall leaderboard