Playbooks Overview

playbooks are a series of triggers, logic, and actions that automate a workflow a playbook can contain triggers, actions, native actions, components, assets, inputs, and outputs playbook architecture a playbook can have one or more flows each flow has exactly one trigger flows do not communicate with each other for details, see \[ flows ]\( /03 using actions/03 flows/02 02 69 flows md) playbook data model on the canvas, turbine stores playbook information in two layers understanding both layers explains what save updates and why some changes appear only after you save from the canvas editor layer what you see in the ui what is stored what runs playbook (container) playbook name, description, canvas layout, flow order, annotations a builder playbook record that lists which flows belong to this playbook does not run by itself; groups flows flow one trigger and its actions on the canvas a playbook (flow) document automation definition plus yaml source ( meta src ) this is what executes when the flow is triggered how the two layers relate one playbook (container) can reference one or more flows each flow is a separate automation document linked from the container when you add a new flow on the canvas, the product creates a new flow document and adds its id to the container what happens when you save saving from the canvas editor can update both layers flow changes (triggers, actions, conditions, connections) the editor updates the in memory flow definition, merges it into the flow yaml source , and sends updates to the turbine playbook api for each dirty flow container changes (playbook name, description, flow order, annotations) the editor saves the builder playbook record separately, including the ordered list of flow ids if you change only flow logic and the container name does not change, you are still saving flow documents if you rename the playbook or reorder flows, the container save runs as well standalone playbooks from the playbooks home page when you create a playbook from orchestration > playbooks and open the classic playbook editor, you usually work with a single flow stored as one playbook document that path does not use a separate builder playbook container in the same way as a multi flow canvas playbook for creating playbooks, see how to create a playbook /01 how%20to%20create%20a%20playbook md (manual) or create and modify playbooks with hero ai https //app archbee com/docs/wdlpsa7glls1ghfgxbo9d/tmmnjglc0e9lipo37kzpb (text to playbook) playbooks home page from orchestration > playbooks , you can search for playbooks by keyword filter by source, interface, or creator sort by last modified, last created, or alphabetical order enable/disable playbooks open playbook operations (export, duplicate, delete) playbook canvas basics the canvas is where you build playbooks using drag and drop actions, triggers, and reusable components it supports ai assistance, flow controls, and testing from the same workspace canvas layout add panel (left) browse and add triggers, actions, and components canvas (center) arrange actions and connect flows details panel (right) configure the selected trigger or action add panel use the add panel to search and drag items into the canvas triggers /02 configuring%20playbooks/01 triggers/02 02 104 record%20event%20triggers mdnative actions /03 using%20actions/01 native%20actions/01 native%20actions mdrecord actions /03 using%20actions/01 native%20actions/record%20actions/02 02 40 03 103 record%20use%20cases mdcomponents / /02 building%20blocks/02 components/01 components md flow connectors and direction flows use connectors to control execution between actions on success on failure on complete green connectors indicate success paths, while red connectors indicate failure paths the canvas uses a top down layout, so flows move from upstream (near the trigger) to downstream (later actions) for details, see \[ flows ]\( /03 using actions/03 flows/02 02 69 flows md) playbook details panel the right hand panel shows playbook details such as the name and description close the panel (x) to free up more canvas space test console use the test console to run end to end tests of your playbook flows for details, see test console /04 testing%20and%20debugging/02 02 75 test%20console md