Diese Seite gibt es auch auf Deutsch.
Trigger Condition Builder
Build trigger conditions for Power Automate from a JSON sample, with valid expressions.
A trigger condition must return true for the flow to start, which saves you unnecessary runs (tip 11). The tool reads the fields from the trigger output, quotes values according to the field type, doubles single quotes in values and reads arrays with ?[0]. You also get operators such as is not empty, endsWith, greaterOrEquals and the option to ignore case with toLower(coalesce(..., '')).
Free. You enter your email address once, then all tools are unlocked. Your data is processed locally in your browser.
How it works
- Paste the JSON body from the run history or load a template.
- Build rules and groups with AND or OR.
- Copy the expression and paste it into the trigger settings under Trigger conditions.
Example: only start when status is Approved
@equals(triggerBody()?['status'], 'Approved')
// combine several conditions in one line
@and(equals(triggerBody()?['status'], 'Approved'), greater(triggerBody()?['amount'], 1000))
// ignore case
@contains(toLower(coalesce(triggerBody()?['title'], '')), 'urgent')Frequently asked questions
Is the trigger builder free?
Yes.
Is data uploaded?
No, the expression is built locally.
What is a trigger condition?
An expression in the trigger settings that must return true for the flow to start. It begins with @ and uses functions such as equals or and.
Are several entries AND or OR?
AND. Several lines under Trigger conditions must all be true. For OR, put everything into one @or(...) expression, which is what the tool builds from an OR group.
Why does my flow not start despite the condition?
The expression must start with @ and return exactly true. Field names are case-sensitive and contains() is case-sensitive too.
Where do I enter the condition?
In the trigger settings under Trigger conditions, one condition per line.
Related tips
- #PowerPlatformTip 11: 'Trigger Condition'
- #PowerPlatformTip 145: 'Power Platform Tools'
- #PowerPlatformTip 133: 'SharePoint Updates with Power Automate, No Required Fields Needed'
- #PowerPlatformTip 144: Infinite Approvals beyond 30 days
- Power Automate Flows vs Automate Rules: Performance and Efficiency Comparison by Daniel Christian