# Rootly > Rootly is an incident management platform that helps engineering teams detect, respond to, and learn from incidents. It integrates with Slack, PagerDuty, Jira, and 60+ other tools, and provides on-call scheduling, alert routing, AI-powered summaries, automated workflows, and collaborative retrospectives. ## Getting Started - [Welcome to Rootly help and documentation](https://docs.rootly.com/help-and-documentation.md): The all-in-one AI platform for on-call, incident response, status pages, and post-incident learning. - [Switching to Rootly](https://docs.rootly.com/switch/switch.md): Move to Rootly from your current on-call tool. Rootly-led migrations bring your users, schedules, and escalation policies over without a rebuild. ### Quick Start - [Signing Up](https://docs.rootly.com/signing-up.md): Create a Rootly account or accept an invitation from your organization to get started with incident management, on-call scheduling, and integrations. - [Manage incidents in Slack with the Rootly integration](https://docs.rootly.com/integrating-with-slack.md): Connect Slack to Rootly to run incidents from Slack with channels, slash commands, message actions, notifications, and Workflow Builder connector controls. - [Microsoft Teams Integration](https://docs.rootly.com/integrating-with-microsoft-teams.md): Connect Microsoft Teams to Rootly to create incident channels, post real-time updates, and start Teams meetings directly from an incident. - [Google Chat Integration](https://docs.rootly.com/integrating-with-google-chat.md): Connect Google Chat to Rootly to create incident spaces, send notifications, run slash commands, and manage on-call alerts directly from chat. - [User Profile](https://docs.rootly.com/user-profile.md): Manage your Rootly account settings, contact details, notification preferences, linked accounts, and subscriptions from your personal user profile page. - [Rootly quick start: sign up, connect Slack, run a demo](https://docs.rootly.com/quick-start-guide.md): Get up and running with Rootly in about 15 minutes, from signing up to connecting Slack, configuring teams, and creating your first incident end to end. ## Alerts - [Alerts: ingestion, deduplication, grouping, and routing](https://docs.rootly.com/alerts/alerts.md): How Rootly ingests, deduplicates, groups, and routes alerts from monitoring tools, with links to setup guides for each stage of the alert lifecycle. ### Routing & Noise Reduction - [Alert Routing](https://docs.rootly.com/alerts/alert-routing.md): Use Alert Routes to determine which teams, services, and escalation policies receive incoming alerts from your monitoring tools based on conditions you define. - [Alert Deduplication](https://docs.rootly.com/alerts/alert-deduplication.md): Collapse repeat events from the same monitor into a single open Rootly alert using a stable identifier, so responders aren't paged twice. - [Alert Grouping](https://docs.rootly.com/alerts/alert-grouping.md): Reduce alert noise by automatically grouping related alerts into a single, leader-driven alert based on time windows, fields, and matching attributes. - [Why did an alert post twice to a Slack channel?](https://docs.rootly.com/alerts/duplicate-slack-alert-messages.md): Find and remove the second notification path when one Rootly alert produces two duplicate Slack messages in the same channel. ### Alert Data - [Alert Fields](https://docs.rootly.com/alerts/alert-fields.md): Use Alert Fields to extract, normalize, and store structured alert data for routing, enrichment, automation, and triage across Rootly. - [Alert Statuses](https://docs.rootly.com/alerts/alert-statuses.md): Understand how alerts progress through their lifecycle in Rootly, including triggered, acknowledged, and resolved states with valid transitions. - [Alert Urgency](https://docs.rootly.com/alerts/alert-urgency.md): Learn how Alert Urgencies determine alert priority across Alert Sources, Heartbeats, Live Call Routing, and Escalation Policies for paging rules. ### Paging & Monitoring - [Manual paging in Rootly: Slack, Web, and mobile](https://docs.rootly.com/alerts/manual-paging.md): Manually page users, teams, services, or escalation policies from Rootly Web, Slack, or mobile for ad-hoc escalations and bringing in subject matter experts. - [Heartbeats](https://docs.rootly.com/on-call/heartbeats.md): Continuously verify system health using Rootly Heartbeats and automatically trigger alerts on missed pings from cron jobs, schedulers, and background workers. - [Live Call Routing](https://docs.rootly.com/on-call/live-call-routing.md): Set up live call routing in Rootly with voicemail, live connect, IVR calling trees, and phone-based on-call escalation for support phone numbers. ## On-Call - [Get started with Rootly On-Call paging and routing](https://docs.rootly.com/on-call/on-call.md): Understand how Rootly On-Call ensures the right people are paged at the right time using schedules, escalation policies, and real-time routing. - [On-Call Pay Calculator](https://docs.rootly.com/on-call/on-call-pay-calculator.md): Accurately calculate and export on-call compensation in Rootly based on real schedule data, holiday rules, and configurable pay rates for finance and HR. ### Being On-Call - [Getting started with Rootly notifications](https://docs.rootly.com/notifications/getting-started.md): Configure general and on-call notifications in Rootly including email, Slack, SMS preferences, shift reminders, escalation rule layers, and contact methods. - [Configure on-call notification rules and shift reminders](https://docs.rootly.com/on-call/on-call-notifications.md): Set up shift reminders and personal notification rules in Rootly On-Call to control how and when you receive alerts via email, push, SMS, and phone calls. - [Phone & SMS Setup](https://docs.rootly.com/notifications/notification-phone-numbers.md): Download Rootly contact cards so your phone can recognize incoming Rootly calls and SMS notifications from on-call paging, IVR routing, and escalations. - [Shift Reminders](https://docs.rootly.com/on-call/shift-reminders.md): Configure Rootly on-call shift reminders that alert you before a shift starts and when it ends, with timing options, nested schedules, and troubleshooting. - [On-Call Widget](https://docs.rootly.com/on-call/on-call-widget.md): See your live on-call status in the Rootly web sidebar—whether you're on call now, your next shift, active pages, and notification-setup gaps—from any page. - [Rootly Mobile App](https://docs.rootly.com/on-call/mobile-app.md): Download and use the Rootly mobile app for iOS and Android to receive, acknowledge, and escalate alerts while on-call, with critical alert and override support. - [Mobile Home Screen Widgets](https://docs.rootly.com/on-call/mobile-widgets.md): Add the Rootly on-call widget to your iPhone or Android home screen to see your on-call status, shift times, and schedules at a glance. - [Alert Muting](https://docs.rootly.com/on-call/alert-muting.md): Temporarily mute automated Rootly alert notifications to yourself from the mobile app during an alert storm, without affecting escalations or teammates. ### Escalation - [Escalation policies for on-call alert routing](https://docs.rootly.com/on-call/escalation-policies.md): Configure Rootly escalation policies with multi-step targets, time delays, and round robin to make sure on-call alerts get acknowledged and acted on. - [Round Robin Functionality](https://docs.rootly.com/on-call/round-robin-functionality.md): Distribute alerts evenly among on-call team members in Rootly using alert-based and cycle-based round robin escalation strategies for fair workload sharing. ### Schedules & Shifts - [On-call schedules, rotations, and overrides](https://docs.rootly.com/on-call/schedules.md): Create, manage, and maintain on-call schedules in Rootly with rotations, layers, overrides, restrictions, and previews to keep coverage clear and predictable. - [Edit Schedules](https://docs.rootly.com/on-call/edit-schedules.md): Update on-call schedules in Rootly, manage overrides, swap shifts, and pause paging without disrupting historical data, audit trails, or reporting. - [Sync Schedules to Slack User Groups](https://docs.rootly.com/on-call/sync-schedules.md): Keep Slack user groups automatically in sync with your Rootly on-call schedules so the right responder is always reachable through @mentions and routing. - [On-Call Shifts](https://docs.rootly.com/on-call/on-call-shifts.md): View current and upcoming on-call coverage in Rootly, manage overrides and swaps, and identify schedule gaps before they cause missed alerts and escalations. - [Requesting Shift Coverage](https://docs.rootly.com/on-call/request-coverage.md): Request coverage in Rootly when you can't work an on-call shift and automatically reassign responsibility to teammates with approval workflows. - [On-Call Shadowing](https://docs.rootly.com/on-call/on-call-shadowing.md): Use on-call shadowing in Rootly to safely train new responders alongside primary on-call without duplicating schedules, paging both, or risking missed alerts. - [Adding a Holiday Calendar](https://docs.rootly.com/on-call/holiday-calendar.md): Preview team holidays and PTO directly alongside your Rootly on-call schedules to proactively identify coverage gaps and plan rotations around time off. ### Insights - [On-Call Metrics](https://docs.rootly.com/on-call/on-call-metrics.md): Analyze on-call performance using response time, alert volume, acknowledgement, and escalation metrics to continuously improve reliability and responder health. - [On-Call Readiness](https://docs.rootly.com/on-call/on-call-readiness.md): Ensure responders are prepared to receive alerts with the Rootly On-Call Readiness report, which surfaces missing contact methods and rules. - [Supported Countries](https://docs.rootly.com/on-call/supported-countries.md): Reference list of countries supported for SMS, push, and phone call notifications in Rootly On-Call, including delivery routes and regional carrier information. ### Migrations - [Migrating From PagerDuty](https://docs.rootly.com/switch/pagerduty-migration.md): Migrate from PagerDuty to Rootly On-Call: concept mapping, what gets imported, timeline, parallel-running patterns, and cutover validation steps. - [Opsgenie Migration](https://docs.rootly.com/switch/opsgenie-migration.md): Migrate users, schedules, teams, services, routing rules, and notification settings from Opsgenie to Rootly On-Call with a Rootly-led, API-based import. ## Incident Response - [Incident management lifecycle in Rootly](https://docs.rootly.com/incidents/incidents.md): Understand how Rootly streamlines incident response through automated detection, paging, triage, and response workflows across your entire incident lifecycle. - [Incident Lifecycle](https://docs.rootly.com/incidents/incident-lifecycle.md): How Rootly models an incident from triage through closure — every status, the timestamps each one records, and how transitions actually happen. - [Incident Response Setup Checklist](https://docs.rootly.com/incident-response-setup-checklist.md): Work through the configuration that makes incident response automatic: declaration forms, the incident channel, roles and runbooks, and closing the loop. - [Responder Checklist](https://docs.rootly.com/responder-checklist.md): If you're the one jumping into the incident channel (not the one configuring forms and workflows), this part is for you. ### Creating Incidents - [Creating Incidents via Web Interface](https://docs.rootly.com/incidents/creating-incidents/creating-incidents-via-web-ui.md): Create incidents through the Rootly web interface with customizable form fields, severity selection, validation rules, and post-creation automation triggers. - [Creating Incidents via Slack Interface](https://docs.rootly.com/incidents/creating-incidents/creating-incidents-via-slack.md): Create incidents from Slack using slash commands or message actions with customizable fields, validation, severity, and channel auto-creation. - [Creating Incidents via PagerDuty Integration](https://docs.rootly.com/incidents/creating-incidents/creating-incidents-via-pagerduty.md): Create Rootly incidents from PagerDuty alerts with automatic service mapping, resolution sync, severity translation, and troubleshooting tips. - [Creating Incidents via API](https://docs.rootly.com/incidents/creating-incidents/creating-incidents-via-api.md): Create incidents programmatically using the Rootly API with supported fields, custom fields, sub-incidents, severity levels, and error handling. - [Converting Existing Slack Channels to Incidents](https://docs.rootly.com/incidents/creating-incidents/converting-existing-slack-channels-to-incidents.md): A step-by-step guide to converting an existing Slack channel into a Rootly incident channel without losing message history, members, or context. - [Incident Title Generator](https://docs.rootly.com/incidents/creating-incidents/incident-title-generator.md): Learn how Rootly automatically generates unique incident titles using random adjective–noun combinations while allowing full customization and manual editing. ### Managing Incidents - [Managing Incident Status via Slack](https://docs.rootly.com/incidents/managing-incidents/managing-incident-status-via-slack.md): Step-by-step guide to updating incident lifecycle status directly from an incident's Slack channel using Rootly slash commands and interactive status modals. - [Resolving Incidents via Web Interface](https://docs.rootly.com/incidents/managing-incidents/resolving-incidents-via-web-ui.md): Move incidents through the Mitigated and Resolved stages using the Rootly web interface to capture timestamps, mitigation notes, and resolution details. - [Resolving Incidents via Slack](https://docs.rootly.com/incidents/managing-incidents/resolving-incidents-via-slack.md): Resolve incidents directly from Slack using Rootly's /rootly resolve command and status update modal to capture resolution context and trigger retrospectives. - [Updating Incident Timestamps](https://docs.rootly.com/incidents/managing-incidents/updating-incident-timestamps.md): Update incident timestamps in Rootly for accurate event documentation, compliance tracking, retrospective analysis, and SLA reporting after the fact. - [Adding Incident Feedback](https://docs.rootly.com/incidents/managing-incidents/adding-incident-feedback.md): Learn how to submit and manage incident feedback through both the Rootly web interface and Slack. Each user may submit feedback once per incident. - [Updating Incident Integration Links](https://docs.rootly.com/incidents/managing-incidents/updating-incident-integration-links.md): View, edit, and update external integration links for incidents through both the Rootly web interface and Slack to keep Jira, ticketing, and docs in sync. ### Roles & Access - [Incident Roles Overview](https://docs.rootly.com/incidents/incident-roles/incident-roles.md): Understand how incident roles provide structure, clarity, and accountability during incidents, and how they are managed in the Rootly web interface and Slack. - [Managing Incident Roles Through Slack](https://docs.rootly.com/incidents/incident-roles/managing-incident-roles-through-slack.md): Assign, update, and manage incident roles like Incident Commander and Comms Lead directly from Slack using slash commands and dialogs. - [Managing Incident Roles Through the Web Interface](https://docs.rootly.com/incidents/incident-roles/managing-incident-roles-through-the-web.md): Configure, assign, and manage incident response roles like Incident Commander and Comms Lead using the Rootly web interface for clear ownership. ### Private Incidents - [Private Incidents](https://docs.rootly.com/incidents/private-incidents/private-incidents.md): Learn how private incidents in Rootly restrict access beyond RBAC with incident-level permissions managed through the web UI and Slack for sensitive cases. - [Managing Private Incident Access via Slack](https://docs.rootly.com/incidents/private-incidents/manage-via-slack.md): Learn how to manage and control access to private incident channels directly through Slack using Rootly’s access management commands and modal. - [Managing Private Incident Access via Web Interface](https://docs.rootly.com/incidents/private-incidents/manage-via-web.md): Manage and control access to private incidents in Rootly directly through the web interface, including viewer lists, RBAC overrides, and audit history. ### Timeline - [Incident Timeline](https://docs.rootly.com/incidents/incident-timeline/incident-timeline.md): Understand how Rootly incident timelines capture key events, decisions, status changes, and system signals throughout the incident lifecycle for retrospectives. - [Adding Events to Timeline via Slack](https://docs.rootly.com/incidents/incident-timeline/adding-events-to-timeline-via-slack.md): Add timeline events from Slack using the /rootly timeline command, message actions, or emoji reactions to capture key moments during incident response. - [Adding Events to Timeline via Web Interface](https://docs.rootly.com/incidents/incident-timeline/adding-events-to-timelines-in-the-web-ui.md): Add timeline events directly from the Rootly web interface with markdown support for event descriptions, custom timestamps, and visibility controls. - [Adding Events to Timeline via Email](https://docs.rootly.com/incidents/incident-timeline/adding-events-to-timeline-via-email.md): Add events to incident timelines by responding to incident emails through the Rootly Email integration, capturing context from external stakeholders. - [Adding Events to Timeline via API](https://docs.rootly.com/incidents/incident-timeline/adding-events-via-api.md): Add timeline events to incidents programmatically via the Rootly API with visibility controls, custom event fields, timestamps, and bulk import support. ### Action Items - [Action Items](https://docs.rootly.com/incidents/action-items/action-items.md): Understand how action items—including tasks and follow-ups—help teams drive effective incident response and long-term reliability improvements. - [Creating Action Items in Slack](https://docs.rootly.com/incidents/action-items/adding-action-items-via-slack.md): Create tasks and follow-ups in Slack using slash commands, emoji reactions, or message menus to convert incident discussions into actionable items. - [Creating Action Items in Web Interface](https://docs.rootly.com/incidents/action-items/adding-action-items-via-web-ui.md): Add tasks and follow-ups to incidents through the web interface, with options for exporting to external tools and manual tracking. - [Creating Action Items via Automation & API](https://docs.rootly.com/incidents/action-items/adding-action-items-via-api.md): Automate action item creation through workflows, incident roles, and direct API integration for scalable incident response processes. - [Viewing Action Items in Slack](https://docs.rootly.com/incidents/action-items/todo-list-via-slack.md): View and manage your assigned incident action items directly in Slack incident channels using the /rootly tasks command and interactive modal dialogs. - [Custom Fields on Action Items](https://docs.rootly.com/incidents/action-items/action-item-custom-fields.md): Add custom fields to tasks and follow-ups to capture organization-specific metadata, drive reporting, power workflow automation, and enrich ticketing exports. - [SLA Policies for Follow-Ups](https://docs.rootly.com/incidents/action-items/sla-policies.md): Use SLA policies to set assignment and completion deadlines on follow-up action items, get notified before deadlines pass, and track violations. ### Incident Operations - [Marking Incidents as Duplicate](https://docs.rootly.com/incidents/incident-operations/marking-as-duplicate.md): Mark incidents as duplicates in Rootly to consolidate response efforts via the web UI, Slack, or API, with auto-cancellation support and parent linking. - [Marking Incidents as Duplicate via Web Interface](https://docs.rootly.com/incidents/incident-operations/web-marking-as-duplicate.md): Learn how to mark incidents as duplicates in the Rootly web interface, including selecting the primary incident and optional auto-cancellation. - [Marking Incidents as Duplicate via Slack](https://docs.rootly.com/incidents/incident-operations/slack-marking-as-duplicate.md): Mark incidents as duplicates from Slack incident channels using the /rootly dup command to consolidate response efforts and avoid scattered chats. - [Creating Sub-Incidents](https://docs.rootly.com/incidents/incident-operations/creating-sub-incident.md): Learn how to split large incidents into sub-incidents for better organization across multiple teams, with workflow automation support. - [Creating Sub-Incidents via Web Interface](https://docs.rootly.com/incidents/incident-operations/web-creating-a-sub-incident.md): Create sub-incidents through the Rootly web interface using the incident menu and creation form to track related child issues under a parent incident. - [Creating Sub-Incidents via Slack](https://docs.rootly.com/incidents/incident-operations/slack-creating-a-sub-incident.md): Create sub-incidents directly from Slack incident channels using the /rootly sub command and interactive dialog to track related issues separately. - [Scheduling Maintenance Incidents](https://docs.rootly.com/incidents/incident-operations/scheduling-a-maintenance-incident.md): Learn how to schedule and manage maintenance incidents for planned service interruptions, including Slack channel creation and status page integration. ## Retrospectives - [Retrospectives](https://docs.rootly.com/retrospectives/retrospectives.md): Right-size retrospective processes by severity, type, or team; auto-draft with Rootly AI; and drive follow-ups through configurable step-by-step processes. ### Collaborative Editor - [Collaborative retrospective editor overview](https://docs.rootly.com/collaborative-retrospectives/overview.md): Explore the Rootly collaborative retrospective editor with real-time co-authoring, dynamic data blocks, Liquid variables, and inline action item tracking. - [Using the Retrospective Editor](https://docs.rootly.com/collaborative-retrospectives/using-the-editor.md): Use the collaborative retrospective editor's formatting tools, slash commands, data blocks, and templates for post-incident reviews. - [Real-Time Collaboration](https://docs.rootly.com/collaborative-retrospectives/real-time-collaboration.md): Work together on retrospectives with real-time editing, collaborative cursors, presence indicators, inline comments, and live co-authoring across teams. - [Liquid Variables in Retrospectives](https://docs.rootly.com/collaborative-retrospectives/liquid-variables.md): Use Liquid templating in retrospective documents to dynamically populate incident data, custom fields, action items, and timeline events. - [Exporting Retrospectives](https://docs.rootly.com/collaborative-retrospectives/exporting-retrospectives.md): Export retrospective content to external documentation providers like Google Docs, Confluence, Notion, SharePoint, Quip, Coda, and other knowledge bases. ### AI in Retrospectives - [Rootly AI in Retrospectives](https://docs.rootly.com/ai/ai-in-retrospectives/overview.md): Rootly AI auto-generates retrospective sections — summary, impact, root cause — from incident data, Slack channels, and bridge-call transcripts. - [Building AI Templates](https://docs.rootly.com/ai/ai-in-retrospectives/building-ai-templates.md): Add Rootly AI blocks to a retrospective template, steer them with custom instructions, and preview the output against a past incident before rollout. - [Insert and Edit AI Blocks in Retrospectives](https://docs.rootly.com/ai/ai-in-retrospectives/using-ai-blocks.md): Insert Rootly AI blocks in a retrospective, watch them generate, inspect their sources, and edit, regenerate, convert, or rate the output. ### Process Configuration - [Configuring Retrospective Processes](https://docs.rootly.com/retrospectives/configuring-retrospective-processes.md): Configure retrospective processes and preferences in Rootly to right-size follow-up work based on severity, incident type, team ownership, or custom conditions. - [Configuring Process Steps](https://docs.rootly.com/retrospectives/configuring-process-steps.md): Customize retrospective process steps in Rootly with titles, requirements, role assignments, due dates, and reminder configurations to standardize follow-ups. - [Configuring Templates](https://docs.rootly.com/retrospectives/configuring-templates.md): Create and manage retrospective templates in Rootly with dynamic content blocks and Liquid to pre-fill documents and apply the right template per incident. ## Status Pages - [Status pages for internal and customer updates](https://docs.rootly.com/configuration/status-pages.md): Create and manage status pages to communicate service health and incident information to internal stakeholders and external customers in real-time. - [Creating a Status Page](https://docs.rootly.com/configuration/creating-a-status-page.md): Set up and customize public status pages in Rootly to communicate service health, incident updates, and scheduled maintenance to your customers. - [Custom Domain Names for Status Pages](https://docs.rootly.com/configuration/custom-domain-names-for-status-pages.md): Configure custom domain names for your public status pages to maintain brand consistency and provide a seamless customer experience. - [Status Page Authentication Methods](https://docs.rootly.com/configuration/status-page-authentication-methods.md): Configure authentication for public Rootly status pages to control viewer access using password protection or SAML-based single sign-on. - [Publishing Incidents to Status Pages](https://docs.rootly.com/configuration/publishing-incidents.md): Publish incidents to your status pages from Slack or the Rootly web UI to keep customers and internal teams updated as an incident progresses. - [Status Page Public API](https://docs.rootly.com/configuration/status-page-public-api.md): Access status and incident information programmatically through public JSON API endpoints exposed on your status page custom domain. ## Rootly AI - [Rootly AI for Your Entire Incident Lifecycle](https://docs.rootly.com/ai/ai.md): How Rootly AI supports every stage of incident response — detection, triage, mitigation, resolution, and retrospectives — across Slack, web, and mobile. - [Using Rootly AI in Slack](https://docs.rootly.com/ai/rootly-in-slack/using-rootly-in-slack.md): How to talk to Rootly AI in Slack — where to invoke it, what to expect while it works, how clarification cards work, and how write actions execute. - [Rootly AI in Web](https://docs.rootly.com/ai/ask-rootly-ai.md): Use the Rootly AI chat panel in the web app to ask questions about an incident, get caught up, and draft updates — all from the incident page. - [Rootly AI on Mobile](https://docs.rootly.com/ai/rootly-ai-on-mobile.md): Rootly AI on the Rootly mobile app — get a live Incident Summary and ask Rootly AI questions or take actions from your phone while on-call. - [Rootly AI Meeting Scribe](https://docs.rootly.com/ai/meeting-scribe.md): Rootly AI records, transcribes, and summarizes incident bridge calls across Zoom, Meet, Webex, Teams, and GoToMeeting — with built-in privacy protections. - [Rootly MCP Server for AI assistants and IDEs](https://docs.rootly.com/integrations/mcp-server.md): Connect AI assistants and IDEs to Rootly using the Model Context Protocol, with Code Mode, OAuth2, hosted, and self-hosted deployment options. ### AI During Incidents - [Generated Incident Title](https://docs.rootly.com/ai/generated-incident-title.md): Rootly AI generates concise, descriptive incident titles from the incident's current context — and improves them as more details become available. - [Incident Summarization](https://docs.rootly.com/ai/incident-summarization.md): Generate Rootly AI summaries of the current incident that capture the problem, impact, resolution steps, and key participants in a single coherent overview. - [Incident Catchup](https://docs.rootly.com/ai/incident-catchup.md): Quickly get up to speed on an ongoing incident with a private Rootly AI summary of timeline events, status, and key decisions, delivered directly in Slack. - [Mitigation & Resolution Summary](https://docs.rootly.com/ai/mitigation-and-resolution-summary.md): Rootly AI generates concise summaries explaining how an incident was mitigated, resolved, cancelled, or closed — for use in retrospectives and timelines. - [Rootly AI Editor](https://docs.rootly.com/ai/rootly-ai-editor.md): Use the Rootly AI Editor to improve writing in any Rootly text field — fix spelling and grammar, adjust length, or simplify language. ### AI in Slack - [Rootly AI in Slack](https://docs.rootly.com/ai/rootly-in-slack/overview.md): Rootly AI works inside your incident channels — catch up on incidents, look up information in real-time, and take actions without leaving Slack. - [Getting Started](https://docs.rootly.com/ai/rootly-in-slack/getting-started.md): Enable Rootly AI in Slack for your team, invite the bot to your incident channels, and walk through your first interaction during a real incident. - [What to Use Rootly AI for](https://docs.rootly.com/ai/rootly-in-slack/what-to-use-rootly-for.md): What Rootly AI in Slack can do to help responders during an ongoing incident — catch up, look up context, take actions — with concrete example prompts. - [Troubleshooting](https://docs.rootly.com/ai/rootly-in-slack/troubleshooting.md): How to diagnose common issues with Rootly AI in Slack — missing responses, permission errors, and unexpected behavior — plus current usage limits. ### AI Connectors - [Connectors](https://docs.rootly.com/ai/connectors/overview.md): Connect your observability, code, docs, and cloud tools as data sources that Rootly AI can query during incident investigations. - [Atlassian (Jira + Confluence)](https://docs.rootly.com/ai/connectors/atlassian.md): Connect Rootly AI to Atlassian — Jira issues, Confluence pages, and project context — via a single one-click authorization. - [AWS](https://docs.rootly.com/ai/connectors/aws.md): Give Rootly AI read-only access to your AWS account via an IAM Role — with fine-grained service and region scoping and optional EKS support. - [Braintrust](https://docs.rootly.com/ai/connectors/braintrust.md): Connect Rootly AI to Braintrust — AI observability, logs, and evals — via a single one-click authorization. - [Cloudflare](https://docs.rootly.com/ai/connectors/cloudflare.md): Connect Rootly AI to Cloudflare — DNS, Workers, Zero Trust, audit logs, Radar, CASB, Logpush, and more — via a single one-click authorization. - [Custom (Any OAuth MCP)](https://docs.rootly.com/ai/connectors/custom.md): Bring your own OAuth-based MCP server as a Rootly AI connector — with an allowlist of tools it can call during investigations. - [Dash0 AI Connector](https://docs.rootly.com/ai/connectors/dash0.md): Connect Rootly AI to Dash0 — traces, logs, metrics, services, dashboards, and alerts — with a region selection and one OAuth authorization. - [Datadog AI Connector](https://docs.rootly.com/ai/connectors/datadog.md): Connect Rootly AI to Datadog — logs, metrics, traces, dashboards, monitors, and incidents — with an authorization flow. - [GitHub AI Connector](https://docs.rootly.com/ai/connectors/github.md): Connect Rootly AI to GitHub — deploys, code diffs, and file ownership — via a single one-click authorization. - [Grafana Cloud](https://docs.rootly.com/ai/connectors/grafana-cloud.md): Connect Rootly AI to your Grafana Cloud stack — metrics, logs, dashboards, and alerts — with a single-field setup. - [Grafana Managed](https://docs.rootly.com/ai/connectors/grafana-managed.md): Connect Rootly AI to your self-hosted Grafana so it can query metrics, logs, dashboards, and alerts during investigations. - [Honeycomb AI Connector](https://docs.rootly.com/ai/connectors/honeycomb.md): Connect Rootly AI to Honeycomb — traces, metrics, logs, BubbleUp investigations, Triggers, and SLOs — with a region selection and one OAuth authorization. - [LaunchDarkly](https://docs.rootly.com/ai/connectors/launchdarkly.md): Connect Rootly AI to LaunchDarkly — flags, targeting, and audit logs — via a single one-click authorization. - [Linear AI Connector](https://docs.rootly.com/ai/connectors/linear.md): Connect Rootly AI to Linear — issues, projects, and roadmaps — via a single one-click authorization. - [New Relic AI Connector](https://docs.rootly.com/ai/connectors/new-relic.md): Connect Rootly AI to New Relic — entities, NRQL queries, alerts, incidents, logs, and golden metrics — with a user API key. - [Notion AI Connector](https://docs.rootly.com/ai/connectors/notion.md): Connect Rootly AI to Notion — docs, runbooks, and databases — via a single one-click authorization. - [Semaphore](https://docs.rootly.com/ai/connectors/semaphore.md): Connect Rootly AI to Semaphore CI/CD — pipelines, job logs, and workflow context during incident investigations. - [Sentry AI Connector](https://docs.rootly.com/ai/connectors/sentry.md): Connect Rootly AI to Sentry — errors, stack traces, and user-impact context — via a single one-click authorization. ### AI Privacy & Security - [Data Privacy for AI Summaries & Web Copilot](https://docs.rootly.com/ai/data-privacy-for-ai.md): Data privacy for Rootly's classic AI features—generated titles, summaries, catchup, AI Editor, and Web Copilot—covering OpenAI handling and opt-out. - [Data Privacy for Rootly AI](https://docs.rootly.com/ai/data-privacy-for-rootly-ai.md): How Rootly AI—the AI agent in Slack, web, and mobile—handles data access, encryption, RBAC, audit logs, retention, BYOK, and PII redaction. - [Slack Scope Updates](https://docs.rootly.com/ai/slack-scope-updates.md): Configure enhanced Slack permissions to enable Rootly AI features with customizable privacy levels for incident channel message ingestion. ## Workflows & Automation - [Rootly workflows for incident response automation](https://docs.rootly.com/workflows/workflows.md): Learn how Rootly workflows automate incident response through trigger events, conditions, actions, execution phases, and scheduling for end-to-end automation. ### Building Workflows - [Workflow Conditions](https://docs.rootly.com/workflows/conditions.md): How Rootly workflows evaluate run conditions — all-of / any-of / none-of join operators, per-field operators, recipes, and troubleshooting misfires. - [Workflow Actions Reference](https://docs.rootly.com/workflows/actions-reference.md): Reference for all 152 Rootly workflow action types, grouped by category: Slack, Google Chat, Jira, on-call, AI, and incident operations. ### Workflow Types - [Workflow Types](https://docs.rootly.com/workflows/workflow-types.md): Understand the six workflow types (incident, post-mortem, action item, alert, pulse, and standalone) and the trigger events available for each. - [Incident Workflows](https://docs.rootly.com/workflows/incident-workflows.md): Automate incident response in Rootly by triggering workflows on incident events like creation, status changes, severity updates, and field updates. - [Retrospective Workflows](https://docs.rootly.com/workflows/retrospective-workflows.md): Automate retrospective tasks in Rootly like doc publishing, ticket creation, and notifications triggered by retrospective lifecycle events and milestones. - [Action Item Workflows](https://docs.rootly.com/workflows/action-item-workflows.md): Automate follow-up and remediation work by triggering workflows on action item changes—keeping tickets, owners, and notifications in sync across systems. - [Alert Workflows](https://docs.rootly.com/workflows/alert-workflows.md): Automate responses to incoming alerts by triggering workflows that declare incidents, page responders, create tickets, and notify teams based on alert data. - [Pulse Workflows](https://docs.rootly.com/workflows/pulse-workflows.md): Automate responses to code change events from CI/CD systems in Rootly to pre-declare incidents, notify teams, track deployments, and capture rollback context. - [Standalone Workflows](https://docs.rootly.com/workflows/standalone-workflows.md): Create manual Slack command-triggered workflows in Rootly for ad-hoc tasks like emailing dashboards, making calls, querying repos, and running scripts. ### Running & Managing - [Manually Running Workflows](https://docs.rootly.com/workflows/manually-running-workflows.md): Trigger Rootly workflows manually through Slack commands, Slack modals, and the web interface for on-demand automation, ad-hoc tasks, and one-off operations. - [Wait and Repeat](https://docs.rootly.com/workflows/workflow-scheduling.md): Delay workflow execution, repeat actions on a schedule, and set stop conditions in Rootly that control when a repeating workflow ends or pauses automatically. - [Locking Workflows](https://docs.rootly.com/workflows/locking-workflows.md): Lock a workflow in Rootly to restrict edit access to Admins and Owners, protecting critical automation from accidental or unauthorized changes. ### Playbooks - [Incident response playbooks overview](https://docs.rootly.com/configuration/playbooks.md): Create and manage response playbooks that automatically attach to incidents based on conditions like severity, service, or team to guide resolution efforts. - [Example Usage With Incidents](https://docs.rootly.com/configuration/example-usage-with-incidents.md): Learn how playbooks automatically attach relevant action items and response procedures when incident types are assigned during incident response. ### Pulses - [Pulses](https://docs.rootly.com/configuration/pulses.md): Track deploys, config changes, and other operational events as pulses — silent context signals that surface in triage to correlate breaks with changes. - [Kubernetes Configuration](https://docs.rootly.com/configuration/kubernetes.md): Configure Kubernetes integration to monitor cluster resources and automatically generate pulses from pod, deployment, and service changes. - [Heroku Configuration](https://docs.rootly.com/configuration/heroku.md): Configure Heroku integration to automatically capture build events and release deployments as contextual pulses for incident correlation. - [GitLab Configuration](https://docs.rootly.com/configuration/gitlab.md): Configure GitLab integration to automatically track repository pushes and merge requests as contextual pulses for enhanced incident analysis. - [GitHub Configuration](https://docs.rootly.com/configuration/github.md): Configure GitHub integration to automatically capture push events and pull request merges as contextual pulses during incident triage and analysis. ### Liquid Templating - [Liquid templating in Rootly workflows](https://docs.rootly.com/liquid/liquid.md): Learn how to use the Liquid templating engine in Rootly workflows to dynamically manipulate data, format content, and create powerful automation expressions. - [Available Liquid Filters](https://docs.rootly.com/liquid/filters.md): Comprehensive reference of built-in and custom Liquid filters for data manipulation, formatting, and string processing in Rootly workflows. - [Secrets](https://docs.rootly.com/liquid/secrets.md): Learn how to access stored secrets in Liquid templates using the secrets variable for secure credential management in Rootly workflows and integrations. - [Timezones](https://docs.rootly.com/liquid/timezones.md): Complete list of timezone identifiers for use with the in_time_zone Liquid filter in Rootly workflows to convert dates and times across global teams. ### Liquid Variables - [Incident Variables](https://docs.rootly.com/liquid/incident-variables.md): Complete reference of all available incident variables for Liquid templating in workflows, Slack formatting, and postmortem templates. - [Alert Variables](https://docs.rootly.com/liquid/alert-variables.md): Reference for alert variables available in Liquid templates used by alert workflows, message templates, and other Liquid-rendered surfaces. - [Action Item Variables](https://docs.rootly.com/liquid/action-item-variables.md): Reference guide for action item variables available in Liquid templates for Rootly Genius workflows, integration formatting, and action item automation. - [Pulse Variables](https://docs.rootly.com/liquid/pulse-variables.md): Reference for pulse variables available in Liquid templates for processing health check, deploy, and monitoring data in Rootly workflows and integrations. - [Team Variables](https://docs.rootly.com/liquid/team-variables.md): Reference guide for team variables available in Liquid templates including team metrics, member data, on-call assignments, and integration mappings in Rootly. - [Task Output Variables](https://docs.rootly.com/liquid/task-output-variables.md): Reference previous workflow action outputs using Liquid template variables to chain Rootly actions together, pass data between steps, and build pipelines. ## Analytics - [Analytics](https://docs.rootly.com/metrics/overview.md): Understand incident performance, on-call workload, and reliability trends with Rootly's default dashboards, custom panels, and dashboard sharing. - [Default Metrics](https://docs.rootly.com/metrics/default-metrics.md): Reference for every panel in Rootly's default Incident Response, Workload, and On-Call dashboards — the collection, operation, and metric key behind each. ### Dashboards - [Managing Dashboards](https://docs.rootly.com/metrics/managing-dashboards.md): Create, share, duplicate, and set default dashboards in Rootly. Ownership types, permission levels, public link behavior, exports, auto-refresh, and deletion. - [Customizing Dashboards](https://docs.rootly.com/metrics/customized-dashboards.md): Build custom metric dashboards with panel types, filters, groupings, multiple datasets, and export options for incident analytics. ## Configuration - [Incident properties and configuration overview](https://docs.rootly.com/configuration/configuration.md): Configure incident properties, custom fields, and settings to characterize incidents, trigger workflows, and filter metrics across your organization. ### Incident Structure - [Incident Kind](https://docs.rootly.com/configuration/incident-kind.md): The Incident Kind property is the immutable classification that decides how an incident behaves, which workflows fire, and status page eligibility. - [Incident Status](https://docs.rootly.com/configuration/incident-status.md): The Incident Status lifecycle — Triage, Started, Mitigated, Resolved, Closed, Cancelled — with transition rules, timestamps, and sub-statuses. - [Custom Statuses](https://docs.rootly.com/configuration/custom-statuses.md): Define custom incident lifecycle stages beyond the default Active, Mitigated, and Resolved statuses to match your organization's response processes. - [Severities](https://docs.rootly.com/configuration/severities.md): Configure incident severity levels, calibrate a severity matrix for your team, and use severities to drive workflows, escalations, and status pages. - [Incident Types](https://docs.rootly.com/configuration/incident-types.md): Configure custom incident type categories to classify incidents by your own taxonomy — customizable, and available in workflow conditions and metrics. - [Incident Causes](https://docs.rootly.com/configuration/incident-causes.md): Track root causes across incidents to surface systemic patterns, prioritize reliability work, and give retrospectives a shared, customizable vocabulary. - [Environments](https://docs.rootly.com/configuration/environments.md): Define environment values (Production, Staging, Development) to distinguish incident scope, drive workflow conditions, and segment metrics in Rootly. ### Forms & Fields - [Forms and custom fields overview](https://docs.rootly.com/configuration/forms-and-fields.md): Configure incident data collection forms and custom fields in Rootly to control when and how information is captured during the incident response lifecycle. - [Built-In Fields](https://docs.rootly.com/configuration/built-in-fields.md): The pre-configured incident properties Rootly ships with — Severity, Environments, Services, Teams, Incident Types — and how to enable or rename them. - [Custom incident fields configuration](https://docs.rootly.com/configuration/custom-fields.md): Create organization-specific incident fields with custom data types, validation rules, and integration mappings to meet unique incident management requirements. - [Default Forms](https://docs.rootly.com/configuration/built-in-forms.md): Configure Rootly's built-in forms that guide users through incident creation, updates, resolution, maintenance, and post-incident processes. - [Custom Forms](https://docs.rootly.com/configuration/custom-forms.md): Build tailored forms with specific field combinations to collect targeted incident data at different stages of the response lifecycle. - [Dynamic Forms](https://docs.rootly.com/configuration/dynamic-forms.md): Configure form variations that adapt based on incident properties like type, team, or severity to collect contextually relevant information. ### Services & Functionalities - [Services](https://docs.rootly.com/configuration/services.md): Configure services to identify impacted components during incidents, manage responders, and integrate with status pages and external tools. - [Functionalities](https://docs.rootly.com/configuration/functionalities.md): Configure functionality categories in Rootly to identify impacted product features during incidents, route to appropriate teams, and surface ownership context. ### Catalog - [Catalogs](https://docs.rootly.com/catalogs.md): Define and manage the entities that matter to your business, like services, teams, and regions, as a structured source of truth for incident response. - [Managing Custom Catalogs](https://docs.rootly.com/managing-custom-catalogs.md): Create custom catalogs, define properties, link catalogs together, and add entities to represent your organization's unique business concepts. - [Catalog Sync CLI](https://docs.rootly.com/catalog-sync.md): Use the rootly-catalog-sync CLI to keep services, teams, and metadata in your Rootly Catalog continuously synced from GitHub, Backstage, APIs, and more. - [Checklists](https://docs.rootly.com/checklists.md): Create checklists to verify that every entity in your catalog has the required properties, and run audits to track completeness across your organization. ### Webhooks - [Outgoing Webhooks](https://docs.rootly.com/configuration/webhooks.md): Send real-time event notifications from Rootly to any external HTTP endpoint as incidents, alerts, pulses, and workflows progress through their lifecycles. - [Event Payloads](https://docs.rootly.com/configuration/event-payloads.md): Reference documentation for webhook event payload structures used in Rootly integrations and custom automations, including incident, alert, and pulse events. ### Edge Connectors - [Rootly Edge Connector for on-premises systems](https://docs.rootly.com/edge-connectors.md): Securely integrate Rootly with internal systems that cannot accept inbound internet connections using outbound-only polling through the Edge Connector. - [Installation & Deployment](https://docs.rootly.com/edge-connectors-installation.md): Install and deploy the Rootly Edge Connector in your environment using Docker or supported orchestrators to securely poll Rootly without inbound connections. - [Action Configuration](https://docs.rootly.com/edge-connectors-actions.md): Configure script and HTTP actions for Rootly Edge Connectors to automate responses to events from internal systems behind your firewall using outbound polling. - [Template Syntax](https://docs.rootly.com/edge-connectors-templates.md): Use Liquid templates in Rootly Edge Connectors to dynamically insert event data, parameters, and secrets into HTTP and script actions during execution. - [Event Examples](https://docs.rootly.com/edge-connectors-event-examples.md): Real-world examples of event payloads received from Rootly Edge Connectors, showing JSON structures for testing actions, scripts, and Liquid template logic. ## Integrations ### Overview - [Rootly integrations with third-party tools](https://docs.rootly.com/integrations/overview.md): Integrations connect Rootly with third-party services and internal tools to extend incident response, automation, and collaboration. - [Integrations Catalog](https://docs.rootly.com/integrations/catalog.md): Browse every Rootly integration. Find the tools you need for alerting, communication, deployment tracking, monitoring, and ticketing. - [IP Allowlist](https://docs.rootly.com/integrations/ip-whitelist.md): Allowlist the IP addresses and hostnames needed for traffic between Rootly and your network, in both directions, through firewalls and proxies. - [API](https://docs.rootly.com/integrations/api.md): Generate and manage API keys to programmatically integrate with Rootly's incident management platform, including scopes, rotation, and authentication methods. ### CLI & Developer Tools - [CLI](https://docs.rootly.com/integrations/cli.md): Manage Rootly incidents, alerts, services, teams, on-call schedules, and workflows from your terminal with the official Rootly command-line interface. - [Terminal UI (TUI)](https://docs.rootly.com/integrations/tui.md): View and manage Rootly incidents and alerts from your terminal with the Rootly TUI application, a fast keyboard-driven interface for on-call responders. - [Setup Wizard](https://docs.rootly.com/integrations/rootly-wizard.md): Go from empty workspace to incident-ready in minutes: the Rootly Setup Wizard configures teams, on-call, alerting, and a status page from your terminal. ### SDKs - [TypeScript SDK](https://docs.rootly.com/integrations/typescript-sdk.md): Type-safe TypeScript client for the Rootly API, powered by openapi-typescript and openapi-fetch, for incident, alert, and on-call automation in Node.js. - [Rust SDK](https://docs.rootly.com/integrations/rust-sdk.md): Strongly-typed Rust client for the Rootly API, generated from the OpenAPI spec with full async/await support, builder patterns, and complete API coverage. - [Python SDK](https://docs.rootly.com/integrations/python-sdk.md): Auto-generated Python client for the Rootly API with sync and async support, type-safe models, and full coverage of incident, alert, and on-call endpoints. - [Swift SDK](https://docs.rootly.com/integrations/swift-sdk.md): Swift client for the Rootly API, auto-generated with Apple's Swift OpenAPI Generator for incident, alert, and on-call automation on iOS and macOS. ### Collaboration - [Google Chat](https://docs.rootly.com/integrations/google-chat/overview.md): Connect Google Chat to Rootly to create incident spaces, run slash commands, and drive incident workflows from chat. - [Mattermost](https://docs.rootly.com/integrations/mattermost.md): Connect Mattermost to Rootly so responders can declare, manage, and coordinate incidents directly from Mattermost with channels and slash commands. - [Microsoft Teams](https://docs.rootly.com/integrations/microsoft-teams.md): Connect Microsoft Teams to Rootly to create incident channels, run workflow actions, and start Teams meetings from incidents. - [Slack](https://docs.rootly.com/integrations/slack/slack.md): Connect Slack to Rootly to declare incidents from chat, run a dedicated incident channel, and drive response with commands and workflows. ### Alerting - [Generic Webhook Alert Source](https://docs.rootly.com/integrations/generic-webhook-alert-source/generic-webhook-alert-source.md): Ingest alerts from any monitoring, observability, or security tool into Rootly via webhook — works with any system that can POST JSON to a URL. - [Opsgenie](https://docs.rootly.com/integrations/opsgenie.md): Connect Opsgenie to Rootly to import services, sync alerts and incidents, automate response workflows, and gradually migrate from Opsgenie to Rootly On-Call. - [PagerTree](https://docs.rootly.com/integrations/pager-tree.md): Connect PagerTree to Rootly for inbound alert webhooks, outbound paging, linked incident workflows, and automatic alert synchronization. - [PagerDuty](https://docs.rootly.com/integrations/pagerduty/pagerduty.md): Connect PagerDuty to Rootly to page on-call responders, sync incidents in both directions, and import teams and schedules. - [VictorOps (Splunk On-Call)](https://docs.rootly.com/integrations/victor-ops.md): Connect VictorOps (Splunk On-Call) to Rootly for API-based escalation, optional inbound webhooks, linked incident workflows, and Slack-based paging. ### Observability - [AWS SNS](https://docs.rootly.com/integrations/aws-sns.md): Receive alerts from Amazon SNS topics in Rootly using a versioned payload schema to create, route, deduplicate, and automatically resolve alerts. - [Checkly](https://docs.rootly.com/integrations/checkly.md): Connect Checkly to Rootly to turn synthetic check failures and API monitoring alerts into routed, actionable incidents and on-call pages. - [Chronosphere](https://docs.rootly.com/integrations/chronosphere.md): Connect Chronosphere to Rootly to turn observability alerts into actionable incidents, paging on-call responders directly from monitor notifications. - [Datadog](https://docs.rootly.com/integrations/datadog/datadog.md): Connect Datadog to Rootly to ingest monitor alerts and capture notebooks, graphs and dashboards during incidents. - [Dynatrace](https://docs.rootly.com/integrations/dynatrace.md): Set up Dynatrace as an alert source in Rootly to route problem notifications, configure urgency rules, page on-call teams, and auto-resolve alerts on recovery. - [Google Cloud Monitoring](https://docs.rootly.com/integrations/google-cloud-monitoring.md): Forward alerts from Google Cloud Monitoring to Rootly for escalation, Slack routing, on-call paging, and automated incident response across GCP workloads. - [Grafana](https://docs.rootly.com/integrations/grafana/grafana.md): Connect Grafana to Rootly to ingest alert events and capture dashboard and panel snapshots during incidents through Genius workflows. - [Honeycomb Integration](https://docs.rootly.com/integrations/honeycomb.md): Receive Honeycomb alerts in Rootly to trigger incidents, notify Slack, page your on-call team, and automatically resolve alerts when triggers clear. - [New Relic](https://docs.rootly.com/integrations/new-relic.md): Connect New Relic to Rootly to ingest alert events and capture metric and chart snapshots during incidents through Genius workflows. - [Nobl9](https://docs.rootly.com/integrations/nobl9.md): Receive alerts in Rootly when SLO error budgets are breached in Nobl9, with routing to on-call teams, Slack channels, and incident creation workflows. - [Prometheus Alertmanager](https://docs.rootly.com/integrations/alertmanager.md): Connect Prometheus Alertmanager to Rootly to ingest firing alerts, automatically resolve them when restored, and page on-call escalation targets. - [Rollbar](https://docs.rootly.com/integrations/rollbar.md): Connect Rollbar to Rootly to ingest error monitoring events as alerts and automate incident creation from application errors, regressions, and exceptions. - [Route AWS CloudWatch alarms into Rootly via SNS](https://docs.rootly.com/integrations/aws-cloudwatch.md): Receive alerts from AWS CloudWatch in Rootly to trigger incidents, route notifications to on-call teams, and automatically resolve alerts when alarms recover. - [Sentry](https://docs.rootly.com/integrations/sentry/sentry.md): Connect Sentry to Rootly to ingest issue and metric alerts, and turn them into incidents or on-call pages with alert workflows. - [Splunk](https://docs.rootly.com/integrations/splunk.md): Connect Splunk to Rootly using the official Rootly Splunk app to forward saved search alerts, trigger on-call paging, and automate incident creation. ### Documentation - [Confluence](https://docs.rootly.com/integrations/confluence/confluence.md): Connect Confluence to Rootly to automatically create and update incident retrospective pages from templates. - [Dropbox Paper](https://docs.rootly.com/integrations/dropbox-paper.md): Connect Dropbox Paper to Rootly to automatically create and update retrospective documents from incidents using Liquid templates. - [Google Docs](https://docs.rootly.com/integrations/google-docs/overview.md): Connect Google Docs to Rootly to automatically create incident retrospective documents from templates using Liquid variables. - [Notion](https://docs.rootly.com/integrations/notion/overview.md): Connect Notion to Rootly to automatically create and update incident retrospective pages in your Notion workspace. - [Quip](https://docs.rootly.com/integrations/quip.md): Connect Quip to Rootly to automatically create and update retrospective documents from incidents using Genius workflows with templates and folder routing. - [SharePoint](https://docs.rootly.com/integrations/sharepoint.md): Connect Microsoft SharePoint to Rootly to automatically create and update Word documents in SharePoint sites during incidents for retrospectives and reports. ### Video Conferencing - [Google Meet](https://docs.rootly.com/integrations/google-meet/google-meet.md): Connect Google Meet to Rootly to create an incident meeting automatically and capture transcripts and summaries with Meeting Scribe. - [Webex](https://docs.rootly.com/integrations/webex/webex.md): Connect Webex to Rootly to automatically create a meeting bridge for each incident and post the link into the incident's Slack channel. - [Zoom](https://docs.rootly.com/integrations/zoom/zoom.md): Connect Zoom to Rootly to create an incident meeting automatically and capture transcripts and summaries with Meeting Scribe. - [GoToMeeting](https://docs.rootly.com/integrations/go-to-meeting.md): Automatically create GoToMeeting sessions for Rootly incidents and share meeting links in Slack channels for quick responder collaboration during outages. ### Development & CI/CD - [AWS Elastic Beanstalk](https://docs.rootly.com/integrations/aws-elastic-beanstalk.md): Connect AWS Elastic Beanstalk to Rootly to log deployment pulses automatically during every application deploy using the Rootly CLI and .ebextensions hooks. - [GitHub](https://docs.rootly.com/integrations/github/github.md): Track deployments, create and update issues, fetch commits, and enrich PR links with automatic status tracking for incident management. - [GitLab Integration](https://docs.rootly.com/integrations/gitlab.md): Connect GitLab to Rootly to track deployments and merge requests as pulses, create issues from incidents, and enrich GitLab links in Slack. - [Heroku Integration](https://docs.rootly.com/integrations/heroku.md): Track Heroku builds and releases as pulses in Rootly, and run commands on dynos directly from incident workflows for deployment context and rollback. - [Kubernetes Integration](https://docs.rootly.com/integrations/kubernetes.md): Connect Kubernetes to Rootly to monitor cluster events across pods, deployments, and services, and surface them as pulses during incidents. ### Communication - [Email](https://docs.rootly.com/integrations/email.md): Create incidents by sending emails to your team's Rootly inbound alias, and send templated email notifications from workflows with Liquid and CC support. - [SendGrid](https://docs.rootly.com/integrations/sendgrid.md): Route Rootly workflow emails through your own SendGrid account to send from your company domain with full delivery visibility, tracking, and authentication. - [SMTP](https://docs.rootly.com/integrations/smtp.md): Route Rootly workflow emails through your own SMTP server to send from your company domain with full control over delivery, authentication, and headers. - [Statuspage.io](https://docs.rootly.com/integrations/status-page-io.md): Connect Atlassian Statuspage.io to Rootly to import status pages and templates, and publish incident updates to your customer-facing status page. - [Twitter / X](https://docs.rootly.com/integrations/twitter.md): Post incident updates to Twitter directly from Rootly workflows or the incident timeline to keep customers and stakeholders informed in real time. ### Data & Analytics - [Airtable](https://docs.rootly.com/integrations/airtable.md): Automatically create and update Airtable records from Rootly incidents using workflow actions to track incidents, follow-ups, and metrics in your bases. - [AWS EventBridge](https://docs.rootly.com/integrations/aws-eventbridge.md): Stream incident and alert lifecycle events from Rootly to AWS EventBridge for real-time event-driven integrations with Lambda and Step Functions. - [Coda](https://docs.rootly.com/integrations/coda/coda.md): Connect Coda to Rootly to automate incident retrospectives with pre-built templates, Liquid variables, and automatic timeline and action item generation. - [Fivetran](https://docs.rootly.com/integrations/fivetran.md): Sync Rootly incident, alert, and metrics data to your data warehouse via Fivetran for custom analytics, BI dashboards, and long-term reliability reporting. - [Looker](https://docs.rootly.com/integrations/looker.md): Capture and share Looker dashboard snapshots directly in Rootly incident workflows and Slack channels to give responders fast access to business context. ### AI & Automation - [Anthropic](https://docs.rootly.com/integrations/anthropic.md): Connect your Anthropic account to Rootly to power AI-assisted incident workflows using Claude with your organization's own API key and data agreements. - [Azure OpenAI](https://docs.rootly.com/integrations/azure-openai.md): Connect Rootly to Azure-hosted OpenAI deployments for AI-assisted incident workflows under your own compliance and data residency rules. - [Glean](https://docs.rootly.com/integrations/glean.md): Sync Rootly incident data to Glean so your team can search incidents, schedules, alerts, and retrospectives alongside the rest of your company knowledge. - [Google Gemini](https://docs.rootly.com/integrations/google-gemini.md): Connect Rootly to Google Gemini to send prompts to Gemini models from incident and action item workflows for AI-assisted summaries and triage. - [Mistral AI](https://docs.rootly.com/integrations/mistral.md): Connect Rootly to Mistral AI to send prompts to Mistral models from incident and action item workflows for AI-assisted summaries, drafts, and triage. - [OpenAI](https://docs.rootly.com/integrations/openai.md): Connect your OpenAI account to Rootly to power AI-assisted incident workflows using your own API key, data agreements, and regional endpoint. - [Superplane](https://docs.rootly.com/integrations/superplane.md): Connect Rootly with Superplane to trigger automated workflows from incident events, manage incidents programmatically, and orchestrate response automation. - [IBM watsonx](https://docs.rootly.com/integrations/watsonx.md): Connect IBM watsonx.ai to Rootly to power incident summaries, alert summaries, and AI text editing with foundation models in your IBM Cloud region. - [Zapier](https://docs.rootly.com/integrations/zapier.md): Connect Rootly with thousands of apps through Zapier to automate incident workflows without code, including ticketing, notifications, CRM, and reporting. - [Agent Plugins](https://docs.rootly.com/integrations/agent-plugins.md): Bring Rootly incident response, on-call context, and retrospectives into Claude Code and Cursor with curated slash commands and automatic hooks. ### Infrastructure & Security - [Google Directory Sync](https://docs.rootly.com/integrations/google-directory-sync.md): Automatically sync users and groups from Google Workspace to Rootly using the Google Admin Directory API to keep team membership and roles up to date. - [HashiCorp Vault](https://docs.rootly.com/integrations/hashicorp-vault.md): Securely read secrets from HashiCorp Vault and inject them into Rootly workflow actions using Liquid templates with KV v1, KV v2, and namespace support. - [Pulumi](https://docs.rootly.com/integrations/pulumi.md): Manage Rootly resources as infrastructure as code using the official Pulumi provider for Node.js and TypeScript with full support for incident configurations. - [SCIM user provisioning and deprovisioning for Rootly](https://docs.rootly.com/integrations/scim.md): Automate Rootly user provisioning and deprovisioning with SCIM 2.0 from Okta, Microsoft Entra, Google Workspace, Keycloak, and other identity providers. - [SSO](https://docs.rootly.com/integrations/sso.md): Enable single sign-on for Rootly with SAML 2.0 compatible identity providers including Okta, Google, OneLogin, Auth0, Azure AD, JumpCloud, and more. - [Terraform](https://docs.rootly.com/integrations/terraform.md): Manage Rootly resources using infrastructure as code with the official Terraform provider for services, severities, workflows, and more. ### Scheduling - [Google Calendar](https://docs.rootly.com/integrations/google-calendar.md): Connect Google Calendar to Rootly to schedule incident meetings from workflows, and import a calendar as a holiday feed for on-call schedules. - [Outlook](https://docs.rootly.com/integrations/outlook.md): Automatically schedule Microsoft Outlook calendar events from incident workflows — ideal for retrospectives, reviews, and follow-ups. ### HR Systems & PTO - [BambooHR](https://docs.rootly.com/integrations/bamboohr.md): Connect BambooHR to Rootly via iCal to overlay employee time off and company holidays on on-call schedules, surfacing coverage gaps early. - [CharlieHR](https://docs.rootly.com/integrations/charliehr.md): Connect CharlieHR to Rootly to overlay employee time off and vacations on on-call schedule timelines, surfacing coverage gaps before pages fire. - [HiBob](https://docs.rootly.com/integrations/hibob.md): Sync HiBob time off into Rootly via calendar feed to overlay vacations and PTO on on-call schedules and spot coverage gaps before pages fire. - [PeopleHR](https://docs.rootly.com/integrations/peoplehr.md): Connect PeopleHR to Rootly via iCal to overlay employee time off and company holidays on on-call schedules, surfacing coverage gaps early. - [Personio](https://docs.rootly.com/integrations/personio.md): Connect Personio to Rootly via iCal feed to overlay employee time off and PTO on on-call schedule timelines, surfacing coverage gaps in advance. - [Rippling](https://docs.rootly.com/integrations/rippling.md): Sync Rippling time off into Rootly to overlay employee vacations and PTO on on-call schedule timelines, surfacing coverage gaps before pages fire. ### Service Catalog - [Backstage](https://docs.rootly.com/integrations/backstage/installation.md): Integrate Rootly with Spotify's Backstage developer portal to enhance service catalog management, ownership tracking, and incident response visibility. - [Cortex](https://docs.rootly.com/integrations/cortex/overview.md): Connect Cortex to Rootly to sync catalog entities into Rootly services and surface Rootly incident data inside Cortex. - [OpsLevel](https://docs.rootly.com/integrations/opslevel.md): Connect OpsLevel with Rootly to sync your service catalog, so responders see current service ownership and metadata during incidents. ### Issue Tracking - [Asana](https://docs.rootly.com/integrations/asana.md): Connect Asana to Rootly to automatically create and update tasks from incidents and action items in your Asana workspace. - [ClickUp](https://docs.rootly.com/integrations/clickup.md): Connect ClickUp to Rootly to create tasks from incidents and receive ClickUp task events as alerts in your incident response process. - [Freshservice](https://docs.rootly.com/integrations/freshservice.md): Connect Freshservice to Rootly to automatically create and update tickets and tasks from incidents in your IT service management workspace. - [Jira](https://docs.rootly.com/integrations/jira/jira.md): Connect Jira to Rootly to create and update issues from incidents, and sync Jira changes back into Rootly. - [Jira (On-Premise)](https://docs.rootly.com/integrations/jira-on-premise.md): Connect Rootly with your Jira Data Center or on-premise instance using URL, username/password, or Personal Access Token authentication. - [Linear Integration](https://docs.rootly.com/integrations/linear/linear.md): Sync Rootly incidents to Linear issues for seamless issue tracking, follow-up management, and engineering context from incident response to delivery. - [Motion integration for Rootly incidents](https://docs.rootly.com/integrations/motion.md): Sync Rootly incidents and action items to Motion tasks with severity-to-priority mapping, bidirectional links, and Liquid title and description templates. - [ServiceNow](https://docs.rootly.com/integrations/service-now.md): Connect ServiceNow to Rootly for bidirectional incident sync — create and update ServiceNow incidents from workflows, and receive ServiceNow events as alerts. - [Shortcut](https://docs.rootly.com/integrations/shortcut.md): Connect Rootly with Shortcut to automatically create and update stories and tasks from incidents, keeping engineering work and incident follow-up in sync. - [Trello](https://docs.rootly.com/integrations/trello.md): Connect Trello to Rootly to automatically create and update cards from incidents, action items, and follow-up workflows. - [Zendesk](https://docs.rootly.com/integrations/zendesk.md): Connect Rootly with Zendesk to automatically create and update tickets from incidents, and receive Zendesk ticket events as Rootly alerts. ## Administration ### Users - [Manage Users](https://docs.rootly.com/managing-users/managing-users.md): View and manage Rootly organization members, including their contact information, roles, team memberships, and integration linkage statuses across providers. - [Manage User Permissions](https://docs.rootly.com/managing-users/user-permissions.md): Control access in Rootly with team-scoped roles for Incident Response and On-Call, with configurable permission sets and custom role definitions. - [Managing Invitations](https://docs.rootly.com/managing-users/invitations.md): View, resend, and delete pending Rootly invitations from Organization Settings to manage who can join your workspace before they accept their invite. - [Inviting Users](https://docs.rootly.com/managing-users/inviting-users-via-web-ui.md): Invite new users to your Rootly organization through the web UI and assign Incident Response or On-Call roles, team memberships, and permissions. - [Inviting Users via Third-Party Integrations](https://docs.rootly.com/managing-users/inviting-users-via-third-party-integrations.md): Invite users to Rootly directly from supported integrations such as Slack, Microsoft Teams, Opsgenie, PagerDuty, and Splunk On-Call to onboard quickly. ### Teams - [Managing teams in Rootly](https://docs.rootly.com/managing-teams/managing-teams.md): Create and manage teams in Rootly for on-call schedules, alert routing, Slack automation, escalation policies, and third-party imports. - [Viewing Teams](https://docs.rootly.com/managing-teams/viewing-teams.md): View, search, and navigate the teams available in your Rootly organization, including team membership, on-call coverage, and owned services. - [Configuring Teams](https://docs.rootly.com/managing-teams/configuring-teams.md): Create and manage teams in Rootly, including members, ownership, Slack channels, escalation policies, and integration mappings for incident response. - [Importing Teams](https://docs.rootly.com/managing-teams/importing-teams.md): Import team names and structure from connected integrations like PagerDuty, Opsgenie, and Slack to quickly populate your Rootly teams without manual setup. - [Attaching Teams To Incidents](https://docs.rootly.com/managing-teams/attaching-teams-to-incidents.md): Associate teams with incidents to coordinate response, and configure workflows that automatically invite team members to the incident Slack channel. - [Team Status Pages](https://docs.rootly.com/managing-teams/team-status-pages.md): Access each team's private status page in Rootly to view incidents, scheduled maintenance, and service health for that team's owned services and components. - [Teams](https://docs.rootly.com/configuration/teams.md): Configure team attributes in Rootly including Slack channels, user groups, escalation policies, on-call schedules, and imports from PagerDuty or Opsgenie. ### Incident Roles Setup - [Configuring Incident Roles](https://docs.rootly.com/configuration/incident-roles.md): Define and manage incident response roles with clear responsibilities, tasks, and hierarchies to ensure effective team coordination during incidents. - [Team Incident Roles](https://docs.rootly.com/managing-teams/incident-roles.md): Configure Incident Roles in Rootly to automatically assign responsibilities like Incident Commander when teams are attached to incidents during response. ### Security & Compliance - [Security Best Practices](https://docs.rootly.com/configuration/security-best-practices.md): Harden your Rootly tenant — identity and SSO, RBAC and least privilege, API hygiene, audit logging, session controls, and integration hygiene. - [Audit Log for compliance and change tracking](https://docs.rootly.com/configuration/audit-log.md): Track configuration changes, integration updates, and incident actions in Rootly with a filterable audit log and JSON:API export for compliance evidence. ## Resources & Help - [Contacting Support](https://docs.rootly.com/contacting-support.md): How to reach Rootly support: email and status page, what to include in your report, and how to grab a device dump from the mobile app. - [Frequently Asked Questions](https://docs.rootly.com/faq.md): Answers to common questions about Rootly incident management: creating incidents from Slack, on-call schedules, alert deduplication, workflows, and Rootly AI. ### Glossary - [Incident Management Glossary](https://docs.rootly.com/glossary.md): Plain-English definitions of incident management terms — incident commander, escalation policy, alert fatigue, MTTR, SEV levels, runbooks, and more. - [What Is Incident Management?](https://docs.rootly.com/glossary/incident-management.md): Incident management is the practice of detecting, responding to, resolving, and learning from unplanned service disruptions. Lifecycle, roles, and tooling. - [What Is Incident Response?](https://docs.rootly.com/glossary/incident-response.md): Incident response is the active work of handling an incident as it happens—mobilizing responders, investigating, mitigating, and communicating until resolved. - [What Is Incident Triage?](https://docs.rootly.com/glossary/incident-triage.md): Incident triage is the rapid assessment of a new incident—its impact, urgency, and scope—to assign a severity and get the right response started fast. - [What Are SEV Levels? SEV1, SEV2, SEV3 Explained](https://docs.rootly.com/glossary/sev-levels.md): SEV levels (SEV1, SEV2, SEV3...) classify incidents by severity of impact, driving who responds, how fast, and how the incident is communicated. - [What Is an Incident Channel (aka War Room)?](https://docs.rootly.com/glossary/war-room.md): An incident channel—often called a war room—is the dedicated space where responders coordinate a major incident, keeping the investigation in one place. - [What Is Alert Fatigue?](https://docs.rootly.com/glossary/alert-fatigue.md): Alert fatigue is the desensitization that sets in when responders receive too many alerts, causing real problems to be missed. Learn the causes and the fixes. - [What Is a Runbook?](https://docs.rootly.com/glossary/runbook.md): A runbook is a step-by-step operational guide for handling a specific task or failure scenario, written so any qualified responder can follow it under pressure. - [What Is MTTR? Mean Time to Resolution Explained](https://docs.rootly.com/glossary/mttr.md): MTTR (mean time to resolution) is the average time from when an incident starts to when it is fully resolved. Formula, examples, and how to improve it. - [What Is MTTA? Mean Time to Acknowledge Explained](https://docs.rootly.com/glossary/mtta.md): MTTA (mean time to acknowledge) is the average time between an alert firing and a responder acknowledging it. Formula, examples, and how to improve it. - [What Is MTBF? Mean Time Between Failures Explained](https://docs.rootly.com/glossary/mtbf.md): MTBF (mean time between failures) is the average operating time between failures. Formula, examples, and how it relates to MTTR and availability. - [What Is an Error Budget?](https://docs.rootly.com/glossary/error-budget.md): An error budget is the amount of unreliability an SLO allows — 100% minus the SLO target. How to calculate it, track burn rate, and set error budget policies. - [MTTA vs MTTR: What's the Difference?](https://docs.rootly.com/glossary/mtta-vs-mttr.md): MTTA measures how fast a responder acknowledges an alert; MTTR measures how fast the team restores service. Learn the formulas and how they work together. - [SLA vs SLO vs SLI: What's the Difference?](https://docs.rootly.com/glossary/sla-vs-slo-vs-sli.md): An SLI is a measurement, an SLO is your internal target for that measurement, and an SLA is the external contract with consequences. Here's how they stack. - [Incident Severity vs Priority: What's the Difference?](https://docs.rootly.com/glossary/severity-vs-priority.md): Severity measures how bad an incident's impact is; priority determines how urgently your team responds. They usually align — but not always. - [Runbook vs Playbook: What's the Difference?](https://docs.rootly.com/glossary/runbook-vs-playbook.md): A runbook is a step-by-step procedure for one specific technical task; a playbook is a broader strategy for handling a whole class of situations. - [Incident vs Problem: What's the Difference?](https://docs.rootly.com/glossary/incident-vs-problem.md): An incident is an unplanned disruption you fix now; a problem is the underlying cause you investigate to stop recurrence. ITIL treats them separately. - [Retrospective vs Postmortem: What's the Difference?](https://docs.rootly.com/glossary/retrospective-vs-postmortem.md): A postmortem analyzes a specific incident after it ends; a retrospective reviews how a team works over time. In incident management the terms overlap. ### Concepts - [What Is an Incident Commander?](https://docs.rootly.com/concepts/incident-commander.md): An incident commander leads the response to an incident—coordinating people, decisions, and communication. Learn the role, skills, and how to assign one. - [How to Run an Incident Retrospective](https://docs.rootly.com/concepts/incident-retrospective.md): An incident retrospective is a blameless review of what happened, why, and what to change. Learn how to run one step by step and what to include. ### Troubleshooting - [Notification Troubleshooting](https://docs.rootly.com/troubleshooting.md): Fix missed or silent Rootly pages: no sound, Do Not Disturb, battery optimization, calls that don't ring, login, and device-specific issues on iOS and Android. - [Login & SSO Troubleshooting](https://docs.rootly.com/troubleshooting/login.md): Fix Rootly sign-in problems by platform: Android (Chrome / Custom Tabs) vs iOS (Safari), plus managed (Intune) devices, lockouts, and web SSO. - [iOS Notification Troubleshooting](https://docs.rootly.com/troubleshooting/ios.md): Fix silent or missed Rootly pages on iPhone: Critical Alerts, Focus modes, the Ring/Silent switch, Apple Watch mirroring, Low Power Mode, and call audio. - [Android Notification Troubleshooting](https://docs.rootly.com/troubleshooting/android.md): Fix silent, delayed, or missed Rootly pages on Android: Do Not Disturb, battery optimization, Work Profiles, and Samsung, Pixel, OnePlus specifics. - [Phone Call Troubleshooting](https://docs.rootly.com/troubleshooting/calls.md): Fix Rootly phone-call pages: calls that don't ring through Do Not Disturb on iPhone or Android, and call audio that's quiet, garbled, or delayed. ## Overview - [Rootly API overview: authentication and conventions](https://docs.rootly.com/api-reference/overview.md): Learn how to authenticate with the Rootly API using bearer tokens, work with rate limits, pagination, filtering, and JSON:API endpoints. - [OAuth 2.0 & OpenID Connect](https://docs.rootly.com/api-reference/oauth2.md): Authenticate with the Rootly API via OAuth 2.0 and OpenID Connect: browser login for CLIs, third-party app consent flows, and automation tokens. - [Official SDKs](https://docs.rootly.com/api-reference/sdks.md): Official Rootly API client libraries for TypeScript, Rust, Python, Go, Swift, Ruby, Java, and Terraform to automate incident management workflows. - [API Changelog](https://docs.rootly.com/api-reference/changelog.md): Track the latest changes, deprecations, and breaking updates to the Rootly API, including new endpoints, payload changes, and version release notes. ## Open Source - [Open Source at Rootly](https://docs.rootly.com/open-source/overview.md): Rootly's commitment to the open source community, including our public projects, contributions, and the libraries we maintain for the reliability ecosystem. ## API Reference - [Rootly API Overview](https://docs.rootly.com/api-reference/overview.md): Authentication, JSON:API conventions, rate limits, and pagination for the Rootly REST API. Full endpoint reference: https://docs.rootly.com/api-reference/overview