Automate → Playbooks

The list of reactive automation playbooks. Each playbook binds a trigger event (something that happens in MisterShell — a health check changes, a config changes, a session ends), optionally narrowed by filters, to a workflow of actions (run an AI agent, send an email, call a webhook, push a config, generate a report, …). Add a Switch to route based on variables or an Approve control to wait for a human decision. See Automation Studio for the event and action catalog and the shared editing workflow.

Playbook authoring happens in the Automation Studio (see Studio); this tab lists what already exists and lets you enable/disable, edit, or delete them.

Authoring playbooks requires the Automation feature in your license. Without it, the Create Playbook and edit buttons are locked (shown with a lock indicator); existing playbooks remain visible.

What you can do

• Filter the list by trigger event or enabled state.
• Enable/disable a playbook.
• Open a playbook in the Studio to edit.
• Create a new playbook (opens an empty Studio).
• See how many times a playbook has run and jump to its runs.
• Delete a playbook.

Common tasks

Filter the list

• Event (dropdown): show only playbooks triggered by a specific event type.
• Enabled (dropdown): show only enabled or only disabled playbooks.

Both filters apply immediately and stack. Clear a filter with the × in its dropdown.

Create a playbook

1. Click Create Playbook (top-right).
2. You are taken to the Studio with an empty canvas. See Studio for how to build the graph.

Edit a playbook

• Click the playbook name (linked) in the table, or click the blue pencil icon in the Actions column. Both open the Studio for that playbook.

Enable / disable

A playbook’s enabled state is shown as a green check or red cross in the Enabled column. To toggle, open the playbook in the Studio and flip the enabled switch in its header.

View a playbook’s runs

In the Run Count column, click the run count (if > 0). You are taken to the Runs tab pre-filtered to this playbook. See Runs.

Delete a playbook

1. Click the red trash icon.
2. Confirm in the dialog.

Historical runs from a deleted playbook remain visible in the Runs tab so that past activity is preserved.

Table columns

Column	Notes
Name	Link into the Studio.
Event	Human-readable trigger event name.
Filter	Chips summarizing field operator value filters applied to the event (e.g., severity = critical). No filters means the playbook fires on every occurrence of the event.
Enabled	Green check / red cross.
Run Count	Count of executions. Click to open filtered Runs view.
Last Run	Timestamp of most recent run, or Never.
Actions	Edit / Delete.

Tips

• Leaving a playbook disabled is the safe way to park work-in-progress. Disabled playbooks do not receive events.
• Trigger filters run before the action chain, so they are a cheap way to reduce noise — a filtered-out event does not produce a run at all.

Permissions

• Read: app.automation.read.
• Write (create / edit / enable): app.automation.write.
• Delete: app.automation.delete.