If flow logic
- UpdatedJul 31, 2025
- 4 minutes to read
- Zurich
- Create Workflows
Selectively apply one or more actions only when a list of conditions is met.
Nested If flow logic blocks
You can add a child If flow logic block to a parent If flow logic block. Add the child If flow logic block to the Then branch of the parent flow logic block.
Inputs
| Input | Description |
|---|---|
| Condition label | Descriptive label for the conditions of branch. A label can be easier to read than a long or complex condition data pill value. |
| Condition | Conditions under which the branch runs. The flow only runs the contents of the Then branch when the conditions evaluate to true. |
Outputs
This flow logic has no outputs.
Example: Perform an action on if an incident has a high urgency
In this example, the action is triggered when the incident record has a high urgency value.
Execution details
- The header shows the state, start time, and runtime for the flow logic.
- The Configuration Details section shows the details about the variables that are used by the flow, including the type, configuration, and runtime values for each variable. Use the condition variable to see if the branch conditions were met.
General guidelines
Use these general guidelines to create effective If flow logic blocks.
- Avoid referring to data pill values outside of the Then branch
- When you set a data pill value from inside a Then branch of If flow logic, the data pill value is only available to other actions in the same branch. Referencing a data pill value that was set inside a Then branch from outside of the flow logic branch produces a null value.
- Group matching condition types in their own condition sets
- Mixing conditions of different types for the same field values can produce unexpected results. For example, adding an AND condition to a group of multiple OR conditions for an incident short description can produce a
situation where the If condition never evaluates to true. Use condition groups to group similar condition types for the same field. For example, group all OR conditions for an incident short description in one condition
set and group all AND conditions for an incident short description in another condition set.
Figure 2. Example of grouping matching conditions into condition sets 
- Replace multiple If flow logic blocks with a Make a decision flow logic block
- Rather than create duplicate If flow logic blocks that only vary by their conditions, use a decision table to generate an answer. For example, suppose you want to use the incident category to set the assignment group of
an incident task record. Rather than create a duplicate If flow logic block for each category value, use the Make a decision flow logic to provide an answer for the assignment group.
Here is an example flow that uses three If flow logic blocks that each create an incident task record. The only difference between the If flow logic blocks are the conditions of the incident category.
Figure 3. Example of multiple If flow logic blocks that do the same action 
Here is an example flow that uses a single Make a decision flow logic block to determine the incident task assignment group from the incident category. The Create task action uses the output of the decision as an input.
Figure 4. Example of replacing multiple If flow logic blocks with a decision 
Here is an example decision table that uses incident record values as an input. The Conditions column consists of two incident category values. The results column consists of the assignment group to use for each condition value.
Figure 5. Example decision table Get Assignment Group from Category 
Related Content
- Append to Flow Variables flow logic
Append a value to one or more array of objects flow variables. Use flow data to generate values.
- Assign subflow outputs flow logic
Specify the data the subflow returns when it completes running. Use subflow output as data for a parent flow or as input for another process.
- Call a workflow flow logic
Run a published and active workflow from your flow. You can use the flow data as a workflow input. For example, you can specify the current record as a workflow input.
- Do the following until flow logic
Apply one or more actions repeatedly until an end condition is met. You can use the flow data to specify the end conditions.
- Do the following in parallel flow logic
Run actions and subflows in separate paths within an isolated flow logic block.
- Dynamic flows flow logic
Identify and run a flow or subflow dynamically by using runtime data. Build templates to provide expected inputs for dynamically called flows or subflows.
- End Flow flow logic
Stop running the current flow. Use End Flow within a branch of the flow to specify an exit condition. For example, end the flow when it reaches a specific If flow logic block.
- Exit Loop flow logic
Exit from a flow logic loop when the conditions of an If flow logic are met. Continue running the flow from the next step after the flow logic loop. This flow logic is also known as break.
- For Each flow logic
Apply one or more actions to each record in a list of records.
- Get Flow Outputs flow logic
Retrieve output values generated by dynamic flows or subflows.
- Go back to flow logic
Return to a prior step in the flow to repeat a sequence of actions.
- Make a decision flow logic
You can use the decision table branching logic in situations where multiple conditional paths are required, as an alternative to nested If, Else If, or Else flow logic. For example, if you want to determine what kind of car insurance you need, you can add inputs such as your age, accident history, and car model to the decision table to determine a level of insurance coverage. This logic can save you time and present a more readable format than nested if conditions or switch case statements.
- Set Flow Variables flow logic
Assign a value to one or more flow variables, which store flow data as data pills. Access flow variable values by referring to their data pill.
- Skip Iteration flow logic
Skip the current iteration of a flow logic loop when the conditions of an If flow logic are met. Continue running the flow logic loop with the next item in the list. This flow logic is also known as continue.
- Try flow logic
Allow a flow to continue running when an error occurs within a flow logic block. Run a sequence of actions in response to errors within the flow logic block.
- Wait for a duration flow logic
Use this flow logic to give your users time to act during automated processes or to wait for a specific date and time to complete actions.