Power Automate

How to merge multiple excel rows and send one Teams message to an email ID mentioned in the row

(1) Share

Report

Posted on by Cayden Asks

Hi Everyone,

Please help a self learn newbie out.

I have this excel file where there is a common key (user email) that can be used to link the records together.

User email	Case ID	Description	Creation date
User1@email.com	12345	Abcdef	12/01/26
User1@email.com	23456	Bcedfgh	18/01/26

I am able to send one Teams message per row to the user now based on the User email in first column. I am trying to enhance it and wish to send one message which has a table containing all of the records under the same user email.

As this file can have multiple different user email and cases, this flow needs to handle that. Appreciate it if anyone can let me know how it can be done!

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (0)

David_MA 14,090 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

You don't show your flow, but I assume you are using the get rows action with a filter query. If so, add a Select action to your flow with the items from the get rows action. Then configure the Select action to return the data in your table. Follow it with a Create HTML table action using the output of the Select action. You can then insert the output of the Create HTML table action in your email.

Was this reply helpful? Yes No
Suggested answer

wolenberg_ 1,476 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hello,

Right now your flow is treating every row in Excel as a separate message, which is why people get spammed with multiple Teams posts. What you really want is to bundle all the rows for the same email together and send just one message.

The trick is simple:
• First, pull all the rows from Excel.
• Then, look at the unique email addresses.
• For each email, gather all the case details that belong to them into one block of text.
• Finally, send that block as a single Teams message.

That way, instead of User1 getting two separate messages for case 12345 and 23456, they’ll just get one message listing both cases neatly.

Was this reply helpful? Yes No

Cayden Asks

6 on at

Like (0)

Report

Copy link

Link copied!

Apologies, the corporate policy makes it hard to access the forums even if it is for a legit purpose.

I managed to make it work, only 1 Teams message is sent to each User. I used a union(body('Select'), body('Select')) in Compose to get unique list of user emails so I will not miss out anyone.

However, the table sent contains 2 additional columns (odata and ItemInternalId), I am wondering if there is a way to remove them. Appreciate if anyone can shed some light. I have attached my flow below.

The table sent

@odata.etag	ItemInternalID	UserEmail	Case ID	Description	Creation Date
	xxxxxxxxxx-xxxxxxx-xxxxxxxx	User1@email.com	12345	Abcdef	12/1/2026
	xxxxxxxxxx-xxxxxxx-xxxxxxxx	User1@email.com	23456	Bcdefgh	18/1/2026