# incident.io AI integration on Definable

> Incident management and response platform

## What this connects

Incident management and response platform

Vendor: https://incident.io

## Tools available

**86** tools available. First 12:

- `INCIDENT_IO_CREATE_ALERT_ATTRIBUTES_V2` — Create Alert Attribute V2 — Tool to create an alert attribute in incident.io. Use when you need to define structured data fields that can be parsed from alerts coming in via alert sources. Alert attributes allow you to extract and organize information from incoming alerts.
- `INCIDENT_IO_CREATE_ALERT_ROUTES_V2` — Create Alert Route V2 — Tool to create an alert route in incident.io. Use when you need to configure how alerts should be processed, routed, and potentially converted into incidents based on conditions, grouping rules, and templates.
- `INCIDENT_IO_CREATE_ALERT_SOURCES_V2` — Create Alert Source V2 — Tool to create a new alert source in incident.io. Use when you need to set up a new integration for receiving alerts from external systems via HTTP webhooks or manual entry.
- `INCIDENT_IO_CREATE_CATALOG_ENTRIES_V3` — Create Catalog Entry V3 — Tool to create a catalog entry in incident.io using the V3 API. Use when you need to add a new entry to a catalog type with specific attribute values. Catalog entries represent items like teams, services, or custom resources in your incident management workflow.
- `INCIDENT_IO_CREATE_CATALOG_TYPES_V3` — Create Catalog Type V3 — Tool to create a new catalog type in incident.io V3 API. Use when you need to define custom resource types for your organization's catalog, such as teams, services, or infrastructure components.
- `INCIDENT_IO_CREATE_CUSTOM_FIELD_OPTIONS_V1` — Create Custom Field Option — Tool to create a new custom field option in incident.io. Use when you need to add a new selectable value to an existing custom field.
- `INCIDENT_IO_CREATE_CUSTOM_FIELDS_V2` — Create Custom Field V2 — Tool to create a custom field in incident.io using the V2 API. Use when you need to add a new custom field to track additional information during incidents.
- `INCIDENT_IO_CREATE_ESCALATIONS_V2` — Create Escalation V2 — Tool to create an escalation in incident.io. Use when you need to page users to respond to alerts. You must specify either an escalation_path_id or direct targets (users/schedules).
- `INCIDENT_IO_CREATE_INCIDENT_ROLES_V2` — Create Incident Role V2 — Tool to create a new incident role in incident.io using the V2 API. Use when you need to define a new role type that can be assigned during incidents to organize responsibilities and ensure the right people are engaged during incident response.
- `INCIDENT_IO_CREATE_INCIDENT_STATUS` — Create Incident Status — Tool to create a new incident status in incident.io. Use when you need to add a custom status for categorizing incidents as 'live' (active), 'learning' (post-incident), or 'closed'.
- `INCIDENT_IO_CREATE_INCIDENTS_V2` — Create Incident V2 — Tool to create a new incident in incident.io using the V2 API. Use when you need to report and track an operational issue or outage. Requires at minimum an idempotency_key and visibility setting. Optionally specify severity, incident type, custom fields, role assignments, and other attributes.
- `INCIDENT_IO_CREATE_MANAGED_RESOURCES_V2` — Create Managed Resource V2 — Tool to create a managed resource in incident.io. Use when you need to mark a resource (schedule, escalation path, or workflow) as being managed by an external system like Terraform or a custom automation tool. This helps track which resources are controlled externally and should not be modified through the dashboard.

## Auth

Auth schemes: `API_KEY`.

## How agents use incident.io

Inside a Definable workflow, incident.io is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → incident.io** — the Researcher (GPT-5.5) pulls context from incident.io (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → incident.io** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into incident.io (create record, post message, draft email).
- **Designer / Engineer → Distributor → incident.io** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via incident.io (attach file, open PR comment, post status).

The Verifier checks every incident.io call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- developer tools — https://definable.ai/apps/category/developer-tools/

## Related

- HTML page: https://definable.ai/apps/incident_io/
- Same category (developer tools): https://definable.ai/apps/category/developer-tools/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt