Playbook Generator Agent Reference

the playbook generator agent runs in playbook building mode on playbook and component editor pages starting in turbine 26 2 0 , playbook builder v2 adds clarifying questions and expanded supported scenarios for building on the canvas when a playbook contains multiple flows, the agent works on one flow at a time —select the flow on the canvas or name it in your prompt multi flow editing in a single session is planned for a future release for procedures, see create and modify playbooks with hero ai docid\ tmmnjglc0e9lipo37kzpb for clarifying questions and progress detail during generation, see the same topic quick reference — operation matrix entity create modify delete enable disable reorder move (cross flow) playbook metadata (name, description) — yes — — — — — flow (with at least one trigger or action) yes yes yes yes yes — no schedule (cron) trigger yes yes yes — — — — flow event trigger yes yes yes — — — — webhook trigger yes yes yes — — — — record event trigger no filter only on existing no no no — — playbook button trigger no filter only on existing no no no — — trigger schema (webhook or flow event) yes yes with trigger — — — — action yes yes yes yes yes yes no connection (on success, on failure, on complete) — yes yes — — — no component (building mode) — yes — — — — — playbook metadata the agent can read and update playbook name and description it can also read created by , modified by , and timestamp metadata when you ask who created or last changed the playbook operation supported read playbook name, description, authorship, timestamps yes update playbook name or description yes enable or disable the entire playbook at product level no — use flow enable or disable instead save, duplicate, copy, export, or package the playbook no — use the ui example prompts who created this playbook? · when was this playbook last modified? · update the playbook description to … flows in turbine 26 2 0 , the agent creates or modifies one flow at a time select the target flow on the canvas, or name it in your prompt applying the same change across multiple flows in one session is planned for a future release multiple flows appear as separate graphs on the same canvas the agent resolves which flow you mean from your wording or the selected flow on the canvas scenario supported notes create a new flow with at least one trigger or action yes empty flows are not supported create multiple new flows in one request no one new flow per build request in 26 2 0 edit one existing flow yes default when you name a flow or have one selected edit multiple flows (same change) no planned for a future release delete a flow by name, position, or content yes removes the flow graph enable or disable a flow by name or selection yes sets flow enabled state enable or disable all flows no one flow at a time in 26 2 0 rename a flow to a unique title yes rename a flow to a title already used by another flow no agent refuses or asks for an alternative copy or move a flow to another playbook no explain what a flow does yes read only; no file changes flow disable vs action disable disabling a flow pauses the entire graph disabling an action skips only that step while the rest of the flow can still run triggers five trigger types exist the agent can create , modify , and delete schedule, flow event, and webhook triggers record event and playbook button triggers can only be filtered on flows where they already exist—the agent cannot create, replace, or delete those trigger types trigger create modify metadata modify filter ( if ) delete enable / disable trigger cron / schedule yes yes — yes — flow event yes yes yes yes yes webhook yes yes yes yes yes record event no no yes (existing only) no no playbook button no no yes (existing only) no no schedule trigger scenario supported create a flow with a schedule (for example, every 7 minutes or daily at 6 am) yes change the cron expression on an existing schedule yes replace a schedule with a webhook or flow event trigger yes add a schedule to a flow that had another trigger type yes example prompts ingest data every 7 minutes · create a flow that runs daily at 6 am and searches for records with status new flow event trigger scenario supported create a new flow with a new flow event trigger yes create a flow reusing an existing flow event definition from another playbook no create a flow with a trigger similar to an existing flow event yes rename flow event trigger id or name yes add or modify trigger filter conditions ( if ) yes map actions to $event data from the trigger schema yes delete a flow event trigger yes replace a flow event trigger with cron or webhook yes webhook trigger scenario supported create a new flow with a webhook trigger yes create a webhook flow similar to an existing webhook flow yes rename a webhook trigger yes add or modify webhook filter conditions ( if ) yes map automation to $event data body fields yes replace webhook with schedule or flow event yes delete webhook trigger only (keep rest of flow) yes configure webhook authentication (shared secret, format, value) no generate webhook url no — use the ui record event and playbook button triggers scenario supported create a new record event or playbook button trigger no replace an existing trigger with record event or playbook button no modify filter conditions on an existing record or button trigger yes replace record event or playbook button with cron, webhook, or flow event yes trigger conditions (all conditional triggers) the agent can build and modify filter conditions including numeric comparisons (for example, $gte , $lte ) string and regex match ( $match ) logical and / or across fields record field change detection ( previous vs record ) array and nested field conditions trigger schemas webhook and flow event triggers use a trigger schema that documents $event data field shapes schedule triggers do not use a per flow trigger schema scenario supported read trigger schema before mapping $event data yes create or update trigger schema when adding webhook or flow event fields yes create or replace schema for record or playbook button triggers no example prompts map $event data alert name to case name on webhook ingest · create a webhook flow with transformation of webhook body fields actions action lifecycle scenario supported notes add a new action (add, insert, another, new, one more) yes creates a new node; does not change existing actions modify an existing named action yes only the targeted action delete an action by name, description, or selection yes rewires connections enable or disable an action yes uses action disabled state rename an action key and title in the flow yes updates references in connections edit action inputs (limits, filters, mappings) yes edit a python script body (specific lines) yes insert an action between two connected actions yes rewires on success paths reorder two actions in the execution chain yes updates entrypoints and connections move or copy an action to another flow no group actions into a sub component no ui only mark an action input as sensitive no ui only configure connector retry, delay, or limit no add vs modify your wording agent behavior add, insert, another, additional, new, one more add a new action; do not edit existing change, update, edit, set … on \[named action] modify only that action ambiguous and the same action type already exists agent asks a clarifying question before editing all flows, every instance, both flows not in 26 2 0 — edit one flow at a time native actions the agent can add, configure, and delete these native action types condition, loop, parallel create or update variable search records, create record, delete records scripts, transformations, http hero ai native action these native actions are not fully supported through prompts (configure them in the ui if needed) export records emit event swimlane intelligence send notification csv get rows components and connectors components (preferred) add, configure, and remove tenant components as sub actions in a playbook flow connector actions add, configure, and remove connector actions; add or change the asset used by a connector action prefer components unless you request a connector directly or no component exists for the task component building mode (component editor) modify user defined input and output schemas publish fields to properties in the output schema cannot add or modify existing interfaces (intents) connections each action has at most one incoming connection and either ( one on success + one on failure ) or ( one on complete ) scenario supported change connection type (on success, on failure, on complete) yes connect an action in one flow to an action in another flow no multiple outgoing on success from one action no multiple incoming connections to one action no mix on success or on failure with on complete on the same action no query and explain (read only) scenario supported what does this playbook or flow do? yes which flows use hero ai, search records, or a specific application? yes who created or modified the playbook? yes explain action logic in plain language yes read live application records (outside automation context) no read playbook run history or logs no test or run the playbook or individual actions no clarification and ambiguity starting in turbine 26 2 0 , the agent uses clarifying questions when your prompt is ambiguous—for example, when multiple applications, components, or fields match, when add vs modify is unclear, or when the target flow is unspecified in a multi flow playbook see create and modify playbooks with hero ai docid\ tmmnjglc0e9lipo37kzpb in create and modify playbooks with hero ai scenario behavior multiple resources match your intent agent asks before implementing add vs modify not clear agent asks target flow ambiguous agent asks or uses selected flow you explicitly said add agent adds; does not ask add vs modify bulk change ( all flows , every instance ) not in 26 2 0 — one flow at a time content locking and concurrent sessions locked by another user when a playbook is locked for editing by another user, hero ai can still describe and query the playbook but cannot apply changes if a lock occurs while generation is running, the ui may show suggested changes with reject or copy changes only—no accept refresh the page after the lock is released to resume editing same playbook in multiple tabs or windows turbine does not prevent the same user from opening the same playbook in multiple browser tabs or windows each session can edit and save independently; the last save wins , and changes from other sessions can be overwritten this is separate from multi user content locking above the same behavior applies when another product workflow opens the playbook builder in a new window (for example, create a playbook or recreate playbook on an ai soc case record) do not click those actions multiple times for the same playbook, and finish one builder session before you start another for manual editing on the canvas, see how to create a playbook docid 0 kvg5p4lthw75itmpuwp for playbooks overview docid\ dp agnnne2mjjfgtv2lz5 , see the turbine user guide validation and safety after the agent changes a flow, the platform validates the playbook graph fix validation errors in the canvas or with follow up prompts before you save not supported scenario why move or copy an action between flows each flow is isolated rename a flow to a duplicate display title name collision create, replace, or delete record event or playbook button triggers guardrail — filter only on existing webhook authorization or shared secret configuration out of scope — use the ui enable or disable the entire playbook (product level toggle) use per flow enable or disable export, duplicate, save, or package the playbook ui operation run or test the playbook use test console create or modify applications, fields, or field values out of scope mark inputs sensitive or configure field masking ui security settings group actions into a sub component ui operation cross flow action wiring platform isolation use variables from assets unless mapped to connector actions asset mapping rule reference playbook or component runs in prompts out of scope answer general turbine documentation questions while in building mode use hero ai companion outside the canvas notes and considerations prompts in hero ai native actions, python scripts, and jsonata transformations are not validated and may be incorrect complex (multi level, multi group) filters in loops, conditions, search records, and trigger conditions might not be fully correct filters by attributes with predefined list values are not supported in search records create variables must not be used inside loops when modifying existing actions, the agent changes only what you name or select on the selected flow for end to end validation after ai changes, use the test console docid 1d0fiftjsdox88pvpk5fs see also create and modify playbooks with hero ai docid\ tmmnjglc0e9lipo37kzpb — procedures, clarifying questions, progress detail hero ai docid\ swz8uetvmvoojwgm xnk — overview of hero ai features and building modes playbooks overview docid\ dp agnnne2mjjfgtv2lz5 — canvas layout, flows, and data model hero ai companion docid\ crqkfvngpcz wj8xthds7 — general companion outside the canvas