When a New Email Arrives (V3) multiple accounts?

[midland192]

Hi All

Not sure if this is possible but.....

I have a flow which is trigged when a new email arrives in a specific mailbox with certain criteria.  

However the same flow needs to run on another mailbox

What I've done is just copied the flow and changed the start trigger to the different mailbox.  It works OK but means if I make a chane to one flow then I have to repeat it on the other

Is there any method whereby the start trigger for 'When a new email arrives' can look on multiple mailboxes?  I can only seem to make one connection at a time to the mailbox

any suggestions or advice appreciated

Paul

[yashag2255 · Accepted solution]

Hi @midland192 

The when an email arrives trigger is designed that way to look for emails on a specific email box only and you can provide only one connection to the connection provider for one flow. To replicate to other mailboxes, you will have to create a copy of the flow an change the connections. You can also export the flow as a zip file and then import it again and provide the connection during the import (doing this will require you to provide the connection only once)

Hope this Helps!

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

[midland192]

thanks for reply

your answer confirms what I thought that its not possible to create multiple connections to different mailboxes.  I'd already created a copy of the flow and modified the start trigger connection.  I just wanted to check that there wasnt some trick I was missing to avoic creating copies

thanks

Paul

[dmorrell]

You can break the flow into pieces

Set up as many flows as you need that trigger on a specific user's mailbox and extract whatever data you need from the email. Then send this to a separate HTML triggered flow which contains the bulk of the logic. This way you have a central flow that you can keep updated and peripheral ones that just feed data to it.

[Yobeekster]

Hi, this is what I did, but there maybe a better approach by using Exchange to create rules to forward all emails to an alias email that would then be used in only one flow. The benefit is that you would not need to change the flow or create an additional flow for new users. 

The result would be having a Sharepoint list with one copy of an email, that Powerapps would then use to show in a gallery, albeit using filters to show only the current users emails. 

***Update: I have created a Shared Email that only the admin has access to. In Exchange settings, I created a rule that Bcc's a message for all incoming emails to the organization. It is that email that is used in a Flow that creates a copy to Sharepoint.

Exchange rule:

Settings for rule:

1. The result is that the "To" and "CC" metadata is maintained, where as the "BCC" would be the above noted Shared Email. 
2. Since the rule is set for the organization for all emails, then it doesn't matter when adding/removing people to the organization. 
3. Only one flow is required without having to add new flows for new people, nor editing the flow. Stays done.
4. All the metadata is stored in Sharepoint, which can then be used in Powerapps as required, by using filters and other logic. 
5. Emails can now be sent/replied to from Powerapps if desired by pulling Sharepoint data.