Run other playbooks inside your playbook using the classic playbook editor
The classic playbook editor will be deprecated soon. For information on converting your playbooks, see Convert classic playbooks to modern playbooks.
You can configure your playbook to run another existing playbook. Call one playbook from another playbook to avoid having to copy and maintain code in different places.
To configure your playbook to run another playbook:
- Drop a new block onto the playbook editor.
- Click on the block, then select Playbook from the block types.
- In the Playbook field, select the playbook you want to run from the drop-down list.
- (Optional) Toggle the Synchronous switch on to make this playbook wait for the called playbook to complete running before continuing.
Playbooks differ from action blocks in the following ways:
- The playbook continues to downstream blocks regardless of whether the called playbook is successful.
- The called playbook doesn't return any values that are used in downstream blocks.
- The called playbook doesn't determine the data set, and it operates on the container data with the scope inherited from the caller.
- The called playbook runs independently from the caller. If you wire a series of playbooks to run, they are processed in parallel if the Synchronous switch is left off. See Determine your playbook flow.
Set container parameters in using the API block with the classic playbook editor
Add custom code to your playbook with the custom function block using the classic playbook editor
This documentation applies to the following versions of Splunk® SOAR (Cloud): current