Playbooks

term definition characteristics playbooks a series of well defined triggers, logic, and actions that automate a workflow user friendly canvas to build playbooks can contain triggers, actions, native actions, components, assets, inputs, and outputs automate workflows to reduce manual processes benefits of playbooks efficiency automates repetitive tasks, saving time and reducing human error consistency ensures that tasks are performed the same way every time, leading to reliable and predictable outcomes scalability can handle increasing volumes of tasks and data without adding manual effort customizability playbooks can be tailored to specific workflows and needs seamless integration playbooks can integrate with external systems and services, automating actions based on real time data inputs as an orchestrator, you can use playbooks to help automate processes and workflows, avoiding manual and repetitive configurations for security events playbook architecture playbooks are designed for quick and easy automation, enabling data processing and enrichment with swimlane turbine’s playbooks, anyone can create modular, repeatable automations that process real time data efficiently playbooks ingest, normalize, and/or enrich data through individual workflows a playbook can have one or more triggers, each with its own flow any number of actions to achieve the desired outcome optional components to enhance the workflow flows term definition characteristics flow a single execution path within a playbook or component, initiated by one trigger and driving subsequent automation each flow can only have one trigger there can be multiple flows in one playbook no cross communication between flows for more details on flows, see docid\ vnclwzre8v2izljbsngkd homepage to access playbooks, follow these steps log in to turbine from the left hand navigation pane, click orchestration and then click playbooks from the playbooks homepage, you can view a list of available playbooks, either enabled or disabled the following table outlines the available features for easier navigation feature function title the title of the pre existing swimlane component or user made component the action title field and component title field have a maximum character limit of 50 characters ensure titles are concise yet descriptive to stay within this limit status indicates whether the playbook is enabled or disabled search enter keywords to search for a component filter use to sort by source, interface, or created by sort by sort by last modified, last created, or alphabetical order arrow icon click to toggle between ascending and descending views ellipsis icon click to access playbook operations such as export and delete plus icon click to create a new playbook create new playbook when setting up an automated workflow, you can create a new playbook to create a new playbook from the playbooks homepage, click the plus icon to open a window where you can enter the playbook name and description once you click save, the playbook canvas opens for you to start building your use case playbook canvas the canvas allows you to create use cases with drag and drop functionality, ai assistance, and other features defining terms and icons the following table shows important user interface (ui) icons and terms used in the canvas toolbar use these icons to customize your playbook canvas icon meaning show/hide the add panel create a new component zoom in/out using the drop down menu enable or disable the playbook show/hide the playbook side panel open test console at the bottom of the window access playbook operations (e g , export, duplicate, delete) add panel the add panel allows you to view, search, filter, sort, and drag and drop actions and components docid\ k8alakpvk17ldlzqu6 it docid\ rj6vmit7bgvijv0ykkkfb docid\ ju3wwjc3jojzgs4catext docid\ ktk9sjearpgfvnngfuchr on the right hand side of the canvas, you can see playbook details, including the name and description to have more space to work within the canvas, click the x icon to close the panel publish playbooks to publish a playbook to the docid\ yqexo79dvepxlby9dihj0 library publish as new content (v1) select publish from the ellipsis icon of the playbooks screen, or navigate to the desired playbook and open the settings menu select publish in the publish content window, select publish as new content (v1) provide a name and description for the content and click next select the content you wish to publish and click next review the selected content, check for potential issues, and click next confirm the details (version 1 0 0), content name, description, and publish message, and click publish a success message confirms that the playbook has been published as new content publish as a new version of existing content (v1+) to update an already published playbook package, follow these steps follow steps 1–3 as outlined in the process in the publish content window, select publish as a new version of existing content (v1+) and choose the package to update review changes, check for issues, and click next confirm the new version (e g , 3 0 0 to 4 0 0) and provide a detailed publish message click publish if merge conflicts are detected, choose to keep library or remote changes and click apply a success message confirms that the updated content has been published you can navigate to the user content library to verify the playbook publication