This post is inspired by a question I received from a previous blog post where the user wants to send a single email reminder for multiple Microsoft List items. The typical Power Automate pattern is one reminder per item. Consolidating items, by owner for example, is harder that you would think. I am using the Issue tracker template for my demo and we will send a single email message for all open items assigned to the same user on a weekly schedule.
Create a new Flow from Power Automate > Create new > Scheduled cloud flow. Provide a Flow name, i.e. “Issue tracker – Weekly report” and click “Create”.

Insert a SharePoint – Get items action and set:
- Site Address and List Name to your target site and list
- Filter Query to:
Status ne 'Completed' or Status ne 'Duplicate'

Insert a Data Operation – Select action and set:
- From to “value” from the previous SharePoint – Get items action
- Map to “Person or group the issue is assigned to” from the previous SharePoint – Get items action

Insert a Initialize variable and set:
- Name to “varAssignedto”
- Type to “Array”
- Value to the following expression:
union(body('Select_-_Assignedto'), body('Select_-_Assignedto'))

Save and test your Flow. Copy the output from the Initialize variable step.

Insert a Data Operation – Parse JSON step and set:
- Content to “varAssignedto” from the previous Initialize variable step
- Click “Generate from sample” and paste in the copied output from the Initialize variable step

Insert a Control – Apply to each action and set:
- Select an output from previous steps to “Body” from the previous Parse JSON step

Add a Data Operation – Filter array action and set:
- From to “value” from the SharePoint – Get items action
- Choose value to “Claims” from the Parse JSON step; “is equal to”; and Choose value to “Person or group the issue is assigned to Claims” from the SharePoint – Get items action

Add a Data Operation – Create HTML table action and set:
- From to “Body” from the previous Filter array action
- Columns to “Custom”:
- Header: Title – Value: “Title” from the previous Filter array action
- Header: DueDate– Value: “DueDate” from the previous Filter array action
- Header: LinkToItem– Value: “{Link}” from the previous Filter array action

The output from the Create HTML table can be messy but there are options to format using CSS if so desired. In my example, I specify Title for the issue name, due date and a link back to the item (See image below). A nice upgrade to this listing would be to combine Title and the link into a single clickable HTML tag.

Finally, add a Send an email (V2) action and set:
- To “Email” from the Parse JSON step
- Subject to “Issue tracker – My items”
- Body to “Output” from Parse JSON step

My completed Flow looks like the image below.

Save and the test the Flow. If all goes well the persons assigned to the issue will receive a single email with all items assigned to them.

I like the idea of this pattern but I would invest time into formatting the HTML table for the best possible user experience prior to production use.
Thanks for reading!
NY
This is super useful ! I didn’t know that we have a Table HTML action, this will save me some …and more string format time, thanks !
LikeLike
Reblogged this on El Bruno and commented:
This is a super useful tip / scenario from my friend Norm !
LikeLike
Thanks, Bruno, I really appreciate that!
LikeLiked by 1 person
Hi Norm and Thank you! I am new with power automate and this helped me alot. I have some concerns and requesting for your help/clarification after doing the test run:
1. Multiple email sent to “assignedto”. – I don’t know if this is the problem but when I added “Email” under “To” from the Parse JSON step under Send an email the flow turns or converted into “Apply to Each”.
Note: Same happened when “Claims” from Parse JSON step” under “Filter Array” (just an observation)
2. Email sent also have the list of action which not belong to that person/persons/group. How can I filter that email to be sent only has/have pending list assigned to that person/persons/group to be sent.
LikeLike
Hi Miko,
1) Does your “Person or group the issue is assigned to” column allow multiple selections? If so, that will cause the “Apply to each”. Interestingly, the template schema has changed and now “Person or group the issue is assigned to” is called “Assigned to”.
2) Possibly related to issue 1. Check the output from Parse JSON action to confirm distinct values.
If you are stuck book some time and we can look into things further. https://calendly.com/norm-young/sharepoint-power-automate-help
Thanks for reading!
NY
LikeLike
This is perfect! Just what I needed! Thank you Norm!
LikeLike
Thanks for saying that Amardip. I appreciate it!
Thanks for reading!
NY
LikeLike
Over the last week I must have followed half a dozen guides for this exact process, and not one has worked. Until now. Thank you!!!
Other than syntax errors, the only place I really got stuck was the Create HTML Table, because the array fields don’t show in the dynamic listing. However, I discovered that if I enter “item()?[‘Title’]” as a function it works. The next time I reopen the flow fresh it looks just like yours.
Now if I could just figure out how to show the values from Choice fields…
LikeLiked by 1 person
Hi Jon,
Thanks for saying that, I really do appreciate it. Let me look into the Choice field stuff and I’ll get back to you.
Thanks for reading!
NY
LikeLike
Thank you, I appreciate that. I actually just found the solution. I just needed to spend a few more minutes hunting to find the exact right post!
https://powerusers.microsoft.com/t5/Building-Flows/Create-HTML-table-from-Sharepoint-List-with-multi-selection/m-p/409714#M47043
Norm Young commented: “Hi Jon, Thanks for saying that, I really do appreciate it. Let me look into the Choice field stuff and I’ll get back to you. Thanks for reading! NY”
LikeLike
Great post as always Norm
LikeLike
Hi Norm,
Many thanks for sharing this helpful post!
Unfortunately I have already got stuck on step 3 – initialize variable.
I am getting the following error when I save at this step:
Correct to include a valid reference to ‘Select_-_Assignedto’ for the input parameter(s) of action ‘Initialize_variable’.
Any ideas what I might be doing wrong?
Kind Regards, Marc
LikeLike
Hi Marc,
Sorry to hear that you are having trouble. The initialize variable step expects the “Select” action name to be “Select – Assignedto”. Either rename the “Select” or update the expression to match your variable name.
I’m happy to help further. https://calendly.com/norm-young/sharepoint-power-automate-help
Thanks for reading.
NY
LikeLike