Přejít na obsah

Peak Automations · Conditions

Not every event deserves the same step.
Conditions sort first.

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 Automations

Illustrative example · sample data · nothing runs

EXAMPLE / LIVE PREVIEW

One check.
The fitting step.

Peak Automations / Sample flowLOCAL EXAMPLE

01 / Example value

How does the form score the inquiry? Condition: score greater than 6.

02 / What Peak Automations showsScore 4: the condition does not hold.

Run ends · the history names the condition

Change the example value. The next step follows the check.
Sample data · nothing runs

One example. Two paths.
The check
decides the next step.
Compare both paths below ↓

Two example values

How does the form score the inquiry? Condition: score greater than 6.

Schematic example on a scale from 0 to 10 with an invented score field. In the product you check your trigger's fields.

4/ 10Not met
Run endsEXAMPLE PATH
Score 4: the condition does not hold.
Then

Score 8: Peak creates a task for sales and notifies Jonas.

Run ends · the history names the condition

8/ 10Met
Run continuesEXAMPLE PATH
Score 8: Peak creates a task for sales and notifies Jonas.

Run continues · both steps in the history

Trust needs clarity

Where conditions stop today.

01 / The existing evidence

No else branch

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.

Peak Automations / Example pathsEXAMPLE
  1. 4/10
    Score 4: the condition does not hold.Run ends · the history names the condition
  2. 8/10
    Score 8: Peak creates a task for sales and notifies Jonas.Run continues · both steps in the history

02 / Your check

All together only

Several conditions in one place are joined with “and”. An “or” across different fields is not possible today.

4 / 1010 / 10

Compare both paths and their reasons.

03 / The clear limit

No run from here

The paths on this page are illustrative. They check no real data and save nothing.

ExampleNothing run

The next step

Let only the right cases through.

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 Automations
Peak Automations · ConditionsWhat is checked?

Illustrative example · sample data · nothing runs

Frequently asked questions

Is there an else branch?

Not yet. If a condition does not hold, the run ends. An else branch is planned.

How many conditions are possible?

Up to ten in one place. They are joined with “and”.

Can I see why a run stopped?

Yes. The history names the condition that was not met.