Test and publish
Before publishing, test how your Playbook behaves across common flows and edge cases. This page covers testing, publishing, and ongoing management of Playbooks.
Test your Playbook
- Walk through the most common paths first, then expand to edge cases — missing inputs, unexpected values, alternate branches.
- Test from the perspective of different end user types.
- Account for error states and fallback scenarios.
You can preview the Playbook in isolation using Test Playbook, or simulate a full conversation using Test AI Agent to confirm it triggers under the right conditions. Test AI Agent is only available for active Playbooks — inactive Playbooks can only be tested using Test Playbook.
Save and publish
Playbooks can be saved as inactive (draft) or active (live in end user interactions). This allows you to work on Playbooks incrementally without affecting the end user experience.
Duplicate a Playbook
To reuse the structure or content of a Playbook, create a copy using the Duplicate option. This is useful for iterating on workflows, experimenting with variations, or creating templates.
Edit or delete a Playbook
Go to Config > Playbooks and open the Playbook to manage.
- Edit: Modify content and save as active or inactive.
- Delete: Select Delete Playbook from the More options menu.
View dependencies
In the Playbook list, each row displays a dependency summary showing counts of linked Playbooks, Actions, Variables, and Handoffs.
Select a Playbook to see the full dependency breakdown:
- Used in: Parent Playbooks that reference this one.
- Uses: Handoffs, Actions, and Variables this Playbook references.
Dependency safeguards
- Deletion protection: You cannot delete a Playbook referenced by an active parent Playbook. Remove the reference first, then delete.
- Circular dependency prevention: Playbooks cannot reference each other in a loop. If saving would create a circular dependency, the save fails and a notification displays the conflicting dependency chain.
