incident.io
Connect
Connect incident.io from the terminal. Pass --help for the flags incident.io accepts.
polylane integration connect --type incident_ioAn API key from Settings → API keys in incident.io.
Connect your incident.io organization with one API key.
- In incident.io API keys, create an API key with the roles listed under Learn more.
- Paste the key into Polylane. Polylane checks it and shows what the key turns on, and names the role a feature needs when that role is missing.
Every new live incident in incident.io starts a Polylane investigation. When Slack is connected to Polylane, the findings post in the incident's Slack channel. Private and test incidents are skipped.
Escalations that Polylane cannot resolve reach incident.io as alerts when their severity is at or above the level set on the integration page, high by default. An alert pages no one until you add the Polylane alert source to an alert route in incident.io.
Read incident.io data and request API changes through Polylane. Changes require safety review and approval.
Polylane maps your incident.io catalog services into the context graph and links them to their repositories.
On connect, Polylane creates a workflow named "Polylane: investigate incidents (your workspace name)", a workflow secret, and an HTTP alert source named "Polylane" in incident.io. Disconnecting deletes all three.
Polylane uses these incident.io roles. A feature whose role is missing stays off, and the integration page names the role.
| Role | What it unlocks |
|---|---|
viewer | Reads incidents, updates, follow-ups, and the catalog, and maps catalog services into the context graph. Required. |
schedules_reader | Reads on-call schedules to tell who is on call. |
workflows_editor, secrets_manage | Creates the workflow that starts an investigation for each new incident. |
on_call_editor | Creates the Polylane alert source that receives unresolved escalations. |
incident_editor, incident_creator | Creates and edits incidents and posts updates, after safety review and approval. |
escalation_creator | Pages an escalation path, after safety review and approval. |
Disconnecting leaves the API key in incident.io. Remove it under Settings → API keys in incident.io.
Disconnect
Disconnecting stops every sync and check and deletes the credentials Polylane held. Polylane removes what incident.io's API lets it remove. The following stays until you remove it yourself:
- incident.io API key
polylane integration disconnect <id>Tools
4Operations agents can perform in threads.