If you’ve been using Power Automate for a while and you’re still just sending basic email notifications, you’re leaving a lot on the table. Power Automate is capable of far more than most small business users ever discover — and the features that make the biggest difference aren’t complicated once you know they exist.
Here are ten tricks that our clients use regularly to get more out of Power Automate without writing a single line of code.
1. Use “Apply to Each” with a Filter First
Most people know about the Apply to Each action for looping through a list of items. What fewer people do is filter the list before the loop starts. If you’re pulling 500 records from a SharePoint List and only need to act on the 12 that meet a condition, processing all 500 wastes run time and burns through your action limits.
Use the Filter Array action before your Apply to Each loop to trim the dataset down to only the records you need. Your flows run faster, cost fewer actions, and are easier to debug when something goes wrong.
2. Run Flows in Parallel Branches
By default, Power Automate runs actions sequentially — step one finishes before step two starts. But many workflows have independent tasks that don’t need to wait on each other. Sending a confirmation email and creating a SharePoint record don’t need to happen in order — they just both need to happen.
Add a Parallel Branch to run those actions simultaneously. On a flow with several independent steps, this can cut total run time by more than half. In the flow designer, click the plus icon between steps and select Add a Parallel Branch.
3. Set Up Run-After Conditions for Error Handling
Every action in Power Automate has a Run After setting that controls when it executes — not just after success, but after failure, timeout, or being skipped. Most people never touch this setting, which means their flows silently fail with no notification.
Configure a Send Email action at the end of your flow with Run After set to “has failed.” When something breaks, you get an immediate notification with the flow name and the step that failed. This alone eliminates the most common complaint we hear about Power Automate: “I didn’t know it stopped working.”
4. Use Variables to Track State Across a Loop
If you need to count how many records were processed, build a running total, or track whether any item in a loop triggered a specific condition, you need variables. Initialize a variable before your Apply to Each loop, then use the Increment Variable or Set Variable action inside the loop to update it as each item is processed.
This is how you build flows that can send a summary email at the end saying “12 records processed, 2 flagged for review” instead of just running silently and hoping everything worked.
5. Use the Compose Action as a Scratchpad
The Compose action is one of the most underused tools in Power Automate. It takes any input — text, a dynamic value, an expression — and outputs it so you can reference it later. Think of it as a named variable for a value you need to reuse or transform.
Instead of writing the same long expression three times in different actions, Compose it once and reference the output everywhere else. It also makes complex flows significantly easier to read and debug because you can label exactly what each piece of data represents.
6. Schedule Flows With Dynamic Timing Using Expressions
The Recurrence trigger lets you schedule a flow to run at a set interval, but it’s static — the same time every day, every week, every month. For more dynamic scheduling, combine a Recurrence trigger with expressions that calculate dates at runtime.
For example, using the expression addDays(utcNow(), -7) gives you the date exactly seven days ago — useful for pulling last week’s records every Monday morning without hardcoding any dates. The formatDateTime expression lets you control exactly how those dates are formatted for use in queries or email subjects.
7. Use HTTP Webhooks to Trigger Flows From Anything
Most people think of Power Automate flows as triggered by Microsoft services — a SharePoint item created, an email received, a form submitted. But the HTTP Request trigger gives your flow a unique URL that anything on the internet can call.
This means you can trigger a Power Automate flow from a website form, a third-party app, a Python script, or any system that can make an HTTP POST request. It opens up integrations that would otherwise require custom connectors or premium licenses. The trigger is included with standard Power Automate and generates a unique URL the moment you save the flow.
8. Use Do Until Loops for Polling and Waiting
Sometimes your flow needs to wait for something to happen before it can proceed — a record to reach a certain status, a file to appear in a folder, an approval that might take hours. The Do Until action loops repeatedly until a condition is met, with a configurable delay between iterations and a maximum count to prevent infinite loops.
A practical example: after submitting a request to an external system, use Do Until to check the status every five minutes until it returns “complete,” then proceed with the next steps. This replaces the need for complex multi-flow architectures just to handle asynchronous processes.
9. Store Sensitive Values in Environment Variables
If your flows use API keys, connection strings, email addresses, or other values that might change or that you don’t want hardcoded in dozens of flows, use Environment Variables instead of typing the value directly into each action.
Environment Variables are defined once at the solution level and referenced across as many flows as you need. When the value changes — a new API key, a different notification email, a updated endpoint URL — you change it in one place and every flow picks it up automatically. This is also the right way to handle differences between development and production environments.
10. Use the “Send an HTTP Request to SharePoint” Action to Do Things the SharePoint Connector Can’t
The standard SharePoint connector in Power Automate covers most common operations — get items, create item, update item, delete item. But SharePoint’s REST API can do far more than the connector exposes, and the Send an HTTP Request to SharePoint action gives you direct access to that full API without leaving Power Automate.
Need to update a managed metadata field? Retrieve items from a specific view? Access list permissions programmatically? All of this is available through the HTTP request action using SharePoint’s REST endpoints. It requires a bit more technical comfort than the standard connector, but it closes the gap between what Power Automate can do out of the box and what SharePoint can actually do.
The Bigger Picture
Power Automate rewards the people who take time to understand it beyond the basics. Most of the flows we see from new users are functional but inefficient — they process more data than they need to, fail silently when something goes wrong, and hardcode values that should be variables. These ten patterns fix the most common versions of those problems.
If you’re building Power Automate flows for your business and hitting walls — or if you’ve inherited flows that nobody fully understands — that’s exactly the kind of situation we untangle.
Ready to talk through your options? Reach out to Anthony at AccessEvolved — email anthony@accessevolved.com or call 212-951-1010. No sales pitch, just a straight conversation about what makes sense for your situation.