Automation recipe
A branching automation that labels a new incident task and routes it by severity, paging on-call for the most serious and notifying a team lead for the next tier.
Overview
When an incident is raised, the first minutes matter. An automated runbook labels the incident and routes it by severity so the right people are alerted without anyone consulting a wiki first.
This template is the built-in Incident runbook recipe in Atlas. It fires when an incident task is created, applies an incident label, and branches on severity to page on-call, notify a team lead, or log only.
Because it ships as a branching recipe, the automation templates page shows the severity paths as a tree before you install, so you can see exactly how routing will behave.
What is included
The recipe fires when an incident task is created so response begins immediately.
An action that applies your incident label so the task is easy to find and filter.
Paths for the highest severity to page on-call and the next tier to notify a team lead.
The branching steps render as a tree on the templates page before you install.
Pick the on-call responder, team lead, and incident label, with no rule to write.
How to use it
Go to /settings/automations/templates and select the Incident runbook recipe.
Choose the on-call responder, the team lead for the next tier, and the incident label.
Check the severity branches in the preview so routing matches your response plan.
Install the recipe so new incident tasks are labelled and routed automatically.
FAQ
Ready when you are
Atlas is the all-in-one work OS: tasks, projects, CRM, contracts, HR, and automation on one shared record, with a governed AI assistant. Start free.