Playbooks
Create a playbook
Turn any successful chat flow into a named, reusable playbook you can run in one message — with the same approval gates.
What is a playbook?
A Playbook is a saved graph of steps derived from a chat flow. Instead of re-describing a multi-step operation every time, you save it once and run it by name. Playbooks support parameters (so you can pass a branch name, environment, or domain at run time) and conditions (so steps can branch based on outcomes).
Note
Playbooks run with the same approval gates as chat. A deploy playbook still shows you the plan and waits for your OK before shipping.
Create from a chat flow
1
Complete the flow in chat
Run the operation you want to save. Make sure it works end-to-end.
2
Ask DunOps to save it
Say
Save this flow as a playbook in the same chat thread.3
Give it a name
DunOps prompts you for a name. Keep it short and action-oriented.
4
It's saved
DunOps confirms and the playbook appears in your Playbooks list.
chat
Save this flow as a playbook
Save this as a playbook called "Deploy storefront to prod"
Turn what we just did into a reusable playbookNaming tips
Use action-verb names: Deploy storefront to prod, Rotate Stripe API key, Promote staging. Avoid generic names like My flow — you'll thank yourself when you have ten playbooks.
Tip
You can also create a playbook from the canvas — open it from the sidebar, drag in step nodes, and save. Chat creation is faster for linear flows; the canvas is better for branching logic.