> For the complete documentation index, see [llms.txt](https://docs.cortex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cortex.io/ingesting-data-into-cortex/integrations/incidentio.md).

# incident.io

{% hint style="info" %}
Cortex connects to many third-party vendors whose system interfaces frequently change. As a result, integration behavior or configuration steps may shift without notice. If you encounter unexpected issues, check with your system administrator or refer to the vendor's documentation for the most current information. Additionally, integration sync times vary and are subject to scheduling overrides and timing variance.
{% endhint %}

This article explains how to configure the integration for incident.io. For instructions on using the integration, see [Using the integration for incident.io](/ingesting-data-into-cortex/integrations/incidentio/using-the-integration-for-incident.io.md).

## **Why use the integration for incident.io**

Incidents don't happen in a vacuum; they happen to services, teams, and systems. The integration for incident.io connects Cortex and incident.io so your teams can see, track, and act on operational health in one place with Cortex serving as the source of truth for both platforms.

Without this integration, incident data lives in isolation. Engineers have to cross-reference incident.io and Cortex manually to understand which services are struggling, which teams are burdened by recurring incidents, or whether an entity meets your organization's reliability standards. The integration eliminates that gap.

Once connected, active and historical incidents surface automatically on entity pages, giving anyone viewing a service a real-time picture of its operational state. You can also [trigger incidents](/ingesting-data-into-cortex/integrations/incidentio/using-the-integration-for-incident.io.md#triggering-an-incident) in incident.io directly from Cortex without switching tools, which is useful when you're already deep in an entity's details and need to escalate fast. And because incident.io can pull Cortex teams and catalog entities directly, your team and service data stays consistent across both tools without manual upkeep.

Beyond visibility, the integration unlocks measurement. With Cortex [Scorecards](/standardize/scorecards.md) and [CQL](/standardize/cql.md), you can write rules that evaluate incident behavior at scale, e.g. flagging entities with too many high-severity incidents in the past 90 days or ensuring every service has a registered incident.io configuration. This turns incident data into an input for engineering standards, not just an artifact to review after the fact.

In short: the incident.io integration makes incidents a first-class signal in Cortex, so you can hold services accountable to reliability expectations and give teams the context they need to respond faster.

### **Using Cortex as a source of truth in incident.io**

incident.io natively supports pulling Cortex teams and catalog entities into incident.io, so Cortex can serve as the source of truth for team and service data across both platforms. This is configured from the incident.io side. See [incident.io's Cortex integration docs](https://docs.incident.io/catalog/cortex) for setup instructions.

## Installing incident.io

### Prerequisites

1. Users with the `Configure Integrations` permission can configure incident.io.
2. Create an [incident.io API key](https://app.incident.io/settings/api-keys) with the following scopes:

* `Create incidents`
* `View all incident data, including private incidents`
* `View data like public incidents and organization settings`
* `View catalog types and entries`

**To install incident.io in Cortex**:

1. From the main sidebar, select **Integrations**.
2. Locate incident.io, then click **Install**.\
   The incident.io side panel opens.
3. In the incident.io side panel, do the following:
   1. The **Category** drop-down menu pre-populates with the appropriate category (required).
   2. Under **Configuration alias**, enter the alias for your configuration (required). Aliases let you specify which account a given entity belongs to when multiple incident.io accounts are connected to Cortex. If no alias is specified, Cortex uses the default configuration.
   3. Under **API key**, enter your incident.io API key (required).
4. Click **Save**.

### **Using multiple incident.io accounts**[**​**](https://docs.cortex.io/docs/reference/integrations/incidentio#configure-the-integration-for-multiple-propsintegration-accounts)

The incident.io integration supports multiple accounts. To add another, repeat the steps in [Installing incident.io](#installing-incident.io) for each additional account.

Each configuration requires an alias, which ties entity registrations to a specific account. If no alias is specified, Cortex uses the default configuration. To set a default:

1. From the main sidebar, select **Integrations**.
2. Locate incident.io, then click **Settings**.
3. Click the **pencil icon** next to a configuration.
4. Toggle **Set as default**. If you only have one configuration, it's automatically set as the default.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cortex.io/ingesting-data-into-cortex/integrations/incidentio.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.