> 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/incident-io.md).

# incident.io

Connect incident.io to analyze operations and manage incidents from Agent Mode

Connect incident.io to investigate incident history, alerts, on-call coverage, and service ownership, then take response and follow-up actions.

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

## What You Can Do

**Read and investigate**

> Show incidents affecting the payments service in the last 30 days and summarize recurring root causes and outstanding follow-ups.
>
> Who is on call for platform right now, and which alerts caused the most overnight responder work this month?

**Take action**

> Declare a high-severity incident for the checkout degradation shown in this investigation and include the affected service and evidence.
>
> Acknowledge the page for this incident, update its status and severity, and create follow-ups for the remediation items we identified.

Available tools include incident and escalation management as well as alert, schedule, catalog, and investigation analysis.

## Setup

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

{% hint style="info" %}
Agent Mode acts with the connected user's incident.io permissions, subject to groundcover's tool restrictions. Write actions may require approval. incident.io OAuth access expires periodically, so users may need to authorize again.
{% 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/incident-io.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.