Flows and Conditions

action flows allow you to control the sequence and execution of actions within a playbook they specify what should happen after each action based on whether it was successful, failed, or simply completed these flows are essential for building dynamic, conditional logic within swimlane playbooks types of action flows turbine supports the following action flows on success executes the next action if the preceding action completes successfully on failure executes the next action if the preceding action fails on complete executes the next action once the preceding action completes, regardless of its success or failure the action flow icon has three types that determine whether the next action should occur on the success, failure, or general completion of the preceding action every action has an action flow icon the table below details icon information for different types of flows position in icon color action flow types / tool tip top (on success) green on success middle (on failure) red on failure bottom (on complete) grey on complete add action flows add an action to the playbook configure the action see inputs docid dy2dffdex99ri 0sunoz for more information hover over the action to display the action flow icon click the on success , on failure , or on complete action flow type as required important! an action can have multiple action flows the example below shows an action with both on success and on failure flows multiple action flows once you have created an action flow, it's time to configure it playbook condition builder now that you have an action flow set up, use the playbook condition builder to define when and how each action should execute based on specific conditions the table below explains the icons and meanings of the action flow controls action flow control icons action flow icons meaning on success executes the next action if the preceding action is successful on failure executes the next action if the preceding action fails on complete executes the next action after the preceding action completes, regardless of the outcome delete condition removes the selected condition configure condition opens the configuration panel to edit the condition add condition adds a new condition to the action flow remove condition deletes the condition from the action flow configure conditional expressions conditional expressions allow you to create dynamic flows within playbooks by setting up conditions that control which actions execute based on specific criteria here’s what you can do create and configure conditions between playbook actions using comparison operators build conditions with minimal code use conditions to execute actions that adapt based on incoming data criteria comparison operators comparison operators are used to compare values in conditional expressions the table below lists the operators and available options comparison operators options null comparison operators is defined / is not defined boolean comparison operators is true / is false string comparison operators matches / matches (case insensitive) / does not match / does not match (case insensitive) string array operators contains / contains (case insensitive) / does not contain / does not contain (case insensitive) numeric comparison operators is greater than / is greater than or equal to / is less than / is less than or equal to / is equal to / is not equal to numeric array operators contains / does not contain read only condition panel in a playbook, you can view the configured conditional logic to understand how actions will execute clicking on a condition line displays the flow condition line in the flow view, you can see the workflow of conditions click edit condition to modify the expression as needed