Cheat sheet
Power Automate Trigger Conditions Cheat Sheet
Common trigger condition patterns for status changes, empty checks, approvals, recurrence guards, and noisy list updates.
Power Automate trigger conditionsflow trigger conditionSharePoint trigger condition
Who this helps
Flow builders trying to reduce unnecessary runs and avoid infinite loops.
What to standardize
- Keep trigger conditions small and readable.
- Use them to reduce noise, not to hide complex process logic.
- Document every condition in the flow notes.
- Test create and update events separately.
Examples
Only run for submitted requests
Start a flow only when a SharePoint choice field is Submitted.
Formula / code
@equals(triggerOutputs()?['body/RequestStatus/Value'], 'Submitted')Expected result: The flow ignores draft and closed updates.
Common mistakes
- Using the wrong dynamic path
- Forgetting choice /Value
- Adding too many conditions at the trigger