Flows

term definition characteristics flow a single execution path within a playbook or component that has one trigger that initiates subsequent automation each flow can only have one trigger there can be multiple flows in one playbook no cross talk between flows | the following image is a playbook canvas with three separate triggers each has its own flow(s) notice the flows do not communicate with one another they are individual execution paths how does information flow? the playbook trigger receives data inputs from either an external system/service or an application record, then applies that data according to the actions needed for the required outcome in a single execution flow the data outputs are then written to an external system/service or a new/existing application record a playbook canvas has a top down flow visualization the flows of information are referred to as upstream and downstream flow connectors the flow between actions goes from the preceding action to the subsequent action there are three types of flow connectors that signal execution type from one action to the next on success on failure on complete visual indicators are displayed after you select a flow connector green flows are "on success" flows, indicating that upon the success of the preceding action, the next action in that flow executes red flows are "on failure" flows, indicating that upon the failure of the preceding action, the next action in that flow executes