Splunk® SOAR (On-premises)

Build Playbooks with the Playbook Editor

As of version 6.4.0, the visual editor for classic playbooks is no longer part of Splunk SOAR. Before upgrading, convert your classic playbooks to modern mode. Your classic playbooks will continue to run and you can view and edit them in the SOAR Python code editor.
For details, see:
This documentation does not apply to the most recent version of Splunk® SOAR (On-premises). For documentation on the most recent version, go to the latest release.

Save a playbook so that can access it using the classic playbook editor

You must save a playbook before can use it. If the playbook has errors, an error message appears with additional information. You cannot save a playbook until you resolve all errors.

  1. Click Save to begin saving a playbook.
  2. Enter a brief description of the playbook.
  3. (Optional) Click Reuse this comment until the editor is reloaded if you want to use the same description each time you save the playbook.
  4. Click Save to finish saving the playbook.

Create a copy of an existing playbook

You can create a copy of any saved playbook by using the Save As option.

Perform the following tasks to create a copy of an existing playbook:

  1. Click the down arrow next to the Save button and click Save As.
  2. Enter a new name for the playbook.
  3. Select the repository where you want to save the playbook.
  4. (Optional) Enter comments or a description about the playbook.
  5. Click Save.
Last modified on 01 February, 2025
Determine your playbook flow using the classic playbook editor   Use keyboard shortcuts in the classic playbook editor

This documentation applies to the following versions of Splunk® SOAR (On-premises): 5.1.0, 5.2.1, 5.3.1, 5.3.2, 5.3.3, 5.3.4, 5.3.5, 5.3.6, 5.4.0, 5.5.0, 6.0.0, 6.0.1, 6.0.2, 6.1.0, 6.1.1, 6.2.0, 6.2.1, 6.2.2, 6.3.0, 6.3.1

Acrobat logo Download manual
Acrobat logo Download this page

Please expect delayed responses to documentation feedback while the team migrates content to a new system. We value your input and thank you for your patience as we work to provide you with an improved content experience!

Was this topic useful?







You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters