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.
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
| 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 |
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
Go to Webhooks in Incident.io
In Incident.io, navigate to Settings → Webhooks.Direct link:
https://app.incident.io/[your-org]/settings/webhooksCreate 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.
| Field | Value |
|---|---|
| Endpoint URL | https://orch.ewake.ai/api/v1/webhooks/incident |
| 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. |
Copy the signing secret now, it won’t be shown again after closing this screen.
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
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 |
Auto-invite ewake to incident channels
Configure Incident.io to automatically add ewake to every new incident channel the moment it is created:
Ewake will be in every incident channel from the first message onward.