---
title: Nested Playbooks
slug: nested-playbooks
docTags: 
createdAt: 2025-08-11T11:13:46.000Z
---

You can nest playbooks into other playbooks as actions. Refer to [Actions](docId\:VvMOb1j4tnj3RVUeXax01) for instructions to add an action to a playbook.

## Terms

| Term            | Meaning                                              |
| --------------- | ---------------------------------------------------- |
| Parent playbook | A playbook that calls another playbook.              |
| Nested playbook | A playbook that calls another playbook as an action. |

:::hint{type="info"}
When nesting a playbook into a parent playbook, the nested playbook's inputs and outputs are available to map to and use in the parent playbook.
:::

To nest a playbook to a new/current playbook:

1. Navigate to the **Playbooks** home page, and then open a playbook (or create/upload a playbook).
2. Click **Add an action**.
3. From **ACTION**, click the **Action** drop-down menu, and select an existing playbook.
4. From **ACTION**, add a title.

::Image[]{src="https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/LJIS4LP88pgdUhmCMtpid_nested-parent-playbook-action-window.png" size="66" width="1128" height="593" darkWidth="800" darkHeight="420" position="center" indent="2" showCaption="false"}

5. Click **Configure** to map inputs and outputs.
6. If the nested playbook has inputs and/or outputs, they are available on **Action Inputs**.
7. Review **Action Outputs**.

::Image[]{src="https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/v9jbZ--ODhn5amkWQrdKw_nested-parent-outputs.png" size="68" width="1784" height="771" darkWidth="800" darkHeight="345" position="center" indent="2" showCaption="false"}

8. When finished, click **Apply**.

You have successfully nested a playbook to your current playbook.

## View Parent Playbooks as Triggers in Nested Playbooks

:::hint{type="info"}
You do not need to select a trigger before adding and configuring actions and conditions.
:::

A trigger automates actions based on the criteria set within a playbook. Playbooks can also be triggers. There are parent and nested playbooks.

When an action is configured to call a nested playbook, the nested playbook will show that parent playbook as a trigger.

:::hint{type="warning"}
If you have more than one playbook as a trigger, click the desired playbook trigger, which will be visible with a blue highlight box around the trigger.
:::

::Image[]{src="https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/GOg5S1sWkuHitOnRnHhXz_nested-playbook-as-trigger.png" size="74" width="1140" height="477" darkWidth="800" darkHeight="335" position="center" showCaption="false"}

The TRIGGER panel displays To view the list of parent playbooks and triggers:

1. From TRIGGER, click **Open Parent Playbook**.

::Image[]{src="https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/J1wX5CoZfi-msDWYXFROe_open-parent-playbook.png" size="24" width="400" height="750" darkWidth="800" darkHeight="1500" position="center" indent="2" showCaption="false"}

2. The parent playbooks and triggers open in a new tab. From here, view and/or make updates to the parent playbooks.
3. **Important!** When calling nested playbooks, Turbine's default configuration is for a maximum depth of 10 playbook levels.