incident.io integration

Quick start

Call incident.io from your generated app's worker code via the OverSkill composio client. The toolkit slug below maps to incident.io's public Composio identifier — your app references it by name and OverSkill handles the OAuth round-trip.

// In your generated app's worker handler:
const composio = composioClient(env);

const result = await composio.execute(
  "INCIDENT_IO_ACTION_NAME",
  { /* action parameters — see Actions section below */ }
);

return new Response(JSON.stringify(result), {
  headers: { "Content-Type": "application/json" }
});

Replace ACTION_NAME with one of the slugs listed in the Actions section below. The composio client handles auth + rate limits automatically — no API key is exposed to user code.

Setup

End-users supply their own incident.io API key. OverSkill provides a pre-built connection form via the integration card — your app can call the composio client immediately once the user has connected.

Available actions

86 actions exposed via the incident.io integration. Each maps to a callable slug — pass it to composio.execute(...) in your worker code.

• INCIDENT_IO_CREATE_ALERT_ATTRIBUTES_V2
• INCIDENT_IO_CREATE_ALERT_ROUTES_V2
• INCIDENT_IO_CREATE_ALERT_SOURCES_V2
• INCIDENT_IO_CREATE_CATALOG_ENTRIES_V3
• INCIDENT_IO_CREATE_CATALOG_TYPES_V3
• INCIDENT_IO_CREATE_CUSTOM_FIELD_OPTIONS_V1
• INCIDENT_IO_CREATE_CUSTOM_FIELDS_V2
• INCIDENT_IO_CREATE_ESCALATIONS_V2
• INCIDENT_IO_CREATE_INCIDENT_ROLES_V2
• INCIDENT_IO_CREATE_INCIDENT_STATUS
• INCIDENT_IO_CREATE_INCIDENTS_V2
• INCIDENT_IO_CREATE_MANAGED_RESOURCES_V2