--- sourceDocument: Brazil Build workflows sourceDocumentLink: https://www.servicenow.com/docs/r/build-workflows Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Build workflows ft:clusterId : - crworkflow bundleId : - crworkflow workflow : - Creator --- # Flow logic # Workflow Studio flow logic {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Workflow Studio flow logic Workflow Studio flow logic enables ServiceNow customers to create conditional and repeated actions within flows and subflows using a graphical interface, minimizing the need for scripting. This functionality helps design flexible and dynamic workflows that can handle complex business scenarios with ease. Show full answer Show less ## Key Features * **Assign Subflow Outputs:** Define data returned from subflows to use in parent flows or other processes. * **Call a Workflow:** Invoke published workflows with specified inputs like the current record. * **Repeat Actions:** Use "Do the following until" to repeatedly execute actions until a specified end condition is met, and "Do the following in parallel" to run actions concurrently in isolated paths. * **Dynamic Flow:** Identify and run flows or subflows dynamically at runtime with templated inputs. * **End Flow:** Stop the current flow execution at any point, useful for exit conditions within branches. * **Loop Controls:** Iterate over lists with "For each," skip iterations with "Skip Iteration," or exit loops early using "Exit Loop." * **Decision Logic:** Apply "If" logic for conditional actions or use "Make a decision" with decision tables for multiple conditional paths, enhancing readability over nested conditions. * **Flow Variables:** Set and append values to flow variables, accessible as data pills for use throughout the flow. * **Error Handling with Try:** Continue flow execution when errors occur and define error response sequences. * **Wait for a Duration:** Pause flow execution to allow user actions or wait for specific date/time events. * **Get Flow Outputs:** Retrieve runtime output values from dynamic flows or subflows to use in subsequent steps. * **Go Back to Flow Logic:** Return to prior flow steps to repeat actions. ## Flow Logic Inputs and Outputs Each flow logic element includes configurable inputs that control its behavior, such as selecting workflows to run or defining conditions for looping and decisions. Outputs expose data generated by flow logic, enabling downstream use, such as the decision result or subflow returned data. ## Practical Benefits for ServiceNow Customers By leveraging these flow logic options, customers can build robust, efficient workflows that automate complex processes with minimal scripting. The graphical interface enhances maintainability and clarity, while features like dynamic flows and decision tables provide flexibility and scalability. Error handling and timing controls help create resilient and user-friendly automation solutions. Enable flows and subflows to specify conditional or repeated actions. Combine the elements of flow logic to create workflows in a graphical interface with little or no scripting. The system provides these flow logic options. {#flow-logic__table_gxs_d3g_p2b__entry__2} | Flow logic option | Description | |-|-| | Assign subflow outputs | 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 | 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 | 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 | Run actions and subflows in separate paths within an isolated flow logic block. | | Dynamic Flow | 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 | 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. | | For each | Apply one or more actions to each record in a list of records. | | Get Flow Outputs | Use this flow logic to access flow contexts and derive the runtime values for dynamic flow outputs. | | If | Selectively apply one or more actions only when a list of conditions is met. | | Make a decision | 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 | 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. | | Try | 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 of time | 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 | [ ] {#flow-logic__table_gxs_d3g_p2b} ## Flow logic inputs {#flow-logic__section_vb1_zjr_xgb} Each flow logic option displays one or more fields that are used to determine its behavior. For example, the Call Workflow flow logic has an input where you are able to select a workflow to run. Use these inputs to define the behavior of the flow and enable optional functionality depending on your needs. See flow logic option documentation for a list of the available inputs and how they control the function of that element. ## Flow logic outputs {#flow-logic__section_nwt_zjr_xgb} Flow logic options may also have outputs. These represent information that is returned by the flow logic. For example, the Make a decision flow logic has an output that contains a decision answer record representing the decision reached by the flow. See the documentation for a flow logic option to see definitions for its outputs. * **[Append to Flow Variables flow logic](https://www.servicenow.com/docs/JlnmAl1y4IYNT_kgYbTTBg)** Append a value to one or more array of objects flow variables. Use flow data to generate values. * **[Assign subflow outputs flow logic](https://www.servicenow.com/docs/qX27EulT5kOBRGKBYxAG8A)** 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](https://www.servicenow.com/docs/NQEIJIgXEakKk3tuRLtZPw)** 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](https://www.servicenow.com/docs/ovrNT5MVtXPVysCc2ZtXzw)** 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](https://www.servicenow.com/docs/fHNODu_WWcW9BSU~UR9nUw)** Run actions and subflows in separate paths within an isolated flow logic block. * **[Dynamic flows flow logic](https://www.servicenow.com/docs/UPiveOIQepWbt3_pM56DDQ)** 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](https://www.servicenow.com/docs/yoHSXT_u6_hZ~2BZ7Vs2sQ)** 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](https://www.servicenow.com/docs/IGMuJBwBeRK~eUyPdIpFIQ)** 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](https://www.servicenow.com/docs/esmLMDyz1JByfBNkIp58zw)** Apply one or more actions to each record in a list of records. * **[Get Flow Outputs flow logic](https://www.servicenow.com/docs/fXxlC3vf5PmIAASLlaHC7w)** Retrieve output values generated by dynamic flows or subflows. * **[Go back to flow logic](https://www.servicenow.com/docs/GrCZOQpQWRJoTNdB39tF2Q)** Return to a prior step in the flow to repeat a sequence of actions. * **[If flow logic](https://www.servicenow.com/docs/DdLyuPtduXTkT6w~M7dtvg)** Selectively apply one or more actions only when a list of conditions is met. * **[Make a decision flow logic](https://www.servicenow.com/docs/8NnG8rZdZCenxcQACsoXIQ)** 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](https://www.servicenow.com/docs/pznT35Am0Xun~TcL09vXNg)** 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](https://www.servicenow.com/docs/fvFzdxlhfu7NJl3i~niFcQ)** 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](https://www.servicenow.com/docs/EfEGiwtJuz7RzLyjvwwBJA)** 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](https://www.servicenow.com/docs/2GOH3wSHrDcPpajWzQTdAg)** 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.