---
title: "incident.io integration for LuumenAI"
url: "https://www.luumen.ai/integrations/incident-io/"
entity: SoftwareIntegration
category: "Incident response"
audience: "SRE, DevOps, platform engineering, IT operations"
---

# incident.io integration for LuumenAI

Read incident context on demand, and make changes as approved steps.

## What LuumenAI can do with incident.io

LuumenAI connects to incident.io with an API token and exposes 86 tools (43 read-only · 28 write · 15 destructive). Reads answer immediately; writes are shown as a plan and require approval by default, configurable per tool by an administrator.

## Key facts

- Authentication: API token
- Tools available: 86 tools (43 read-only · 28 write · 15 destructive)
- Plan: available on all plans
- Category: Incident response

## About incident.io with LuumenAI

Connect incident.io and your team can ask about alert routes, escalations, custom fields, and catalog entries without opening the web app. Luumen reads that configuration directly and answers in the terminal. When a change is needed — a new escalation, an alert route, a catalog entry — it shows the exact call first and waits for approval before sending it. Authentication is by API key.

## Example tools

Read-only (43 in total):

- `INCIDENT_IO_GET_ALERT_ATTRIBUTES_V2` — Retrieve a specific alert attribute by its ID from incident.io.
- `INCIDENT_IO_GET_ALERT_ROUTES_V2` — Retrieve a specific alert route configuration by its ID from incident.io.
- `INCIDENT_IO_GET_ALERT_SOURCES_V2` — Retrieve a specific alert source by its ID from incident.io.
- `INCIDENT_IO_GET_CATALOG_ENTRY_V3` — Retrieve a specific catalog entry by ID from incident.io.
- `INCIDENT_IO_GET_CATALOG_TYPES_V3` — Retrieve a specific catalog type by ID from incident.io V3 API.
- `INCIDENT_IO_GET_CUSTOM_FIELD_OPTIONS_V1` — Retrieve a specific custom field option by its ID.
- `INCIDENT_IO_GET_CUSTOM_FIELD_V1` — Retrieve details of a specific custom field by ID in incident.io.
- `INCIDENT_IO_GET_CUSTOM_FIELD_V2` — Retrieve details of a specific custom field by ID using the V2 API in incident.io.

Write and destructive (43 in total, approval required by default):

- `INCIDENT_IO_CREATE_ALERT_ATTRIBUTES_V2` — Create an alert attribute in incident.io.
- `INCIDENT_IO_CREATE_ALERT_ROUTES_V2` — Create an alert route in incident.io.
- `INCIDENT_IO_CREATE_ALERT_SOURCES_V2` — Create a new alert source in incident.io.
- `INCIDENT_IO_CREATE_CATALOG_ENTRIES_V3` — Create a catalog entry in incident.io using the V3 API.
- `INCIDENT_IO_CREATE_CATALOG_TYPES_V3` — Create a new catalog type in incident.io V3 API.
- `INCIDENT_IO_CREATE_CUSTOM_FIELD_OPTIONS_V1` — Create a new custom field option in incident.io.
- `INCIDENT_IO_CREATE_CUSTOM_FIELDS_V2` — Create a custom field in incident.io using the V2 API.
- `INCIDENT_IO_CREATE_ESCALATIONS_V2` — Create an escalation in incident.io.

## Frequently asked questions

### How does LuumenAI connect to incident.io?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

### Can LuumenAI change things in incident.io on its own?

Read actions answer immediately. Anything that writes is shown as a plan and requires approval by default, including the 15 actions classified as destructive. Administrators configure that per tool.

### Is there an audit trail?

Every call to incident.io — read or write, approved or declined — is recorded with the actor, the input, and the result.

Full page: https://www.luumen.ai/integrations/incident-io/