Skip to main content
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.
This article explains how to configure the integration for incident.io. For instructions on connecting incident.io to entities, see Connecting entities to incident.io. For information on how to use the integration, see Using the integration for incident.io.

​
Why use the integration for incident.io

incident.io is an incident management platform that coordinates how teams declare, respond to, and resolve incidents. The integration brings that data into Cortex, so an entity’s incident history and current on-call coverage sit alongside its ownership, dependencies, and Scorecard results. The integration for incident.io brings the following into Cortex:
  • Incidents - Active and historical incidents for an entity, with severity, status, and affected entities.
  • On-call schedules - Who’s on call now and who’s on call next for an entity. Requires the On-call category.
You can also build Scorecard rules and Cortex Query Language (CQL) queries against incident and on-call data, and track incident frequency and mean time to resolution (MTTR) in Eng Intelligence.

​
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 for setup instructions.

​
Configuring incident.io

​
Prerequisites

  1. Users with the Configure Integrations permission can configure incident.io.
  2. Create an incident.io API key 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
    • schedules.view
    • catalog_entries.view

​
Installing incident.io in Cortex

  1. From the main sidebar, expand Integrations, then select Configurations.
  2. Locate incident.io, then click Install. The incident.io side panel opens.
  3. In the incident.io side panel, do the following:
    1. From the Category dropdown, select the types of data to import (required):
      • Incidents - Imports incidents with severity, status, and affected entities.
      • On-call - Imports on-call schedules, including who’s on call now and next.
      For more information, see Integration categories.
    2. Under Configuration alias, enter the alias you’ll use to tie entity registrations to different configuration accounts (required).
    3. Under API key, enter your incident.io API key (required).
  4. Click Test connection. A successful connection means your integration is configured correctly.
  5. Click Save.
To modify an existing configuration, see Modifying an integration configuration.

​
Using multiple incident.io configurations

The incident.io integration supports multiple configurations. To add another:
  1. From the main sidebar, expand Integrations, then select Configurations.
  2. Locate incident.io, then click Settings.
  3. In the upper-right corner of the page, click Add configuration.
  4. Follow the steps in Installing incident.io in Cortex above.
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, expand Integrations, then select Configurations.
  2. Locate incident.io, then click Settings.
  3. Click the pencil icon next to a configuration.
  4. Toggle on Set as default. If you only have one configuration, it’s automatically set as the default.
Last modified on October 5, 2026