How it works
Once connected, Ewake uses Incident.io in two ways. Between incidents, it ingests postmortems, timelines, and workflows to build a picture of how your systems fail and how your team responds — this is what feeds the knowledge graph. During a live incident, engineers can ask Ewake questions and get answers drawn from that history, helping them resolve things faster.Prerequisites
Before setting up this integration, ensure you have:Configuration
Configure Permissions
Grant the following permission groups to the API key:Ewake asks for two things from Incident.io: the incident data itself, and the catalog that gives it meaning.
- View data, like public incidents and organisation settings (18 scopes). This is the core group — it’s what lets Ewake read incident timelines, alerts, and postmortems, which are the main inputs to the knowledge graph.
- View catalog types and entries (3 scopes). Needed so Ewake knows which services and teams a given incident touches.
- Can read schedules (optional). Enable this if you want Ewake to factor on-call rotations into its reasoning.
Copy API Key
Copy the generated API key to your clipboard.
Make sure to copy the key immediately as you won’t be able to see it again.
Slack bot in incident channels
To have Ewake in your live incident channels, configure Incident.io to automatically add the Ewake Slack bot to new incident channels:Create or edit a workflow
Create a new workflow, or edit an existing one, that runs when an incident is declared.