Using Expressions in Nodes
An expression is a small formula that produces a value when a workflow runs. Use one whenever a setting should be worked out from the data in a run rather than typed in ahead of time: a premium with tax added, a condition that checks a score, a label chosen from a status. Under the hood these are written in CEL, the expression language, but you rarely need to think about the name; on this page we just call them expressions.
Expressions show up in many places: the conditions on a Check or Conditional node, the formula on a Map node, inside a string template, and in any node setting that accepts one.
Referencing values
An expression reads values that earlier steps produced by naming the group, the step, and the value:
You usually pick these from the builder’s value picker rather than typing them. See Variables & Data Flow for the full picture of where values come from.
What you can write
Expressions cover the everyday building blocks of logic and math.
The ? : form reads as “if this, then the first value, otherwise the second.” It
is the most common way to pick a value based on a condition.
A worked example
Chen Insurance Group scores each inbound quote request in an earlier step. A Check node then turns that score into a decision using two expressions, tried in order:
If the applicant’s score is 80 or higher and their documents are complete, the first condition wins and the request is approved. Otherwise, if the score is at least 50, the second wins and it goes to review. If neither is true, the node’s default outcome applies. This is how a run reacts to real data instead of fixed values.
Text inside quotes is compared exactly, including uppercase and lowercase, so
"Active" and "active" are not the same. Match the exact value the earlier
step produces.
Expressions can also call functions, like counting a list or formatting a phone number. See the Function Reference for what is available.