Guide
Runbook Step Reference
Pick the right step family for the job and avoid adding steps that your workspace is not ready to run.
Common step families
Coverage and paging: contact the current on-call coverage, assign incident roles from coverage, or post owner context.Chat and bridge: create or notify Slack and Microsoft Teams channels, create Zoom or Google Meet bridges, or invite people into the working channel.Ticketing and status: create Jira issues, create PagerDuty incidents, or create customer-facing Statuspage incidents.Retrospective and exports: export retrospective output to Confluence or Google Docs.Notifications and waits: send custom notifications, wait for incident phases, wait for retrospective milestones, or repeat a check on a timer.
Use this page to choose well
- Use a step only if it is marked ready in the builder.
- Prefer steps that can derive incident context automatically instead of forcing responders to fill the same details again.
- Keep manual steps for human judgment and use automation for repeatable actions with a clear success condition.
- If one step depends on another, express that with step conditions instead of relying on responder memory.
When to split a runbook
- Split the runbook when one branch is for chat setup and another is for customer communications.
- Split the runbook when one part is always safe to automate and another still needs judgment.
- Split the runbook when different teams own different parts of the process.