incident.io logo
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.

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.

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 provides the conversations, permissions, connections, skills, and automations.

Developer Tools & IT

What the incident.io connector can do

Incident management and response platform

One connection, many Spaces

Connect incident.io once, then decide which Spaces can use it in threads, skills, automations, and coding work.

Representative actions

  • 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.

  • 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.

  • 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.

  • 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.

  • 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.

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.

FAQ

Questions people ask before connecting incident.io

Can Claude use incident.io?

Yes. Add a incident.io connection to a Space that runs Claude, then use its approved tools and data from any channel in that Space.

Can Codex work with incident.io through Type?

Yes. Add a incident.io connection to a Space that runs Codex, then use its approved tools and data from any channel in that Space.

Is this the same as a incident.io MCP server?

Not exactly. Type 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