Choose the right data for a workflow condition
Distinguish a typed value from a real source output and plan meaningful branch checks.
Part of Prepare an inactive workflow for review
Choose the right data for a workflow condition
A workflow can run correctly and still answer the wrong question if its inputs mean the wrong thing. Decide what the values represent before connecting business data.
Define the input
1. Name the value you need. “Reviewed items” could mean all items, items with a review, or items whose latest review was approved. Choose one definition.
2. Identify the source record and revision. An old count may no longer describe the current work.
3. Specify the type and missing-value behaviour. A blank is not zero, and text “5” is not automatically the same as Number 5.
Inspect the condition
Open your workflow, select its If / Else condition and read the value configuration.
Set a value uses a literal you type. Use an output is for a value produced elsewhere. Before using an output, identify the actual source step and field, its type and whether it supplies the information your rule needs.
A label such as “Read checklist count” does not establish that a source connection exists. If the graph contains only a Manual trigger and a condition with literals, it is not retrieving live checklist data.
Check both branches
For an equality rule with a target of 5:
- Input 5 should return true.
- Input 4 should return false.
- A missing value, wrong type or superseded source needs resolving before you rely on the result.
These are expected results for planning your test, not proof that the workflow has already run.
Your outcome is a clear input definition and a meaningful check for each branch. Do not replace a real value with one that makes the result look successful. If a supported source output is not available, keep the workflow as a literal practice draft rather than implying that live data is connected.
Continue learning
In this series: Design and check workflows — guide 4 of 8.
Turn what you learned into the way the team works.
Mark this lesson complete once the workflow exists in your workspace—not simply when you reach the bottom.