Skip to main content
Connecting incident.io lets Traversal reference incident details, linked alert details, severities, and incident statuses during investigations.

​
What Traversal reads

  • Incidents — incident details, severities, statuses, and timelines
  • Alerts — alerts linked to incidents

​
Setup

1

Create an API key

  1. In incident.io, go to Settings > API Keys
  2. Click Create API key and name it (e.g., “Traversal”)
  3. Grant read access to incidents and related metadata. If your workspace uses team-scoped API keys, make sure the key covers every team whose incidents Traversal should read.
  4. Copy the API key (starts with inc_, only shown once)
2

Configure in Traversal

Go to Company Knowledge > Integrations, select incident.io, and paste the API key.
This integration only requires an incident.io API key. You do not need to enter a base URL or any additional authentication fields.

​
Auto-add the Traversal Slack bot to incident channels

incident.io can automatically create a dedicated Slack channel for each incident (for example, #inc-2026-07-01-checkout-latency). To have Traversal join those channels the moment they’re created — even when they’re private — use an incident.io Workflow that invites the Traversal Slack bot.
This requires the Traversal Slack app to be installed in the same workspace where incident.io creates incident channels.
1

Create a workflow with the trigger “An incident is created or changed”

In incident.io, go to Settings > Workflows, click New Workflow, and select the trigger An incident is created or changed.Feel free to configure the workflow’s filters to select for the incidents you want Traversal’s bot in — for example, restrict it to incidents at or above a given severity. Leave the filters empty to have Traversal join every incident channel.
2

Add an “Invite a Slack bot ...” step

Add a step and choose Invite a Slack bot user to the incident channel. Select the Traversal bot as the user to invite.
3

Save and set the workflow live

Once your steps are added, click Save as draft, then Save and set live. If asked whether to run the workflow on incident changes, select No so it only applies to incidents going forward.
From then on, Traversal is added to each new incident channel automatically and can begin assisting as soon as the incident opens.
After enabling the workflow, trigger a test incident and confirm the Traversal bot appears in the new incident channel before relying on it in production.

​
More information