Rebuilding existing playbooks in Workflow Studio

You can’t convert existing flows directly into playbooks in Workflow Studio. Each flow designer step that creates a response task to guide the analyst must be broken down into separate actions or subflows.

You are not allowed to convert existing flows directly into playbooks in Workflow Studio. Each flow designer step that creates a response task to guide the analyst must be broken down into separate actions or subflows. By using these granular subflows or actions, you must create activity definitions. After you build these activity definitions, they get added as activities within stage in the process definition. You can reuse activity definitions across multiple playbooks.

You can customize each activity to render the required actions within them and how the card should look while building the activity definition. The activity can show email clients, tables, actions, KB articles, URLs, and so on. You can define how the activity definition and underlying action or subflows are created.

For more information, refer to the following sections.

• Activity definitions

• Process Automation Designer

Parent Topic:Using SIR Workspace

Related topics

{Using ServiceNow Otto for Security Incident Response (SIR) generative AI skills}[]

{Using agentic AI workflows}[]

{Working with Security Incident Records}[]

{Security Incident Playbook}[]

{Prerequisites for the Playbooks}[]

{Activity Definitions}[]

{Sample Playbooks for SIR Workspace}[]

{Working with MSI Records}[]

{Working with Form UI actions}[]

{Security Incident Closure workflow}[]

{Handle security incidents using Advanced Work Assignment}[]