Build and run playbooks

Prerequisites

playbooks.read and playbooks.write.
Saved, individually tested workbooks for every step.
playbooks.read to export; playbooks.write to import and run.
tasks.write to schedule and tasks.run to validate immediately.

Route

Open /automations/playbooks.
Open /automations/tasks.

How to build and validate a playbook

Select New playbook, or use Generate with AI and review the generated draft and proposed workbooks.
Name the playbook and add steps in dependency order.
Select a workbook for each step.
Set Always run or a running-severity threshold of warning, error, or critical.
Where supported by the draft/editor, map static parameters and structured output from earlier steps; ensure the producer emits each referenced key.
Optionally emit a completion notification event and choose its minimum severity.
Save, select Run, and confirm execution.
Open History and expand the run to inspect each succeeded, failed, or skipped step and its reason.

Expected result: Enabled steps execute in order; severity gates skip steps below their threshold; the run records the worst severity and per-step outcomes.

Verification: Run at least one healthy and one warning/error scenario. Confirm gates, mappings, failure stopping behavior, and the final notification event if enabled.

How to import, export, and schedule a playbook

Select Export to download the playbook bundle, including its referenced workbooks.
In the destination environment, select Import and choose the reviewed bundle.
Inspect the imported playbook and every imported workbook for commands, identifiers, parameters, and connection scope.
Run each workbook independently, then run the playbook and inspect per-step history.
Go to /automations/tasks, create a playbook-target schedule, and save it paused.
Use Run now, inspect task and playbook histories, then enable the schedule.

Expected result: The playbook and required workbooks are available in the destination and execute correctly before recurrence is enabled.

Verification: Confirm references resolve, no required step is missing, and the scheduled run links to the expected playbook result.

Safety and rollback

Imported portability does not prove provider compatibility. Pause or archive the schedule first, then remove an invalid playbook only after checking references. External writes require provider-specific rollback.

A gate is workflow logic, not authorization. Every step retains its workbook’s provider permissions and side effects. Keep detection and remediation separate. Edit or delete the playbook to stop future manual use, and pause any scheduled task that references it; reverse provider-side changes separately.

Troubleshooting

Symptom	Resolution
Missing workbook	re-import the complete playbook export and review import feedback.
Duplicate-looking workbook	compare definitions and references before deleting either copy.
Scheduled run differs from manual run	compare connection, parameter, run mode, and actor context.
Unexpected skip	inspect the accumulated severity before that step and its threshold.
Empty mapping	enable structured extraction in the producing workbook and match its key exactly.
Run stops	inspect the first failed step; later steps are not a recovery mechanism unless explicitly designed.
Wrong scope	verify each workbook’s connection and parameters, not only the playbook.
Playbooks overview	Review connector configuration and retry.
Build and run workbooks	Review connector configuration and retry.