> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ewake.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Incident.io

> Connect Incident.io to let ewake auto-investigate new incidents and build a knowledge map from your incident history.

<Info>
  **What you'll get:** Two complementary workflows, ewake can automatically investigate new incidents the moment they are declared, and build a [production knowledge map](/concepts) from your past incidents and postmortems to surface historical context during live investigations.
</Info>

***

## Two ways to connect

| Option      | What it does                                                            | When to use it                                                  |
| ----------- | ----------------------------------------------------------------------- | --------------------------------------------------------------- |
| **Webhook** | ewake automatically investigates new incidents as they are declared     | You want ewake active in every incident from the first second   |
| **API Key** | ewake ingests past incidents and postmortems to build its knowledge map | You want ewake to have historical context during investigations |

You can set up both. The webhook handles real-time response; the API key enriches the knowledge map over time.

***

## Option 1, Webhook (automatic investigation)

When a new incident is declared in Incident.io, ewake receives the event via webhook and immediately begins investigating, before anyone has to manually trigger it.

### Prerequisites

* An Incident.io account with **admin access** to the Webhooks settings
* Access to your ewake dashboard

### Configuration

<Steps>
  <Step title="Go to Webhooks in Incident.io">
    In Incident.io, navigate to **Settings** → **Webhooks**.

    Direct link: `https://app.incident.io/[your-org]/settings/webhooks`
  </Step>

  <Step title="Create a new webhook">
    Click **Add webhook** and fill in the following:

    | Field            | Value                                            |
    | ---------------- | ------------------------------------------------ |
    | **Endpoint URL** | `https://orch.ewake.ai/api/v1/webhooks/incident` |

    Under **Events**, enable the following:

    | Event                                        | Why                                                                                    |
    | -------------------------------------------- | -------------------------------------------------------------------------------------- |
    | `public_incident.incident_created_v2`        | **Required.** Triggers ewake the moment an incident is declared.                       |
    | `public_incident.incident_updated_v2`        | (Optional) Notifies ewake when incident details change during an active investigation. |
    | `public_incident.incident_status_updated_v2` | (Optional) Notifies ewake when an incident is resolved or its status changes.          |

    Save the webhook. Incident.io will generate a **signing secret**, copy it immediately.

    <Note>
      Copy the signing secret now, it won't be shown again after closing this screen.
    </Note>
  </Step>

  <Step title="Register the signing secret in ewake">
    In your ewake dashboard, go to **Integrations** → **Incident.io** → click **Configure**.

    Paste the signing secret in the dedicated field.

    <img src="https://mintcdn.com/ewakeai/M1QmRrA-jDM2VkcE/images/integrations/alerting/incident-io/webhook-signing-secret.png?fit=max&auto=format&n=M1QmRrA-jDM2VkcE&q=85&s=1aa9e139a6fb64f13db8cdae7f6a9c63" alt="Incident.io webhook signing secret field in ewake" style={{ maxHeight: "320px", objectFit: "cover", objectPosition: "top", borderRadius: "8px" }} width="934" height="320" data-path="images/integrations/alerting/incident-io/webhook-signing-secret.png" />

    <Check>
      Webhook is active. Ewake will automatically start investigating the next time an incident is declared in Incident.io.
    </Check>
  </Step>
</Steps>

***

## Option 2, API Key (knowledge map)

Connecting via API key gives ewake read access to your past incidents and postmortems. This enriches the knowledge map, so during a live investigation, ewake can surface patterns like *"this looks like incident #47 from three weeks ago, caused by a deploy on payments-api."*

The API key is **optional** if you are only using the webhook workflow, but recommended for the full experience.

### Prerequisites

* An Incident.io account with **admin permissions** to create API keys
* Access to your ewake dashboard

### Configuration

<Steps>
  <Step title="Open Settings in Incident.io">
    Click the **⚙️ gear icon** at the bottom left → **Settings**.
  </Step>

  <Step title="Go to API Keys">
    Under **Extend** → click **API Keys** → **Create New API Key**.
  </Step>

  <Step title="Set permissions">
    Grant the following permission groups:

    | Permission group                            | Scope     | Required?                           |
    | ------------------------------------------- | --------- | ----------------------------------- |
    | View data (public incidents + org settings) | 18 scopes | ✅ Required                          |
    | View catalog types and entries              | 3 scopes  | ✅ Required                          |
    | Read schedules                              | —         | Optional, enables on-call reasoning |
  </Step>

  <Step title="Copy the API key">
    Copy the key immediately, you won't be able to see it again.
  </Step>

  <Step title="Connect in ewake">
    Go to your ewake dashboard → **Integrations** → **Incident.io** → paste the API key → click **Connect**.

    <Check>
      Incident.io is connected. Ewake will begin ingesting your incident history.
    </Check>
  </Step>
</Steps>

***

## Auto-invite ewake to incident channels

Configure Incident.io to automatically add ewake to every new incident channel the moment it is created:

<Steps>
  <Step title="Open Workflows">
    In Incident.io → **Settings** → **Workflows**.
  </Step>

  <Step title="Create or edit a workflow">
    Add a workflow that triggers when an incident is declared.
  </Step>

  <Step title="Add the Slack bot step">
    Add the **"Invite a Slack bot user to an incident channel"** step → select **ewake**.
  </Step>
</Steps>

Ewake will be in every incident channel from the first message onward.