Maker/Toolkit

Tool · Power Automate · Triggers

Trigger Condition Builder

Build Power Automate trigger conditions without guesswork, so a flow only starts when it should. For SharePoint, Dataverse, Outlook and other triggers.

Works with
  • Power Automate
  • SharePoint
  • Dataverse
  • Outlook
Trigger
Run when

Conditions

Trigger condition

  1. On the trigger, open Settings and find Trigger conditions.
  2. Add a condition and paste this line.
@equals(triggerOutputs()?['body/Status/Value'], 'Approved')
  • When a condition is false, the flow doesn’t start at all, so it uses no runs and doesn’t appear in run history.
  • Use internal column names. Choice and lookup columns are read through /Value, people through /Email.

Questions

FAQ

What is a trigger condition?
A rule on the trigger itself. If it is false, the flow never starts, which saves runs, avoids loops and keeps run history clean, unlike a Condition action that only checks after the flow has started.
Why does every condition start with @?
The Trigger conditions box expects a full expression, and the @ marks it as one. Paste each line exactly as shown.
How do I make OR logic?
Separate condition boxes are always combined with AND. For OR, choose "Any is true" and the builder writes a single @or(...) condition for one box.
How do I stop a flow from triggering itself?
When a flow updates the same SharePoint item that triggered it, it can loop. Use the "Ignore edits made by the flow’s account" preset with the email of the account the flow’s connection uses.
My condition never matches. What should I check?
Use internal names (spaces become _x0020_), read choice columns through /Value, and compare numbers without quotes. If text case might differ, tick Aa to ignore case.

↑ ↓ moveEnter open