All the context, all the automation, all your tools, all in one platform that helps you resolve issues faster and with less effort.
Incident management with built-in AI to automate your workflows for faster resolutions—directly in Google Chat.
Rootly turned incident response into an operating system that scales: clearer ownership, faster resolution, stronger retros, and less reliance on heroics.
Matthew Duren, VP of Engineering, KnowBe4
The moment an incident starts, Rootly spins up a dedicated Google Chat space, invites responders, and posts a live incident overview card—severity, status, roles, and next steps in one place. No hunting for the right thread. No blank space.
Rootly posts to a shared announcement space so leadership and stakeholders stay current without joining the response. Status changes flow out automatically—the people fixing the problem stay focused on fixing it.
@Rootly in Google Chat and the agent will answer your questions in plain language and takes actions on your behalf, as your user, within your permissions: page someone, change severity or status, manage action items, draft comms, get caught up, generate a full analysis to improve, and so much more.
Rootly AI SRE analyzes your code changes, telemetry, and past incidents to quickly determine what’s wrong and how to fix it.
AI retros with customizable blocks that capture every action, then draft the summary, impact, root cause, and more. All editable, with tasks tracked to done.
One intuitive and powerful platform, from the first alert to the final action item.
Modern on-call that pages the right person, the first time.
A service catalog that makes every incident smarter.
AI that surfaces probable root cause and suggests fixes for you.
Beautiful, automated status pages that keep your customers informed.
Sensitive incidents are always scoped to the people who should see them, and no one else.
Manage incident response as code, the way your team ships everything else.
Connect all your existing alerting sources—and extend further with our Terraform provider, API, or MCP server.
Everything you need to know about Incident Response with Google Chat.
What is Rootly Incident Response?
Rootly enables engineering teams run the entire incident inside Slack, Microsoft Teams, and Google Chat — declaring, assigning roles, coordinating the fix, updating stakeholders, capturing the timeline, and more. Because it's part of one platform, each incident inherits context from on-call, the service catalog, and past incidents, so response starts a step ahead.
Does Rootly work in Slack, Microsoft Teams, and Google Chat?
Yes. The full incident lifecycle runs natively in Google Chat, Slack, and Microsoft Teams—declaration, coordination, comms, AI assistance, and retrospectives—without switching to a separate interface.
What does Rootly's Google Chat integration do?
When an incident starts, Rootly creates a dedicated Google Chat space, invites responders, and posts real-time incident overview cards. Teams can run the incident with slash commands and emoji shortcuts, post automated updates to announcement spaces, and connect on-call alerting — the full incident workflow, inside Google Chat.
How does the integration connect to Google Workspace?
The recommended production setup uses a service account with domain-wide delegation, configured by a Workspace admin — this enables rich incident cards, slash command dialogs, and emoji reactions. A simpler OAuth option is available for quick evaluation.
Can we use Google Chat alongside Slack or Microsoft Teams?
Yes. Rootly supports multiple chat integrations simultaneously, with workflows that route incidents to specific platforms based on conditions — useful for mixed workspaces, migrations, or acquisitions.
What permissions does Rootly need?
The service account requires six Google Chat scopes for creating spaces, managing members, and sending messages. The full scope list is in the installation guide, and setup is controlled by your Workspace admin.
Does the rest of Rootly work with Google Chat incidents?
Yes. Incidents in Google Chat are full Rootly incidents — connected to on-call schedules, catalog context, workflows, status pages, and retrospectives like any other.
.svg)
