You're Probably Overusing "Apply to each" in Power Automate

JaganReddyK — Tue, 28 Jul 2026 04:47:47 +0000

When I started building Power Automate solutions, my answer to almost every array was the same:

Use "Apply to each."

It worked. My flows ran successfully, and I moved on.

But as projects became larger, I noticed a pattern:

That's when I started looking for ways to simplify my flows—and XPath became one of my favorite techniques for working with XML.

The Problem

Imagine receiving an XML response with hundreds of employee records.

If you only need one employee's name, should your flow really loop through every record?

Probably not.

XPath lets you query XML directly.

Instead of saying:

"Check every employee until you find ID 102."

You simply ask:

"Give me the employee whose ID is 102."

The expression looks like this:

```text id="m8t2p4"
xpath(
xml(outputs('Compose')),
'/Employees/Employee[Id="102"]/Name/text()'
)




The result?



```text id="w5c6y1"
David

That's it.

No loop.

No condition.

Just the data you need.

Using XPath can help you:

It's a small optimization, but when applied across dozens of production flows, the impact adds up.

XPath is ideal when you're working with:

If your data is JSON, Power Automate already provides excellent functions such as filter(), select(), and first().

Choose the right tool for the job.

One lesson I've learned while building automation solutions is this:

The fastest flow isn't always the one with the most actions—it's the one with the fewest necessary actions.

Next time you add an Apply to each, pause for a moment and ask yourself:

Can XPath solve this instead?

You might be surprised how much simpler your flow becomes.

If you enjoy practical tips on Power Automate, SharePoint, Microsoft 365, SPFx, Python, and AI-powered automation, stay connected for more articles.