Score 8: Peak creates a task for sales and notifies Jonas.
Run ends · the history names the condition
Peak Automations · Conditions
A condition checks a value from the trigger or an earlier step: is, is not, is one of, contains, greater than, less than, is set. Only when all conditions hold does the run continue. Otherwise it ends, and the history tells you why.
Set a condition in Peak AutomationsIllustrative example · sample data · nothing runs
01 / Example value
How does the form score the inquiry? Condition: score greater than 6.
Run ends · the history names the condition
Change the example value. The next step follows the check.
Sample data · nothing runs
Two example values
Schematic example on a scale from 0 to 10 with an invented score field. In the product you check your trigger's fields.
Score 8: Peak creates a task for sales and notifies Jonas.
Run ends · the history names the condition
Run continues · both steps in the history
Trust needs clarity
01 / The existing evidence
If a condition does not hold, the run ends. A second path for “otherwise” inside the same automation does not exist yet; it is planned. Until then you build a second automation with the opposite condition.
02 / Your check
Several conditions in one place are joined with “and”. An “or” across different fields is not possible today.
Compare both paths and their reasons.
03 / The clear limit
The paths on this page are illustrative. They check no real data and save nothing.
The next step
Describe your routine with a condition, for example “only if the budget is set”, and test it in your workspace.
Set a condition in Peak AutomationsIllustrative example · sample data · nothing runs
Not yet. If a condition does not hold, the run ends. An else branch is planned.
Up to ten in one place. They are joined with “and”.
Yes. The history names the condition that was not met.