airbyte-agent-incident-io 0.1.3

Airbyte Incident-Io Connector for AI platforms

Incident-Io

The Incident-Io agent connector is a Python package that equips AI agents to interact with Incident-Io through strongly typed, well-documented tools. It's ready to use directly in your Python app, in an agent framework, or exposed through an MCP.

Connect to the incident.io API to access incident management data including incidents, alerts, escalations, users, schedules, and more. incident.io is an on-call, status pages, and incident response platform. This connector provides read-only access to core incident management entities via the v1 and v2 APIs. Requires an API key from your incident.io dashboard (Pro plan or above).

Example questions

The Incident-Io connector is optimized to handle prompts like these.

• List all incidents
• Show all open incidents
• List all alerts
• Show all users
• List all escalations
• Show all on-call schedules
• List all severities
• Show all incident statuses
• List all custom fields
• Which incidents were created this week?
• What are the most recent high-severity incidents?
• Who is currently on-call?
• How many incidents are in triage status?
• What incidents were updated today?

Unsupported questions

The Incident-Io connector isn't currently able to handle prompts like these.

• Create a new incident
• Update an incident's severity
• Delete an alert
• Assign someone to an incident role

Installation

uv pip install airbyte-agent-incident-io

Usage

Connectors can run in open source or hosted mode.

Open source

In open source mode, you provide API credentials directly to the connector.

from airbyte_agent_incident_io import IncidentIoConnector
from airbyte_agent_incident_io.models import IncidentIoAuthConfig

connector = IncidentIoConnector(
    auth_config=IncidentIoAuthConfig(
        api_key="<Your incident.io API key. Create one at https://app.incident.io/settings/api-keys>"
    )
)

@agent.tool_plain # assumes you're using Pydantic AI
@IncidentIoConnector.tool_utils
async def incident_io_execute(entity: str, action: str, params: dict | None = None):
    return await connector.execute(entity, action, params or {})

Hosted

In hosted mode, API credentials are stored securely in Airbyte Cloud. You provide your Airbyte credentials instead. If your Airbyte client can access multiple organizations, also set organization_id.

This example assumes you've already authenticated your connector with Airbyte. See Authentication to learn more about authenticating. If you need a step-by-step guide, see the hosted execution tutorial.

from airbyte_agent_incident_io import IncidentIoConnector, AirbyteAuthConfig

connector = IncidentIoConnector(
    auth_config=AirbyteAuthConfig(
        customer_name="<your_customer_name>",
        organization_id="<your_organization_id>",  # Optional for multi-org clients
        airbyte_client_id="<your-client-id>",
        airbyte_client_secret="<your-client-secret>"
    )
)

@agent.tool_plain # assumes you're using Pydantic AI
@IncidentIoConnector.tool_utils
async def incident_io_execute(entity: str, action: str, params: dict | None = None):
    return await connector.execute(entity, action, params or {})

Full documentation

Entities and actions

This connector supports the following entities and actions. For more details, see this connector's full reference documentation.

Entity	Actions
Incidents	List, Get, Search
Alerts	List, Get, Search
Escalations	List, Get, Search
Users	List, Get, Search
Incident Updates	List, Search
Incident Roles	List, Get, Search
Incident Statuses	List, Get, Search
Incident Timestamps	List, Get, Search
Severities	List, Get, Search
Custom Fields	List, Get, Search
Catalog Types	List, Get, Search
Schedules	List, Get, Search

Authentication

For all authentication options, see the connector's authentication documentation.

Incident-Io API docs

See the official Incident-Io API reference.

Version information

• Package version: 0.1.3
• Connector version: 1.0.2
• Generated with Connector SDK commit SHA: 9808f8a1ffe01ef505588251deb2fe305b0760e5
• Changelog: View changelog