.svg)
.svg)
/rootly and /incident prefixes.
These commands are built-in and cannot be modified. To create custom commands that trigger your own workflows or forms, see Custom Workflows and Custom Forms.
Quick Reference
| Icon | Meaning |
|---|---|
| π | Works in any Slack channel |
| π¨ | Requires incident channel |
Getting Started
| Command | Description | Where |
|---|---|---|
/rootly connect | Link your Slack account to Rootly | π |
/rootly help | View available commands and descriptions | π |
/rootly support | Report an issue to Rootly | π |
Create & View Incidents
| Command | Description | Where |
|---|---|---|
/rootly new | Declare a new incident and create a channel | π |
/rootly test | Create a test incident (not publicly announced) | π |
/rootly maintenance | Schedule a maintenance window | π |
/rootly list | View up to 10 active incidents | π |
/rootly overview | Open incident control center | π¨ |
/rootly catchup | Get AI-powered incident summary | π¨ |
Update Incidents
| Command | Description | Where |
|---|---|---|
/rootly update | Edit incident fields (severity, type, etc.) | π¨ |
/rootly summary | Add or edit incident summary | π¨ |
/rootly timeline | Add an event to the incident timeline | π¨ |
/rootly timestamps | Edit status change timestamps | π¨ |
/rootly convert | Convert current channel to incident channel | π (non-incident) |
Incident Status
| Command | Description | Where |
|---|---|---|
/rootly status | Change incident status | π¨ |
/rootly mitigate | Mark incident as mitigated | π¨ |
/rootly resolve | Mark incident as resolved | π¨ |
Teams & Services
| Command | Description | Where |
|---|---|---|
/rootly add team | Attach a team to the incident | π¨ |
/rootly add service | Tag impacted services | π¨ |
/rootly add functionality | Tag impacted functionalities | π¨ |
/rootly add alert | Associate an alert with the incident | π¨ |
Roles & Assignments
| Command | Description | Where |
|---|---|---|
/rootly assign | Assign, add, or remove incident roles | π¨ |
/rootly escalate | Escalate to PagerDuty, Opsgenie, or VictorOps | π¨ |
Action Items
| Command | Description | Where |
|---|---|---|
/rootly task | Create a task (to complete during incident) | π¨ |
/rootly followup | Create a follow-up (post-incident action) | π¨ |
/rootly add action item | Create a task or follow-up | π¨ |
/rootly action items | View action items assigned to you | π¨ |
On-Call & Paging
| Command | Description | Where |
|---|---|---|
/rootly oncall | View on-call schedules | π |
/rootly page | Page a schedule, team, or escalation policy | π (with On-Call) / π¨ |
/rootly alerts | View all alerts | π |
Advanced
| Command | Description | Where |
|---|---|---|
/rootly manage fields | Set values for custom incident fields | π¨ |
/rootly integrations | Manage links to integrated tools (Jira, PagerDuty, etc.) | π¨ |
/rootly statuspage | Publish an update to a status page | π¨ |
/rootly feedback | Log feedback about the incident response | π¨ |
/rootly duplicate | Mark incident as duplicate of another | π¨ |
/rootly sub | Create a sub-incident | π¨ (parent) |
/rootly workflows | Manually trigger a workflow | π¨ |
Command Details
Creating Incidents
Creating Incidents
/rootly new
Opens the incident creation form. Fill in title, summary, severity, and type. Rootly will:- Create a dedicated Slack channel
- Post the initial incident message
- Trigger configured workflows
/rootly test
Same as /rootly new, but the incident is marked as a test and wonβt be publicly announced. Use for training and workflow testing./rootly maintenance
Schedule planned maintenance. Maintenance incidents appear in the Rootly web UI and can be published to status pages.Managing Status
Managing Status
/rootly status
Opens a modal to change the incident status (In Triage β Active β Mitigated β Resolved β Closed)./rootly mitigate
Quick action to mark the incident as mitigated. Youβll be prompted to add a comment explaining the mitigation./rootly resolve
Quick action to mark the incident as resolved. Youβll be prompted to add a resolution comment.Action Items
Action Items
Tasks are actions to complete during the incident (e.g., βRestart the databaseβ).Follow-ups are post-incident actions (e.g., βAdd monitoring for this failure modeβ).Use
/rootly action items to see a checklist of items assigned to you for this incident.On-Call Commands
On-Call Commands
/rootly oncall
View whoβs currently on-call for any schedule. Works with Rootly On-Call and integrated providers (PagerDuty, Opsgenie, VictorOps)./rootly page
Page responders through Rootly On-Call. Select schedules, teams, or escalation policies. Add an optional note for context./rootly escalate
Escalate the current incident to external paging providers. Requires the relevant integration to be installed.Channel Conversion
Channel Conversion