A decision branch in Zoho Flow is inserted as a step in the flow canvas. You define one or more conditions using field values from previous steps, such as whether a deal amount is above a threshold, whether a field is empty, or whether a status matches a specific value. Each condition branch defines the actions to execute when that condition is true. A default branch handles executions where no defined condition is met. Multiple branches can be added to a single decision step to handle several distinct cases.
Use a decision branch whenever the correct action depends on a data value in the triggering record. Common examples: route a support ticket to different teams based on issue category, send different email notifications based on deal size, or skip a data sync step if a required field is empty. Avoid stacking many nested decision branches in a single flow; if the logic becomes complex, splitting the flow into multiple focused flows or using a subflow improves readability and maintenance.
Always define a default branch to handle unexpected data values; without it, executions that match no condition will stop silently, making it hard to diagnose why some records were not processed. Test each branch independently by constructing test records that satisfy each condition. Condition comparisons are often case-sensitive, so verify that field value formatting in your source app matches the values you enter in the branch criteria exactly. Numeric comparisons require that the field is mapped as a number type, not a string.
In Zoho Flow, both a condition and a decision branch evaluate criteria to control flow execution. The decision branch is specifically designed to split execution into multiple named paths, each with its own set of actions, before the flow continues. A condition step typically filters whether execution proceeds at all. Use a decision branch when you need the flow to do different things depending on the data, not just stop or continue.
Yes. A decision branch in Zoho Flow supports multiple condition paths plus a default branch. You can add as many conditions as needed to handle different data values, and each path can have its own sequence of action steps. However, adding more than four or five branches to a single decision step can make the flow harder to read and maintain; consider whether some branches could be handled in a separate flow.
Aaxonix is a certified Zoho implementation partner based in Pune. Architecture-first, no surprises.