Conditional & Threshold Routing
Make a step earn its place in the chain — add conditions like "Budget greater than 1000" and the step only runs for the requests that need it; everything else skips straight past.
Updated
Conditional and threshold routing lets an Administrator gate a step in the visual flow builder so it only runs for requests that meet the conditions you set. Each condition compares a form field against a value using an operator — equals, less than, less than or equal, greater than, greater than or equal, or contains — so both numeric thresholds and text matches work. Conditions combine with AND logic: if any one is unmet, the step is skipped and the request follows a different approval path. It's available on all tiers.
Who this is for: admin.
Add a condition so the step only runs past a threshold
When only larger spend needs an extra sign-off, a threshold condition keeps the step out of the way of everything else. You'll need a workflow open in the builder with a step to configure.
-
Sign in as an Administrator.
-
Click Configure step on the step you want to gate.

Step 2 -
Click Conditions.

Step 3 -
Click Add Condition.

Step 4 -
Choose the form field the condition should test from Field — the example uses Budget.

Step 5 -
Choose the comparison from Operator — the example uses Greater than.

Step 6 -
Enter the threshold the field is compared against in Value — the example uses
1000.
Step 7 -
Click Add Condition to save the condition.

Step 8
The condition is listed on the step as Budget Greater than 1000.
Add a text-match condition alongside it
A second condition narrows the step further — for example, a spend threshold that only applies to a particular kind of request. Conditions combine with AND logic, so the step runs only when every condition is met.
-
Click Add Condition.

Step 1 -
Choose the form field for the text match from Field — the example uses Event.

Step 2 -
Choose Contains from Operator to match on part of the field's text.

Step 3 -
Enter the text to look for in Value — the example uses
Gala.
Step 4 -
Click Add Condition to save the second condition.

Step 5
The second condition is listed on the step as Event Contains Gala.
Edit a condition's value
When a threshold changes — a new spending limit, a different cutoff — you can adjust an existing condition instead of rebuilding it.
-
Click Edit condition on the condition you want to change.

Step 1 -
Enter the new comparison value in Value — the example uses
500.
Step 2 -
Click Save Changes.

Step 3
The updated condition reads Budget Greater than 500.
Remove a condition
Removing a condition loosens the gate: with fewer conditions to satisfy, the step runs for more requests. Delete the ones that no longer describe when the step should apply.
-
Click Delete condition on the condition you no longer need.

Step 1
The deleted condition is gone from the step, leaving the remaining condition — Budget Greater than 500 in the example screenshots.