incident.io Integration
Bi-directional incident sync between TigerOps and incident.io for fully coordinated response. AI summaries, timeline events, and resolution data flow automatically in both directions.
How It Works
Create an incident.io API Key
In incident.io, go to Settings > API Keys and create a new key with incident and alert source permissions. You will also need your organization slug from the account settings.
Add TigerOps as an Alert Source
In incident.io, create a new HTTP alert source and point it to the TigerOps webhook URL displayed in the integration panel. This enables incident.io to receive TigerOps alerts.
Configure Field Mappings
Map TigerOps incident fields (severity, affected services, AI summary) to incident.io custom fields. Set team, role, and severity mappings for automatic responder assignment.
Sync Runs Bi-Directionally
Status changes in either system propagate to the other. Resolve in TigerOps, incident.io closes. Acknowledge in incident.io, TigerOps reflects the responder assignment.
What You Get Out of the Box
Bi-Directional Status Sync
Incident status changes in TigerOps and incident.io stay in sync in real time. Resolution, escalation, and acknowledgment in either system are reflected in both.
AI Summary in incident.io
TigerOps injects its AI-generated incident summary, root cause hypothesis, and impacted metrics directly into the incident.io incident description on creation.
Alert Source Integration
TigerOps acts as a native alert source in incident.io, so alerts flow through the standard incident.io alert routing, deduplication, and escalation pipeline.
Custom Field Population
TigerOps auto-populates incident.io custom fields such as affected services, error budget burn rate, SLO status, and deployment correlation on incident creation.
Timeline and Action Sync
Every TigerOps investigation step — anomaly detected, root cause identified, remediation executed — is posted as a timeline update in the incident.io incident feed.
Postmortem Pre-Fill
TigerOps pre-populates the incident.io follow-up and postmortem sections with AI-generated contributing factors, timeline summary, and suggested action items.
Bi-Directional Sync Config
Configure field mappings and sync behavior between TigerOps and incident.io.
# TigerOps — incident.io Integration Config
integrations:
incident_io:
api_key: "${INCIDENT_IO_API_KEY}"
org_slug: "${INCIDENT_IO_ORG_SLUG}"
webhook_secret: "${INCIDENT_IO_WEBHOOK_SECRET}"
min_severity: warning
auto_declare: true
auto_resolve: true
severity_mapping:
critical: "SEV1"
warning: "SEV2"
info: "SEV3"
custom_fields:
affected_services: "custom_field_abc"
slo_breach: "custom_field_def"
ai_summary: "custom_field_ghi"
deployment_sha: "custom_field_jkl"
sync_options:
push_timeline_events: true
push_runbook_actions: true
pull_status_changes: true
pull_role_assignments: true
service_mappings:
- tigerops_service: "api-gateway"
incident_io_service: "API Gateway"
default_severity: "SEV1"Common Questions
How does bi-directional sync work technically?
TigerOps uses the incident.io REST API to push updates outbound (creating incidents, posting timeline events). Inbound updates from incident.io flow via webhooks that incident.io fires to a TigerOps endpoint when incident status, severity, or assignments change.
Can I use TigerOps as an alert source in incident.io without creating incidents automatically?
Yes. You can configure TigerOps to only send alerts to the incident.io alert source without auto-declaring incidents. This lets incident.io alert routing rules and on-call engineers decide when to escalate to a full incident.
Will TigerOps create duplicate incidents if incident.io has already declared one manually?
TigerOps checks for an open incident.io incident with matching service and severity before creating a new one. If a match is found, TigerOps attaches its data to the existing incident instead of opening a duplicate.
Does the integration support incident.io custom severities?
Yes. You can map TigerOps internal severity levels (info, warning, critical) to any custom incident.io severity you have configured, including custom labels and numeric scales.
Can TigerOps trigger incident.io workflows and automation rules?
Yes. Because TigerOps integrates as a native alert source, any incident.io automation rules configured to run on alert receipt or incident creation will trigger normally — including Slack war room creation, PagerDuty paging, and Statuspage updates.
Close the Loop with incident.io
No credit card required. Bi-directional sync in minutes. AI data flows into every incident.