Use incident.io from Claude
Add the incident.io connection to a Space that runs Claude, then use it from every channel in that Space.
Connectorincident.io
incident.io integration for Claude and Codex
Create a incident.io connection, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.
CategoryDeveloper Tools & IT
Use incident.io from Codex
Add the incident.io connection to a Space that runs Codex, then use it from every channel in that Space.
Use incident.io from Sidekick
Connect your own OpenClaw to Sidekick while type.com provides the conversations, permissions, connections, skills, and automations.
Developer Tools & IT
What the incident.io connector can do
incident.io centralizes how a team detects, routes, and responds to incidents, with structured data for alerts, catalogs, and escalation. With an incident.io connection in type.com, an on-call or platform Space can ask the agent to stand up a new alert source, wire it to a route, or add a service to the catalog, all without switching out of the thread where the rest of the response is happening.
One connection, many Spaces
Connect incident.io once, then decide which Spaces can use it in threads, skills, automations, and coding work.
What teams do with incident.io in type.com
Stand up a new alert source fast
When a new monitoring tool comes online, ask the agent to create the incident.io alert source and attach the right attributes in one thread.
Create an incident.io alert source for our new Datadog webhook and add an attribute for affected region.
Route alerts without leaving the thread
Define a routing rule so alerts from a given source automatically group into the correct incident, cutting the manual triage step during an on-call shift.
Set up an incident.io alert route so database alerts always page the storage team.
Keep the service catalog current
As new services launch, have the agent add catalog entries so incident.io always reflects the current list of owned services and teams.
Add our new billing service as a catalog entry in incident.io under the payments team.
Representative actions
- Create Alert Attribute V2
Defines a structured field that incident.io can extract from incoming alerts, useful for organizing data from a new alert source.
- Create Alert Route V2
Sets up rules for how matching alerts get grouped, templated, and turned into incidents automatically.
- Create Alert Source V2
Registers a new integration for receiving alerts from an external system by webhook or manual entry.
- Create Catalog Entry V3
Adds a specific item, such as a team or service, into an existing incident.io catalog type.
- Create Catalog Type V3
Defines a new category of catalog resource, like teams or infrastructure components, for organizing incident data.
Connection
API and auth details
incident.io documents API access for incident-management and response workflows. Integrations can work with incidents, statuses, severities, custom fields, workflows, escalation and response data, catalog resources, and reporting-oriented incident records using API keys available on eligible plans.
- Source
- type.com catalog metadata
- Auth schemes
- API key
- API docs
- https://docs.incident.io/
- API reference
- https://api-docs.incident.io/
- Official site
- https://incident.io/
FAQ
Questions people ask before connecting incident.io
Can Claude configure incident.io alerts from type.com?
Yes. With an incident.io connection shared to a Space, the agent can create alert attributes, routes, and sources, and update the catalog, all from a thread your team already uses.
How does type.com authenticate with incident.io?
incident.io uses an API key. An admin adds it once when the connection is created, then decides which Spaces can use it for alert and catalog changes.
Can incident.io catalog updates run on a schedule?
Yes. Turn a recurring catalog check into a type.com automation, for example a weekly review that flags services missing from the incident.io catalog.
Is this the same as a incident.io MCP server?
Not exactly. type.com uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.
More developer tools & it connectors
All Developer Tools & IT integrationsConnect Buildkite to Claude in type.com to check access tokens, list organizations, and view connected pipeline agents from a shared thread.
Connect BunnyCDN to Claude in type.com to block IPs, manage referer rules, and add storage zones for your pull zones from a shared thread.
Connect CDR Platform to Claude in type.com to price carbon removal methods, check service health, and finalize purchases as a team.
Connect Celigo to Claude in type.com to clone flows, exports, and integrations, and assign export errors from a shared team thread.