Skip to main content
What you’ll get: Two complementary workflows, ewake can automatically investigate new incidents the moment they are declared, and build a production knowledge map from your past incidents and postmortems to surface historical context during live investigations.

​
Two ways to connect

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

1

Go to Webhooks in Incident.io

In Incident.io, navigate to Settings → Webhooks.Direct link: https://app.incident.io/[your-org]/settings/webhooks
2

Create a new webhook

Click Add webhook and fill in the following:Under Events, enable the following:Save the webhook. Incident.io will generate a signing secret, copy it immediately.
Copy the signing secret now, it won’t be shown again after closing this screen.
3

Register the signing secret in ewake

In your ewake dashboard, go to Integrations → Incident.io and open the card, Connect with API key if it is not connected yet, Overview if it is.Paste the signing secret in the dedicated field.Incident.io webhook signing secret field in ewake
Webhook is active. Ewake will automatically start investigating the next time an incident is declared in Incident.io.

​
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

1

Open Settings in Incident.io

Click the ⚙️ gear icon at the bottom left → Settings.
2

Go to API Keys

Under Extend → click API Keys → Create New API Key.
3

Set permissions

Grant the following permission groups:
4

Copy the API key

Copy the key immediately, you won’t be able to see it again.
5

Connect in ewake

Go to your ewake dashboard → Integrations → Incident.io → paste the API key → click Save.
Incident.io is connected. Ewake will begin ingesting your incident history.

​
Auto-invite ewake to incident channels

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

Open Workflows

In Incident.io → Settings → Workflows.
2

Create or edit a workflow

Add a workflow that triggers when an incident is declared.
3

Add the Slack bot step

Add the “Invite a Slack bot user to an incident channel” step → select ewake.
Ewake will be in every incident channel from the first message onward.