Power Automate flow runs too often, can I filter the trigger?
A trigger on SharePoint or Outlook runs on every change by default. Trigger conditions filter server-side, so you pay no runs for irrelevant events. Saves directly on throttling and pricing tier.
Try this first
- 1Open trigger > Settings > Trigger Conditions. Add an OData expression, e.g. @equals(triggerOutputs()?['body/Status'], 'Approved').
- 2Test by making an irrelevant change: without trigger condition the flow runs, with correct it doesn't. Otherwise the syntax is wrong (sometimes silent).
- 3SharePoint: condition can be on columns, status, lookup fields. Much cheaper than 'Apply to each' with an if inside.
- 4Keep conditions simple: 1 or 2 conditions. Complex boolean logic in trigger-condition is hard to debug.
- 5For flows with dynamic conditions: use trigger-condition for the base (e.g. status), filter inside the flow for specifics.
When to bring us in
Got Power Automate flows running too often and burning quota, the win is usually in trigger conditions. We can look.
See also
- n8n: self-host or cloud?Self-hosted is cheaper at volume and keeps data local. Cloud removes ops burden.
- Zapier or Make: which fits better?Zapier is straight-line; Make handles complex flows with routers and iterators for less money.
- Power Automate Cloud or Desktop: which to use?Cloud for SaaS integrations and triggers. Desktop for RPA against legacy Windows apps without APIs.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.