> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/automate/connectors/rootly.md).

# Rootly

Connect Rootly to investigate incidents and coordinate response from Agent Mode

Connect Rootly to give Agent Mode incident history and on-call context, then use that context to coordinate and document the response.

This connector is for Agent Mode. To send monitor notifications to Rootly, configure a [Rootly Destination](/automate/connected-apps/incident.io-1.md).

## What You Can Do

**Read and investigate**

> Find Rootly incidents similar to this database saturation event and summarize their causes, mitigations, and time to resolution.
>
> Show the current and next on-call responders for the database team and summarize incidents from the current shift.

**Take action**

> Create a Rootly incident for this confirmed production impact with the correct service, severity, summary, and investigation link.
>
> Update the incident with the confirmed root cause and create action items for the remediation work, including suggested owners.

Rootly tools can cover incidents, alerts, on-call schedules, retrospectives, and action items. The exact actions available depend on permissions and tool restrictions.

## Setup

1. A workspace admin goes to **Integrations → Connectors → Org Connectors**, selects **Rootly**, and enables it.
2. The admin clicks **Connect**, completes OAuth, and reviews the [tool restrictions](/automate/connectors/mcp.md#managing-tool-restrictions).
3. Each user goes to **Integrations → Connectors → My Connections**, selects **Rootly**, and clicks **Connect**.
4. Complete the Rootly OAuth flow.

{% hint style="info" %}
Agent Mode acts with the connected user's Rootly permissions, subject to groundcover's tool restrictions. Write actions may require approval.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.groundcover.com/automate/connectors/rootly.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.