incidentio

What This Skill Does

The incident.io skill allows OpenClaw AI agents to interface directly with the incident.io platform, enabling automated incident management workflows. It provides the capability to query organizational metadata such as severities, incident statuses, and incident types, which are prerequisites for creating standardized incidents. Furthermore, the skill supports the creation, retrieval, and updating of incidents, as well as the ability to post updates directly to an incident channel. By leveraging the incident.io REST API, this skill streamlines incident response by reducing manual intervention, ensuring that incidents are tracked consistently with the appropriate metadata.

Installation

To integrate this skill, use the OpenClaw CLI: clawhub install openclaw/skills/skills/jensastrup/incidentio

After installation, obtain an API key from your incident.io dashboard under Settings > API keys. Export this key as an environment variable in your working environment: export INCIDENTIO_API_KEY="your-api-key"

Ensure your token has the necessary permissions to read organizational data and create incidents.

Use Cases

• Automated Triage: Automatically trigger an incident creation in incident.io when a monitoring tool detects a critical system breach or service degradation.
• Status Synchronization: Keep stakeholders updated by programmatically posting status updates or investigative notes from an AI agent directly into an active incident.
• Consistency Enforcement: Standardize incident creation by having the AI agent fetch valid severity_id and incident_type_id values before opening a new ticket, preventing human entry errors.

Example Prompts

1. "Check the current list of incident severities and then create a new high-severity incident titled 'API latency spike' with a summary describing the current 500ms response time."
2. "List all active incident statuses, then fetch the details for incident ID INC-1234 to see the latest updates."
3. "Create a new incident for the 'Database Connection' issue, setting the type to 'Service Outage' and the status to 'Triage' using the correct IDs."

Tips & Limitations

• Idempotency: Always use unique idempotency keys for incident creation to prevent duplicate tickets in case of network retries.
• API Versioning: Remember that incident.io uses v2 for core incident operations and v1 for metadata like severities and types. Ensure your calls are routed correctly.
• Rate Limiting: The API allows 1200 requests per minute; for high-frequency automated tasks, ensure your agent implementation respects these thresholds.
• Data Integrity: Always fetch severities and status IDs dynamically; do not hardcode these IDs, as they vary between organization instances.