incident.io Tools

incident.io is an incident-management platform for declaring, coordinating, and resolving operational incidents. Use these tools in a workflow to list existing incidents, create a new incident, or fetch a single incident by ID via the incident.io v2 REST API.

Overview

Operations

Configuration

incidentio_list_incidents

incidentio_create_incident

Note: created incidents default to visibility: "public" in the request body.

incidentio_get_incident

Outputs

incidentio_list_incidents

• data (json) — Array of incident objects.
• metadata (json) — List metadata, containing:
  • count (number) — Number of incidents returned.
  • after (string) — Cursor for the next page.

incidentio_create_incident

• data (json) — The created incident object.
• metadata (json) — Incident identifiers, containing:
  • id (string) — Incident ID.
  • reference (string) — Incident reference.

incidentio_get_incident

• data (json) — The incident object.
• metadata (json) — Incident identifiers, containing:
  • id (string) — Incident ID.
  • reference (string) — Incident reference.

YAML Example

incidentio_1:
  type: incidentio
  name: "incident.io"
  inputs:
    operation: "incidentio_create_incident"
    name: "Checkout is failing for some users"
    idempotencyKey: "checkout-failure-2026-06-26"
    apiKey: "{{INCIDENTIO_API_KEY}}"
  connections:
    outgoing:
      - target: next-block-id

Tips

• Authentication is a Bearer API key. Generate one in the incident.io dashboard (Settings → API keys) and store it as an environment variable, then reference it with {{INCIDENTIO_API_KEY}} — never hard-code the key.
• For create operations, set idempotencyKey when retrying or when the same event might fire twice; if you leave it blank a random UUID is generated, so repeated runs will create duplicate incidents.
• The metadata.after cursor returned by incidentio_list_incidents is incident.io's pagination cursor — feed it forward (or page through with pageSize) when you need more than one page of results. Pass an incident's metadata.id (e.g. {{incidentio_1.metadata.id}}) into a downstream incidentio_get_incident step to fetch full details.