Workflow Automation CoE > Playbooks > Building Dynamic Playbooks > Part 4: Nested Playbooks
This is Part 4, the final article in a four-part series on dynamic playbooks. Start with Part 1: Overview and Conditional Activities » for the full pattern lineup or continue below for the deep dive on nested playbooks.
Goal
In this article, you will learn how to use nested playbooks in Workflow Studio to build a reusable Knowledge Management (KM) content quality review process that can be embedded in multiple parent playbooks, without duplicating the logic.
Technology
|
Product/Feature |
Description |
|
End-to-end process automation with a guided user experience layered on top of subflows or flow actions |
|
|
Standalone child playbooks embedded in a parent, functioning like subflows for playbooks |
Instructions
Use Case: Reusable Quality Review with Nested Playbooks
The scenario. Your organization has a standard content quality review process: a reviewer runs through a quality checklist, records a quality score, and decides whether the article passes or fails. If it fails, a remediation task is created, and the review pauses until remediation is complete. This same quality review needs to happen in three different contexts: during initial article creation, during periodic article maintenance, and when processing feedback that triggers an update.
Why nested playbooks. Rather than duplicating the quality review logic in three separate playbooks, you build it once as a standalone child playbook and embed it in each parent. Changes to the quality review process propagate automatically to every parent playbook that uses it. This works just like creating a reusable subflow, but at the playbook level.
Important: The child playbook must use the Standalone execution type and be activated with at least one launch playbook permission defined before it can be nested.
Since nested playbooks are configured as Standalone and do not have a parent record against which they run, it is recommended to add relevant inputs to provide context. These are defined in the Playbook properties.
Like in subflows, we provide an out-of-the-box step in playbooks to assign outputs from runtime data that will then be available to the parent playbook.
Attention: There’s currently a small defect on Australia instances that affects the Set Playbook Outputs activity. We expect this defect to be fixed with Process Automation Designer v30.1, releasing in September 2026. (Disclaimer: The exact release date may change.)
The Playbook Outputs Var Table Name is supposed to be pre-filled and read-only, which it is currently not. To work around the issue, please enter var__m_sys_pd_process_output_<sys_id of playbook>, then you will be able to pick from the defined outputs for this playbook.
How to nest a playbook
To nest a child playbook, open the parent playbook in Diagram view, select the + icon inside a stage, and choose the Add a playbook icon from the mini picker. Search for your activated child playbook and configure the child properties.
When the parent playbook is executed, nested playbook activities seamlessly insert in the same playbook experience at the stage where it launched. The process worker doesn’t even notice that a child playbook has started and they can continue working without friction.
Tip: Optional activities are not currently supported within nested child playbooks. If you need optional activities, add them at the parent playbook level.
Conclusion
Reach for nested playbooks when the same process segment needs to run in multiple parent playbooks, and you want a single source of truth that updates everywhere it's used.
This wraps up the series. For the full pattern lineup and the "which pattern do I need" quick reference, revisit Part 1: Overview and Conditional Activities ».
We want to hear from you. If you can think of cool use cases that you could solve with nested playbooks, or you have a use case that doesn't quite fit this example, drop it in the comments. And if you've made it through the whole series, we'd love to hear how you're combining these patterns in your own KM (or non-KM) playbooks.
Series Navigation
|
Part |
Article |
Link |
|
1 |
Overview and Conditional Activities |
|
|
2 |
Decision Activities and Decision Stages |
|
|
3 |
Playbook Variants |
|
|
4 |
Nested Playbooks |
(this article) |
