Create and Modify Playbooks with Hero AI

use playbook building mode (also called text to playbook ) to create or change playbook flows on the canvas with natural language the playbook generator agent applies your prompts to the selected flow or flows starting in turbine 26 2 0 , playbook builder v2 added clarifying questions before building and progress detail messages while generation runs starting in turbine 26 3 0 , the agent can edit multiple flows in one request —select flows on the canvas or name them in natural language, then review and accept all or reject all proposed changes see edit multiple flows in one request /#edit multiple flows in one request you can still edit a single flow by selecting it on the canvas or naming it in your prompt for manual drag and drop creation, see how to create a playbook docid 0 kvg5p4lthw75itmpuwp for supported operations, limits, and trigger rules, see playbook generator agent reference docid 3jkvn5yplm u06tfjhiac choose your path i want to… start here create the first flow in a new playbook with ai create a new flow with hero ai /#create a new flow with hero ai change an existing flow on the canvas modify an existing flow /#modify an existing flow edit several flows in one hero ai prompt edit multiple flows in one request /#edit multiple flows in one request accept or reject ai changes across flows review and accept hero ai changes /#review and accept hero ai changes understand what a flow does without editing it ask questions about existing flows /#ask questions about existing flows answer agent questions before a build completes clarifying questions /#clarifying questions (playbook or component canvas) see status messages during generation progress during playbook generation /#progress during playbook generation see what the agent supports (including multi flow) playbook generator agent reference docid 3jkvn5yplm u06tfjhiac confirm i am in the right hero ai mode enter playbook building mode /#enter playbook building mode understand container vs flow when saving playbooks overview docid\ dp agnnne2mjjfgtv2lz5 enter playbook building mode there is no separate building mode toggle in settings the companion enters playbook building mode when hero ai opens with canvas context (the product knows which playbook and flow you are editing) how you open hero ai mode typical use hero ai from the main application toolbar (outside the canvas editor) general companion questions and chat not tied to a specific canvas flow; see hero ai companion docid\ crqkfvngpcz wj8xthds7 build with hero ai on the canvas toolbar playbook building mode generate or change flows with the playbook generator agent start building with hero ai on an empty canvas playbook building mode create the first flow in a new playbook hero ai companion while a playbook canvas is already open playbook building mode modify or explain the selected flow navigate away from the playbook canvas editor (panel can stay open) general companion building mode ends; see hero ai companion docid\ crqkfvngpcz wj8xthds7 steps to enter playbook building mode open a playbook in the canvas editor (see how to create a playbook docid 0 kvg5p4lthw75itmpuwp to create one manually first, if needed) do one of the following click build with hero ai on the canvas toolbar, or on an empty canvas, click start building with hero ai , or open the hero ai companion from the playbook canvas confirm that the companion shows playbook building mode (see below) before you send a build or modify prompt what you should see in playbook building mode when building mode is active, the hero ai companion typically shows a banner such as entered playbook building mode or playbook building mode near the top of the panel if you open hero ai only from the main toolbar and do not see building mode, you are in the general companion open the playbook canvas and use build with hero ai or start building with hero ai instead to stop generation while a playbook is being built, click cancel on the canvas progress overlay or in the companion when shown for enable, disable, delete, and trigger rules, see playbook generator agent reference docid 3jkvn5yplm u06tfjhiac edit multiple flows in one request starting in turbine 26 3 0 , playbook builder v3 can apply coordinated edits across more than one flow in a single hero ai session how to target multiple flows open a multi flow playbook in the canvas editor and enter playbook building mode do one or both of the following canvas select a flow on the canvas unless you name other flows in the prompt, the agent scopes edits to that selection natural language name flows by their titles (for example "in enrich alerts and notify soc , add a virustotal check after the first action ") prefer titles over canvas position words such as "the first flow" or "the leftmost flow"—the agent asks for a title instead of guessing position send the prompt answer any clarifying questions if the agent asks which flows or actions you mean when generation finishes, review the in chat flow summary (changes grouped by flow with added / removed / modified lines) and the canvas summary footer — see review and accept hero ai changes /#review and accept hero ai changes accept all or reject all , or accept/reject per flow, then save the playbook example multi flow prompts "add the same slack notification step to triage and escalate " "disable legacy ingest and add a schedule every 15 minutes to notify soc " "create a new flow called archive closed that runs daily at 02 00 utc and archives closed cases " "enable all flows " / "disable all flows " (agent updates each flow’s enabled state) what multi flow editing does not change you still save the playbook after accepting changes so container and flow layers persist record event and playbook button triggers remain limited (filter existing only) — see playbook generator agent reference docid 3jkvn5yplm u06tfjhiac the agent cannot connect an action in one flow to an action in another flow (cross flow edges are not supported) content locking and concurrent tab rules still apply if the same playbook is open in more than one browser tab or window, saves can overwrite each other see content locking and concurrent sessions https //docs swimlane com/playbook generator agent reference#content locking and concurrent sessions in playbook generator agent reference review and accept hero ai changes when hero ai proposes canvas changes across one or more flows, turbine shows two related summaries canvas summary (footer) a footer panel appears with a title such as hero ai made changes to 2 flows (or added / removed flow phrasing) for each affected flow it lists added , removed , and modified items you can action what it does accept all keeps all pending hero ai changes across the listed flows reject all discards all pending hero ai changes (confirm when prompted) per flow accept / reject accept or reject changes for one flow (tooltips accept changes to flow / reject changes to flow ) click a change label focuses that action or flow on the canvas (removed items are not focusable) use the status labels to decide what to review status when it appears added a new action or flow that hero ai created for this prompt removed an action or flow that hero ai removed for this prompt modified a meaningful change to that action, such as configuration updates or a change to the outgoing edge type (for example, on success to on failure ) when hero ai only adds or removes an action, the parent action is not listed as modified solely because its outgoing connection was rewired to the new or next action (same edge type) for example, a prompt such as "add a logging note component at the end of every flow" should mainly show added items, not a long list of unchanged parents marked modified review modified items when the summary shows a real config or edge type change on that action in chat flow summary the companion message for that turn can include a collapsible summary by flow with the same added / removed / modified structure use it to understand what changed for that prompt; bulk accept/reject remains on the canvas summary accepting changes updates the canvas draft save the playbook to persist if you reject changes and prompt again for the same flow, the agent rebuilds from the current accepted state create a new flow with hero ai open a playbook in the canvas editor and enter playbook building mode on an empty canvas, click start building with hero ai describe what you want to build (for example "create a playbook that fetches alerts from crowdstrike every 5 minutes, extracts observables, and enriches them with virustotal ") each new flow must include at least one trigger or action (empty flows are not supported) answer any clarifying questions if the agent asks — see clarifying questions /#clarifying questions review progress detail messages and the generated flow — see progress during playbook generation /#progress during playbook generation when the canvas summary appears, also review the canvas and in chat summaries /#review and accept hero ai changes iterate with follow up prompts save the playbook when you are satisfied so both the flow and container layers persist modify an existing flow enter playbook building mode on the playbook canvas select the flow you want to change on the canvas, name it in the prompt, or @ mention the flow in chat ask hero ai to update it (for example "add an ip reputation check after the enrichment step and branch if malicious ") answer clarifying questions if prompted review progress messages and the updated flow use review and accept hero ai changes /#review and accept hero ai changes when the canvas summary appears save the playbook ask questions about existing flows the playbook generator agent is not limited to creating or modifying flows you can also use it to understand what an existing flow does open the hero ai companion from a playbook canvas in building mode and ask questions such as "what does this flow do?" "explain the steps in this playbook " "why would this flow branch at the condition step?" hero ai analyzes the selected flow and provides a plain language explanation, which helps onboard new team members, audit automation logic, or troubleshoot unexpected behavior clarifying questions starting in turbine 26 2 0 , both playbook building mode and component building mode may pause and ask clarifying questions when your prompt needs more detail before it can build or change a flow or component safely when they appear after you submit a build or modify prompt in playbook building mode or component building mode when the agent needs choices such as trigger type, target system, error handling, or branch behavior what you see the hero ai panel shows a brief message that it needs more detail before it can continue building an optional intro message from the agent explains why it paused one question at a time with question x of y progress an instruction line select one option below (single select) or select one or more options below (multi select) selectable options options with descriptions show an info icon; hover for the full description back , next , and save buttons to move through questions and submit answers how to respond step action 1 read the question and select one or more options 2 click next to continue, or save on the last question 3 use back to change a prior answer 4 if other is available, select it and enter custom text in the main chat input field (required before next or save ) after you click save , your answers are submitted to the agent and generation continues a summary of your clarifying answers may appear in the chat history you cannot send a new build prompt while clarifying questions are active complete or navigate away from the question flow before starting a different request while clarifying questions are open, the canvas progress overlay may show waiting for user response with an alert icon instead of the generation sparkle answer clarifying questions with the integration and trigger you actually use in production vague answers produce generic flows that need more manual edits progress during playbook generation starting in turbine 26 2 0 , text to playbook shows progress detail status messages on the canvas and in the hero ai companion while the playbook generator agent works where messages appear location what you see canvas progress overlay up to three rolling status lines with animated dots on the current line and a cancel button while the agent runs hero ai companion chat a live progress stack under the assistant message for the current run what messages mean message pattern (examples) what the agent is doing processing prompt the agent accepted your prompt and is starting the run reading playbook or trigger schemas loading current flow structure and trigger configuration reading native action schemas or component discovering available actions and connectors building playbook or updating flow steps adding or changing actions on the canvas thinking a detailed in progress update is underway (canvas overlay only when the underlying hub message exceeds roughly 75 characters) waiting for user response the agent is waiting for clarifying question answers in the companion a short custom sentence the agent supplied a specific description for the current tool step messages update in real time wording may vary between runs long hub messages may display as thinking on the canvas overlay while the full detail remains in the companion progress stack while generation is running canvas editing and some companion actions are limited until the agent finishes, you cancel, or clarifying questions appear click cancel on the canvas overlay to stop the current generation attempt do not navigate away from the playbook editor if you need to monitor completion after generation completes review the flow on the canvas before saving use the companion to ask follow up modify prompts or clarifying questions on the next iteration prompt tips be explicit about triggers, actions, and data sources use step placement language (for example, "after \[step name]" or "before \[step name]") ask for error handling when external integrations are involved see also hero ai docid\ swz8uetvmvoojwgm xnk — overview of all hero ai features and building modes playbook generator agent reference docid 3jkvn5yplm u06tfjhiac — supported scenarios, multi flow matrix, limits, and validation notes organizing playbook in the canvas https //docs swimlane com/organizing playbook in the canvas — canvas tools (multi select, group, cut, copy, paste, and zoom) playbooks overview docid\ dp agnnne2mjjfgtv2lz5 — canvas layout, flows, and data model hero ai companion docid\ crqkfvngpcz wj8xthds7 — general companion (records, reports, tenant questions) test console docid 1d0fiftjsdox88pvpk5fs — validate flows after ai changes