---
sourceDocument: Brazil Build workflows
sourceDocumentLink: https://www.servicenow.com/docs/r/build-workflows

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Nested Playbooks

# Nested Playbooks {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Nested Playbooks

Nested Playbooks allow you to embed a child playbook within a parent playbook to organize complex processes and present a clear sequence of steps during runtime.
This feature supports reusability by enabling child playbooks to be used across multiple parent playbooks, reducing duplication and simplifying maintenance.
It also improves performance in Playbook Designer by breaking large playbooks into manageable parts.
Show full answer Show less  

## Key Features

* **Standalone Execution Type:** Child playbooks must be created as standalone, meaning they launch manually without automated triggers. They must be marked as "nestable" and activated to be available for inclusion in parent playbooks.
* **Permissions:** Child playbooks require the same runtime permissions as their parent playbooks to function properly.
* **Optional Activities:** Optional activities cannot be inserted within nested child playbooks at runtime. Only parent playbooks can include optional activities and insertion points.
* **Restart Behavior:** Individual activities or stages within a nested playbook cannot be restarted independently. Restarting is done at the nested playbook level from the parent playbook, controlled by rules such as "Skip on restart," "Run always," and "Skip on first run."
* **Cancellation Behavior:** Cancelling a parent playbook automatically cancels all associated child playbooks. Child playbooks can also be cancelled directly via UI or API.

## Building Nested Playbooks

The process involves two main steps:

* Creating a nestable standalone child playbook designed for reuse.
* Creating a parent playbook that hosts and launches the child playbook.

This structure enables modular and maintainable playbook configurations that enhance operational efficiency and clarity during execution.  
Embed or "nest" a child playbook within a parent playbook to organize your processes and then present the appropriate sequence of steps in the runtime experience. Creating child playbooks that can be used in other parent
playbooks enables you to define sets of activities that can be re-used across multiple playbooks to avoid duplication.
Using nested playbooks can also enable you to break up very large playbooks so they are easier to maintain, and they can load faster in Playbook Designer.

## About nested playbooks {#nested-playbooks__section_hbw_nb3_d3c}

When building child playbooks, they must be of the Standalone execution type. This means that they are launched manually and not with an automated trigger. When you create a new playbook and select the Standalone execution type,
select a check box that allows the playbook to be nested in a parent playbook. The "nestable" playbook must be activated to be visible in the picker for selection as a nestable playbook in a parent playbook.

Permissions

:   Nested (child) playbook must have the same runtime permissions as the parent.

Inserting optional activities
:   In this release, nested playbooks don't support inserting optional activities at runtime. Parent playbooks can still include optional activities, but insertion points are restricted to the parent playbook. Optional activities from
    the parent can't be inserted within a child playbook.

Restarting playbooks
:
    Restart is not supported on individual activities or stages that belong to a nested playbook. A restart of the whole nested playbook can be performed when the nested playbook is restarted from the parent playbook. The restart behavior of the nested playbook from the parent playbook is based on the following restart rules that are defined for the Launch Nested Playbook activity:

    * Skip on restart: The nested playbook is not cancelled and continues to run.
    * Run always: The nested playbook is cancelled, and a new nested playbook is triggered when the launch nested playbook activity starts again.
    * Skip on first run: The nested playbook is only triggered when the parent playbook is restarted. It then follows the Run always rule behavior after subsequent restarts.
    {#nested-playbooks__ul_wr2_rky_23c}

How nested playbooks are affected by cancellation
:   Cancellation of the parent playbook automatically terminates the child playbook. Child playbooks can be cancelled by using the UI or an API.

## Process to build nested playbooks {#nested-playbooks__section_mwj_mc3_d3c}

Building nested playbooks is a two-part process:

1. Build a child playbook that can be nested in a parent playbook. For information about this step, see [Create a nestable child playbook](https://www.servicenow.com/docs/tScGdMVgsQlrMOL_uGamNw "Nest a child playbook within a parent playbook to organize your processes. Creating child playbooks that can be used in other parent playbooks enables you to define sets of activities that can be re-used across multiple playbooks to avoid duplication.").
2. Build a parent playbook that can host the child playbook. For more information about this step, see [Create a parent playbook to host a nestable child playbook](https://www.servicenow.com/docs/9RG1spBrT_T9izw7KzMnbw "After you have created a nestable child playbook, then you can create a parent playbook to host the child playbook.").
{#nested-playbooks__ol_sxp_4c3_d3c}