incident.io

App · 26 actions

Run incident response from your workflows: declare and update incidents, share updates, add follow-ups and actions, raise and resolve alerts, see who is on call, cover shifts and page people.

Actions

ActionWhat it does
Create follow-upAdd a follow-up to an incident: something to do once it is over.
Create incident actionAdd an action to an incident: a task to do while it is under way.
Declare incidentDeclare an incident.
Delete follow-upDelete a follow-up from its incident.
Get alertGet one alert with its status, source and links.
Get follow-upGet one follow-up with its status, assignee and labels.
Get incidentGet one incident with its status, severity, type, roles and Slack channel.
Get incident settingsGet the severities, statuses, incident types and roles your organization uses, with their ids.
Get who is on callFind who is on call for a schedule now, or at a time you choose.
List alertsList alerts from your monitoring tools, newest first, filtered by status, source or when they fired.
List escalationsList pages sent to people, filtered by state, escalation path or time.
List follow-upsList follow-ups (work to do after an incident), on one incident or all, oldest first.
List incident actionsList actions (tasks to do while an incident is under way), on one incident or all, oldest first.
List incident updatesList the updates shared on an incident, or on every incident.
List incidentsList incidents, newest first, filtered by stage, status, severity, type or the day they were declared.
List schedulesList your on-call schedules with who is on call on each right now.
List usersList the people in your incident.io organization, or find one by email.
Page peoplePage people now, through an escalation path or directly, with incident.io's on-call notifications (an escalation).
Put someone on callPut a person on call on a schedule for a time window, in place of whoever the rota has (a schedule override).
Remove on-call overrideRemove an override, so the rota decides who is on call again.
Resolve alertMark a firing alert resolved.
Send alertRaise (or clear) an alert on one of your HTTP alert sources, so incident.io routes it as it would one from a monitoring tool.
Share incident updatePost an update on an incident for everyone following it, and move its status or severity at the same time if you choose.
Update follow-upChange a follow-up's title, description, status, assignee or labels.
Update incidentChange an incident's name, summary, severity, status or call link, or give someone a role.
Update incident actionChange an action's description, status or assignee, such as marking it completed.

Create follow-up

Add a follow-up to an incident: something to do once it is over.

Inputs

Incident IDincident_idtextRequired
The incident's id, from 'List incidents', 'Declare incident' or a trigger.
TitletitletextRequired
What should be done after the incident.
Descriptiondescriptiontext
More detail. Markdown works.
Assigneeassignee_idtext
The person it is assigned to.
Labelslabelslist
Labels to file it under.

Outputs

follow_upobject
The follow-up
Example output
{
  "follow_up": {
    "assignee": {
      "email": "jo@example.com",
      "id": "01G0J1EXE7AXZ2C93K61WBPYEH",
      "name": "Jo Bloggs",
      "slack_user_id": "U0123ABC"
    },
    "completed_at": "",
    "created_at": "2026-10-15T09:00:00Z",
    "description": "So we hear before customers do.",
    "id": "01FCNDV6P870EA6S7TK1DSYDG7",
    "incident_id": "01FDAG4SAP5TYPT98WGR2N7W91",
    "labels": [
      "monitoring"
    ],
    "status": "outstanding",
    "title": "Add an alert for checkout errors",
    "updated_at": "2026-10-15T09:00:00Z"
  }
}

Create incident action

Add an action to an incident: a task to do while it is under way.

Inputs

Incident IDincident_idtextRequired
The incident's id, from 'List incidents', 'Declare incident' or a trigger.
DescriptiondescriptiontextRequired
What needs doing. Markdown works.
Assigneeassignee_idtext
The person it is assigned to.

Outputs

incident_actionobject
The action
Example output
{
  "incident_action": {
    "assignee": {
      "email": "jo@example.com",
      "id": "01G0J1EXE7AXZ2C93K61WBPYEH",
      "name": "Jo Bloggs",
      "slack_user_id": "U0123ABC"
    },
    "completed_at": "",
    "created_at": "2026-10-15T09:00:00Z",
    "description": "Roll back the payments service",
    "id": "01FCNDV6P870EA6S7TK1DSYDG8",
    "incident_id": "01FDAG4SAP5TYPT98WGR2N7W91",
    "status": "outstanding",
    "updated_at": "2026-10-15T09:00:00Z"
  }
}

Declare incident

Declare an incident. incident.io opens its Slack channel and runs your workflows as it would for one declared by hand.

Inputs

NamenametextRequired
A short explanation of what is happening.
Summarysummarytext
More detail on the incident. Markdown works.
Severityseverity_idtext
The incident's severity.
Typeincident_type_idtext
The incident type. Leave empty for your default type.
Statusincident_status_idtext
The status to start in. Leave empty for incident.io's usual first status.
Visibilityvisibilitytext
Public incidents are open to anyone in your Slack workspace; private ones are invite only. Defaults to public.One of: public (Public: anyone in your Slack workspace (default)), private (Private: invite only).
Kind of incidentmodetext
A real incident, a test (kept out of reports), or a past incident you are recording, which is not announced. Defaults to real.One of: standard (Real incident (default)), test (Test incident), retrospective (Past incident, not announced).
Role to assignrole_idtext
A role, such as Incident Lead, to give to the person chosen next.
Give the role torole_user_idtext
The person who takes the role chosen.
Slack channel nameslack_channel_nametext
A name for the incident's Slack channel, instead of the usual one.

Outputs

incidentobject
The incident
Example output
{
  "incident": {
    "call_url": "https://zoom.us/j/123",
    "created_at": "2026-10-15T09:00:00Z",
    "id": "01FDAG4SAP5TYPT98WGR2N7W91",
    "incident_role_assignments": [
      {
        "assignee": {
          "email": "jo@example.com",
          "id": "01G0J1EXE7AXZ2C93K61WBPYEH",
          "name": "Jo Bloggs",
          "slack_user_id": "U0123ABC"
        },
        "role": {
          "description": "Runs the response.",
          "id": "01FCNDV6P870EA6S7TK1DSYDG9",
          "name": "Incident Lead",
          "role_type": "lead",
          "shortform": "lead"
        }
      }
    ],
    "incident_status": {
      "category": "live",
      "description": "We are looking into it.",
      "id": "01FCNDV6P870EA6S7TK1DSYD5H",
      "name": "Investigating",
      "rank": 2
    },
    "incident_type": {
      "description": "Something customers can see is broken.",
      "id": "01FCNDV6P870EA6S7TK1DSYDG2",
      "is_default": true,
      "name": "Production outage"
    },
    "mode": "standard",
    "name": "Checkout is failing for some users",
    "permalink": "https://app.incident.io/incidents/123",
    "reference": "INC-123",
    "severity": {
      "description": "Issues causing significant impact.",
      "id": "01FH5TZRWMNAFB0DZ23FD1TV96",
      "name": "Major",
      "rank": 3
    },
    "slack_channel_id": "C02AW36C1M5",
    "slack_channel_name": "inc-123-checkout-is-failing",
    "slack_channel_url": "https://slack.com/app_redirect?channel=C02AW36C1M5",
    "summary": "Card payments fail with a timeout.",
    "updated_at": "2026-10-15T09:00:00Z",
    "visibility": "public"
  }
}

Delete follow-up

Delete a follow-up from its incident.

Inputs

Follow-up IDfollow_up_idtextRequired
The follow-up's id, from 'List follow-ups' or 'Create follow-up'.

Outputs

deletedtrue/false
Always true once deleted
follow_up_idtext
The follow-up deleted
Example output
{
  "deleted": true,
  "follow_up_id": "01FCNDV6P870EA6S7TK1DSYDG7"
}

Get alert

Get one alert with its status, source and links.

Inputs

Alert IDalert_idtextRequired
The alert's id, from 'List alerts' or a trigger.

Outputs

alertobject
The alert
Example output
{
  "alert": {
    "alert_source_id": "01GW2G3V0S59R238FAHPDS1R67",
    "created_at": "2026-10-15T09:00:00Z",
    "deduplication_key": "checkout-errors",
    "description": "Errors started at 09:00.",
    "id": "01GW2G3V0S59R238FAHPDS1R66",
    "resolved_at": "",
    "source_url": "https://grafana.example.com/d/checkout",
    "status": "firing",
    "title": "Checkout error rate above 5%",
    "updated_at": "2026-10-15T09:00:00Z"
  }
}

Get follow-up

Get one follow-up with its status, assignee and labels.

Inputs

Follow-up IDfollow_up_idtextRequired
The follow-up's id, from 'List follow-ups' or 'Create follow-up'.

Outputs

follow_upobject
The follow-up
Example output
{
  "follow_up": {
    "assignee": {
      "email": "jo@example.com",
      "id": "01G0J1EXE7AXZ2C93K61WBPYEH",
      "name": "Jo Bloggs",
      "slack_user_id": "U0123ABC"
    },
    "completed_at": "",
    "created_at": "2026-10-15T09:00:00Z",
    "description": "So we hear before customers do.",
    "id": "01FCNDV6P870EA6S7TK1DSYDG7",
    "incident_id": "01FDAG4SAP5TYPT98WGR2N7W91",
    "labels": [
      "monitoring"
    ],
    "status": "outstanding",
    "title": "Add an alert for checkout errors",
    "updated_at": "2026-10-15T09:00:00Z"
  }
}

Get incident

Get one incident with its status, severity, type, roles and Slack channel.

Inputs

Incident IDincident_idtextRequired
The incident's id, from 'List incidents', 'Declare incident' or a trigger.

Outputs

incidentobject
The incident
Example output
{
  "incident": {
    "call_url": "https://zoom.us/j/123",
    "created_at": "2026-10-15T09:00:00Z",
    "id": "01FDAG4SAP5TYPT98WGR2N7W91",
    "incident_role_assignments": [
      {
        "assignee": {
          "email": "jo@example.com",
          "id": "01G0J1EXE7AXZ2C93K61WBPYEH",
          "name": "Jo Bloggs",
          "slack_user_id": "U0123ABC"
        },
        "role": {
          "description": "Runs the response.",
          "id": "01FCNDV6P870EA6S7TK1DSYDG9",
          "name": "Incident Lead",
          "role_type": "lead",
          "shortform": "lead"
        }
      }
    ],
    "incident_status": {
      "category": "live",
      "description": "We are looking into it.",
      "id": "01FCNDV6P870EA6S7TK1DSYD5H",
      "name": "Investigating",
      "rank": 2
    },
    "incident_type": {
      "description": "Something customers can see is broken.",
      "id": "01FCNDV6P870EA6S7TK1DSYDG2",
      "is_default": true,
      "name": "Production outage"
    },
    "mode": "standard",
    "name": "Checkout is failing for some users",
    "permalink": "https://app.incident.io/incidents/123",
    "reference": "INC-123",
    "severity": {
      "description": "Issues causing significant impact.",
      "id": "01FH5TZRWMNAFB0DZ23FD1TV96",
      "name": "Major",
      "rank": 3
    },
    "slack_channel_id": "C02AW36C1M5",
    "slack_channel_name": "inc-123-checkout-is-failing",
    "slack_channel_url": "https://slack.com/app_redirect?channel=C02AW36C1M5",
    "summary": "Card payments fail with a timeout.",
    "updated_at": "2026-10-15T09:00:00Z",
    "visibility": "public"
  }
}

Get incident settings

Get the severities, statuses, incident types and roles your organization uses, with their ids.

Inputs

None.

Outputs

incident_roleslist
The incident roles
incident_statuseslist
The statuses, in order
incident_typeslist
The incident types
severitieslist
The severities, least severe first
Example output
{
  "incident_roles": [
    {
      "description": "Runs the response.",
      "id": "01FCNDV6P870EA6S7TK1DSYDG9",
      "name": "Incident Lead",
      "role_type": "lead",
      "shortform": "lead"
    }
  ],
  "incident_statuses": [
    {
      "category": "live",
      "description": "We are looking into it.",
      "id": "01FCNDV6P870EA6S7TK1DSYD5H",
      "name": "Investigating",
      "rank": 2
    }
  ],
  "incident_types": [
    {
      "description": "Something customers can see is broken.",
      "id": "01FCNDV6P870EA6S7TK1DSYDG2",
      "is_default": true,
      "name": "Production outage"
    }
  ],
  "severities": [
    {
      "description": "Issues causing significant impact.",
      "id": "01FH5TZRWMNAFB0DZ23FD1TV96",
      "name": "Major",
      "rank": 3
    }
  ]
}

Get who is on call

Find who is on call for a schedule now, or at a time you choose.

Inputs

Scheduleschedule_idtextRequired
The on-call schedule.
Atatdate and time
The moment to look at. Leave empty for now.

Outputs

attext
The moment looked at
countnumber
How many people are on call
namestext
Their names, joined with commas
schedule_idtext
The schedule looked at
shiftslist
The shifts covering that moment
userslist
Everyone on call then
Example output
{
  "at": "2026-10-15T09:00:00Z",
  "count": 1,
  "names": "Jo Bloggs",
  "schedule_id": "01G0J1EXE7AXZ2C93K61WBPYEK",
  "shifts": [
    {
      "end_at": "2026-10-22T00:00:00Z",
      "rotation_id": "01G0J1EXE7AXZ2C93K61WBPYEJ",
      "start_at": "2026-10-15T00:00:00Z",
      "user": {
        "email": "jo@example.com",
        "id": "01G0J1EXE7AXZ2C93K61WBPYEH",
        "name": "Jo Bloggs",
        "slack_user_id": "U0123ABC"
      }
    }
  ],
  "users": [
    {
      "email": "jo@example.com",
      "id": "01G0J1EXE7AXZ2C93K61WBPYEH",
      "name": "Jo Bloggs",
      "slack_user_id": "U0123ABC"
    }
  ]
}

List alerts

List alerts from your monitoring tools, newest first, filtered by status, source or when they fired.

Inputs

Statusstatustext
Only firing or only resolved alerts.One of: firing, resolved.
Alert sourcealert_source_idtext
Only alerts from this source.
Deduplication keydeduplication_keytext
Only the alert with this key.
Fired on or aftercreated_afterdate and time
Only alerts that fired at or after this time.
Page sizepage_sizenumber
How many to return, 1 to 50. The default is 25.From 1 to 50.
Next page cursoraftertext
The 'next_cursor' from an earlier page, to get the page after it.

Outputs

alertslist
The alerts
countnumber
How many are on this page
next_cursortext
Pass as 'Next page cursor' to get the next page; empty on the last
total_countnumber
How many match in all, when incident.io says
Example output
{
  "alerts": [
    {
      "alert_source_id": "01GW2G3V0S59R238FAHPDS1R67",
      "created_at": "2026-10-15T09:00:00Z",
      "deduplication_key": "checkout-errors",
      "description": "Errors started at 09:00.",
      "id": "01GW2G3V0S59R238FAHPDS1R66",
      "resolved_at": "",
      "source_url": "https://grafana.example.com/d/checkout",
      "status": "firing",
      "title": "Checkout error rate above 5%",
      "updated_at": "2026-10-15T09:00:00Z"
    }
  ],
  "count": 1,
  "next_cursor": "",
  "total_count": 1
}

List escalations

List pages sent to people, filtered by state, escalation path or time.

Inputs

Statusstatustext
Only escalations in this state.One of: pending, triggered, acked (Acknowledged), resolved, expired, cancelled, snoozed, delayed, pending_repeat (Waiting to repeat).
Escalation pathescalation_path_idtext
Only escalations that followed this path.
Created on or aftercreated_afterdate and time
Only those created at or after this time.
Page sizepage_sizenumber
How many to return, 1 to 50. The default is 25.From 1 to 50.
Next page cursoraftertext
The 'next_cursor' from an earlier page, to get the page after it.

Outputs

countnumber
How many are on this page
escalationslist
The escalations
next_cursortext
Pass as 'Next page cursor' to get the next page; empty on the last
total_countnumber
How many match in all, when incident.io says
Example output
{
  "count": 1,
  "escalations": [
    {
      "created_at": "2026-10-15T09:00:00Z",
      "description": "The primary is at 100%.",
      "escalation_path_id": "01G0J1EXE7AXZ2C93K61WBPYEP",
      "id": "01G0J1EXE7AXZ2C93K61WBPYEN",
      "priority": {
        "name": "High"
      },
      "status": "triggered",
      "title": "Database is out of disk",
      "updated_at": "2026-10-15T09:00:00Z"
    }
  ],
  "next_cursor": "",
  "total_count": 1
}

List follow-ups

List follow-ups (work to do after an incident), on one incident or all, oldest first.

Inputs

Incident IDincident_idtext
Only those on this incident. Leave empty for every incident.
Kind of incidentincident_modetext
Only from incidents of this kind. Leave empty for real incidents and past incidents recorded afterwards.One of: standard (Real incidents), retrospective (Past incidents recorded afterwards), test (Test incidents), tutorial (Tutorial incidents).
Created on or aftercreated_afterdate and time
Only those created at or after this time.
Page sizepage_sizenumber
How many to return, 1 to 250. incident.io's default is 25.From 1 to 250.
Next page cursoraftertext
The 'next_cursor' from an earlier page, to get the page after it.

Outputs

countnumber
How many are on this page
follow_upslist
The follow-ups
next_cursortext
Pass as 'Next page cursor' to get the next page; empty on the last
total_countnumber
How many match in all, when incident.io says
Example output
{
  "count": 1,
  "follow_ups": [
    {
      "assignee": {
        "email": "jo@example.com",
        "id": "01G0J1EXE7AXZ2C93K61WBPYEH",
        "name": "Jo Bloggs",
        "slack_user_id": "U0123ABC"
      },
      "completed_at": "",
      "created_at": "2026-10-15T09:00:00Z",
      "description": "So we hear before customers do.",
      "id": "01FCNDV6P870EA6S7TK1DSYDG7",
      "incident_id": "01FDAG4SAP5TYPT98WGR2N7W91",
      "labels": [
        "monitoring"
      ],
      "status": "outstanding",
      "title": "Add an alert for checkout errors",
      "updated_at": "2026-10-15T09:00:00Z"
    }
  ],
  "next_cursor": "",
  "total_count": 1
}

List incident actions

List actions (tasks to do while an incident is under way), on one incident or all, oldest first.

Inputs

Incident IDincident_idtext
Only those on this incident. Leave empty for every incident.
Kind of incidentincident_modetext
Only from incidents of this kind. Leave empty for real incidents and past incidents recorded afterwards.One of: standard (Real incidents), retrospective (Past incidents recorded afterwards), test (Test incidents), tutorial (Tutorial incidents).
Created on or aftercreated_afterdate and time
Only those created at or after this time.
Page sizepage_sizenumber
How many to return, 1 to 250. incident.io's default is 25.From 1 to 250.
Next page cursoraftertext
The 'next_cursor' from an earlier page, to get the page after it.

Outputs

countnumber
How many are on this page
incident_actionslist
The actions
next_cursortext
Pass as 'Next page cursor' to get the next page; empty on the last
total_countnumber
How many match in all, when incident.io says
Example output
{
  "count": 1,
  "incident_actions": [
    {
      "assignee": {
        "email": "jo@example.com",
        "id": "01G0J1EXE7AXZ2C93K61WBPYEH",
        "name": "Jo Bloggs",
        "slack_user_id": "U0123ABC"
      },
      "completed_at": "",
      "created_at": "2026-10-15T09:00:00Z",
      "description": "Roll back the payments service",
      "id": "01FCNDV6P870EA6S7TK1DSYDG8",
      "incident_id": "01FDAG4SAP5TYPT98WGR2N7W91",
      "status": "outstanding",
      "updated_at": "2026-10-15T09:00:00Z"
    }
  ],
  "next_cursor": "",
  "total_count": 1
}

List incident updates

List the updates shared on an incident, or on every incident.

Inputs

Incident IDincident_idtext
Only those on this incident. Leave empty for every incident.
Page sizepage_sizenumber
How many to return, 1 to 250. incident.io's default is 25.From 1 to 250.
Next page cursoraftertext
The 'next_cursor' from an earlier page, to get the page after it.

Outputs

countnumber
How many are on this page
incident_updateslist
The updates
next_cursortext
Pass as 'Next page cursor' to get the next page; empty on the last
total_countnumber
How many match in all, when incident.io says
Example output
{
  "count": 1,
  "incident_updates": [
    {
      "created_at": "2026-10-15T09:00:00Z",
      "id": "01FCNDV6P870EA6S7TK1DSYDG5",
      "incident_id": "01FDAG4SAP5TYPT98WGR2N7W91",
      "message": "We have found the cause and are rolling back.",
      "new_incident_status": {
        "category": "live",
        "description": "We are looking into it.",
        "id": "01FCNDV6P870EA6S7TK1DSYD5H",
        "name": "Investigating",
        "rank": 2
      },
      "new_severity": {
        "description": "Issues causing significant impact.",
        "id": "01FH5TZRWMNAFB0DZ23FD1TV96",
        "name": "Major",
        "rank": 3
      },
      "updater": {
        "user": {
          "email": "jo@example.com",
          "id": "01G0J1EXE7AXZ2C93K61WBPYEH",
          "name": "Jo Bloggs",
          "slack_user_id": "U0123ABC"
        }
      }
    }
  ],
  "next_cursor": "",
  "total_count": 1
}

List incidents

List incidents, newest first, filtered by stage, status, severity, type or the day they were declared. Returns one page; pass 'next_cursor' as 'Next page cursor' for more.

Inputs

Stagestatus_categorytext
Only incidents at this stage, such as Active or Closed.One of: triage, live (Active), paused, learning (Post-incident), closed, declined, canceled, merged.
Statusstatus_idtext
Only incidents in this status.
Severityseverity_idtext
Only incidents of this severity.
Typeincident_type_idtext
Only incidents of this type.
Declared on or aftercreated_afterdate
Only incidents declared on or after this day.
Declared on or beforecreated_beforedate
Only incidents declared on or before this day.
Include test incidentsinclude_test_incidentstrue/false
Also list test and tutorial incidents, which are left out otherwise.Default: false.
Orderordertext
Newest or oldest declared first. Defaults to newest first.One of: newest (Newest first (default)), oldest (Oldest first).
Page sizepage_sizenumber
How many to return, 1 to 500. The default is 25.From 1 to 500.
Next page cursoraftertext
The 'next_cursor' from an earlier page, to get the page after it.

Outputs

countnumber
How many are on this page
incidentslist
The incidents
next_cursortext
Pass as 'Next page cursor' to get the next page; empty on the last
total_countnumber
How many match in all, when incident.io says
Example output
{
  "count": 1,
  "incidents": [
    {
      "call_url": "https://zoom.us/j/123",
      "created_at": "2026-10-15T09:00:00Z",
      "id": "01FDAG4SAP5TYPT98WGR2N7W91",
      "incident_role_assignments": [
        {
          "assignee": {
            "email": "jo@example.com",
            "id": "01G0J1EXE7AXZ2C93K61WBPYEH",
            "name": "Jo Bloggs",
            "slack_user_id": "U0123ABC"
          },
          "role": {
            "description": "Runs the response.",
            "id": "01FCNDV6P870EA6S7TK1DSYDG9",
            "name": "Incident Lead",
            "role_type": "lead",
            "shortform": "lead"
          }
        }
      ],
      "incident_status": {
        "category": "live",
        "description": "We are looking into it.",
        "id": "01FCNDV6P870EA6S7TK1DSYD5H",
        "name": "Investigating",
        "rank": 2
      },
      "incident_type": {
        "description": "Something customers can see is broken.",
        "id": "01FCNDV6P870EA6S7TK1DSYDG2",
        "is_default": true,
        "name": "Production outage"
      },
      "mode": "standard",
      "name": "Checkout is failing for some users",
      "permalink": "https://app.incident.io/incidents/123",
      "reference": "INC-123",
      "severity": {
        "description": "Issues causing significant impact.",
        "id": "01FH5TZRWMNAFB0DZ23FD1TV96",
        "name": "Major",
        "rank": 3
      },
      "slack_channel_id": "C02AW36C1M5",
      "slack_channel_name": "inc-123-checkout-is-failing",
      "slack_channel_url": "https://slack.com/app_redirect?channel=C02AW36C1M5",
      "summary": "Card payments fail with a timeout.",
      "updated_at": "2026-10-15T09:00:00Z",
      "visibility": "public"
    }
  ],
  "next_cursor": "",
  "total_count": 1
}

List schedules

List your on-call schedules with who is on call on each right now.

Inputs

Page sizepage_sizenumber
How many to return, 1 to 250. incident.io's default is 25.From 1 to 250.
Next page cursoraftertext
The 'next_cursor' from an earlier page, to get the page after it.

Outputs

countnumber
How many are on this page
next_cursortext
Pass as 'Next page cursor' to get the next page; empty on the last
scheduleslist
The schedules
total_countnumber
How many match in all, when incident.io says
Example output
{
  "count": 1,
  "next_cursor": "",
  "schedules": [
    {
      "created_at": "2026-10-15T09:00:00Z",
      "current_shifts": [
        {
          "end_at": "2026-10-22T00:00:00Z",
          "rotation_id": "01G0J1EXE7AXZ2C93K61WBPYEJ",
          "start_at": "2026-10-15T00:00:00Z",
          "user": {
            "email": "jo@example.com",
            "id": "01G0J1EXE7AXZ2C93K61WBPYEH",
            "name": "Jo Bloggs",
            "slack_user_id": "U0123ABC"
          }
        }
      ],
      "id": "01G0J1EXE7AXZ2C93K61WBPYEK",
      "name": "Primary on-call",
      "permalink": "https://app.incident.io/on-call/schedules/01G0J1EXE7AXZ2C93K61WBPYEK",
      "timezone": "Europe/London",
      "updated_at": "2026-10-15T09:00:00Z"
    }
  ],
  "total_count": 1
}

List users

List the people in your incident.io organization, or find one by email.

Inputs

Emailemailtext
Only the person with this email address.
Include deactivated peopleinclude_inactivetrue/false
Also list people who have been deactivated.Default: false.
Page sizepage_sizenumber
How many to return, 1 to 250. incident.io's default is 25.From 1 to 250.
Next page cursoraftertext
The 'next_cursor' from an earlier page, to get the page after it.

Outputs

countnumber
How many are on this page
next_cursortext
Pass as 'Next page cursor' to get the next page; empty on the last
total_countnumber
How many match in all, when incident.io says
userslist
The people
Example output
{
  "count": 1,
  "next_cursor": "",
  "total_count": 1,
  "users": [
    {
      "base_role": {
        "id": "01G0J1EXE7AXZ2C93K61WBPYEQ",
        "name": "Responder",
        "slug": "responder"
      },
      "email": "jo@example.com",
      "id": "01G0J1EXE7AXZ2C93K61WBPYEH",
      "is_active": true,
      "name": "Jo Bloggs",
      "slack_user_id": "U0123ABC"
    }
  ]
}

Page people

Page people now, through an escalation path or directly, with incident.io's on-call notifications (an escalation).

Inputs

TitletitletextRequired
What the page is about. Everyone paged sees it.
Detailsdescriptiontext
More detail for the people paged.
Escalation pathescalation_path_idtext
Page whoever this escalation path reaches. Choose this or people, not both.
Peoplenotify_user_idslist
Page these people directly. Choose this or an escalation path, not both.
Incident IDincident_idtext
An incident to link the page to.

Outputs

escalationobject
The escalation
Example output
{
  "escalation": {
    "created_at": "2026-10-15T09:00:00Z",
    "description": "The primary is at 100%.",
    "escalation_path_id": "01G0J1EXE7AXZ2C93K61WBPYEP",
    "id": "01G0J1EXE7AXZ2C93K61WBPYEN",
    "priority": {
      "name": "High"
    },
    "status": "triggered",
    "title": "Database is out of disk",
    "updated_at": "2026-10-15T09:00:00Z"
  }
}

Put someone on call

Put a person on call on a schedule for a time window, in place of whoever the rota has (a schedule override).

Inputs

Scheduleschedule_idtextRequired
The on-call schedule.
Personon_call_user_idtextRequired
Who to put on call.
Fromstart_atdate and timeRequired
When they go on call.
Untilend_atdate and timeRequired
When they come off call.
Rotationrotation_idtext
The schedule's rotation to cover. Needed only when it has more than one.

Outputs

overrideobject
The override
Example output
{
  "override": {
    "end_at": "2026-10-20T17:00:00Z",
    "id": "01G0J1EXE7AXZ2C93K61WBPYEL",
    "layer_id": "01G0J1EXE7AXZ2C93K61WBPYEM",
    "rotation_id": "01G0J1EXE7AXZ2C93K61WBPYEJ",
    "schedule_id": "01G0J1EXE7AXZ2C93K61WBPYEK",
    "start_at": "2026-10-20T09:00:00Z",
    "user": {
      "email": "jo@example.com",
      "id": "01G0J1EXE7AXZ2C93K61WBPYEH",
      "name": "Jo Bloggs",
      "slack_user_id": "U0123ABC"
    }
  }
}

Remove on-call override

Remove an override, so the rota decides who is on call again.

Inputs

Override IDoverride_idtextRequired
The override's id, from 'Put someone on call'.

Outputs

deletedtrue/false
Always true once deleted
override_idtext
The override deleted
Example output
{
  "deleted": true,
  "override_id": "01G0J1EXE7AXZ2C93K61WBPYEL"
}

Resolve alert

Mark a firing alert resolved. Alerts from tools that resolve their own, such as Datadog, can only be resolved there.

Inputs

Alert IDalert_idtextRequired
The alert's id, from 'List alerts' or a trigger.

Outputs

alertobject
The alert
Example output
{
  "alert": {
    "alert_source_id": "01GW2G3V0S59R238FAHPDS1R67",
    "created_at": "2026-10-15T09:00:00Z",
    "deduplication_key": "checkout-errors",
    "description": "Errors started at 09:00.",
    "id": "01GW2G3V0S59R238FAHPDS1R66",
    "resolved_at": "2026-10-15T09:00:00Z",
    "source_url": "https://grafana.example.com/d/checkout",
    "status": "resolved",
    "title": "Checkout error rate above 5%",
    "updated_at": "2026-10-15T09:00:00Z"
  }
}

Send alert

Raise (or clear) an alert on one of your HTTP alert sources, so incident.io routes it as it would one from a monitoring tool.

Inputs

Alert sourcealert_source_idtextRequired
The HTTP alert source to send it to, set up in incident.io under On-call > Alerts.
TitletitletextRequired
What is wrong, in a line.
Statusstatustext
Firing raises the alert; resolved clears it. Defaults to firing.One of: firing, resolved.
Descriptiondescriptiontext
More detail. Markdown works.
Deduplication keydeduplication_keytext
A key of your own for this problem. Send the same key again to update the same alert, or with Resolved to clear it.
Linksource_urltext
A link to the problem in the tool that found it.
Extra detailsmetadataobject
Keys and values the alert source is set up to read, such as team.

Outputs

alert_source_idtext
The alert source sent to
deduplication_keytext
The key the alert was recorded under
messagetext
What incident.io did with it
statustext
incident.io's answer, such as success
Example output
{
  "alert_source_id": "01GW2G3V0S59R238FAHPDS1R67",
  "deduplication_key": "checkout-errors",
  "message": "Event accepted for processing",
  "status": "success"
}

Share incident update

Post an update on an incident for everyone following it, and move its status or severity at the same time if you choose.

Inputs

Incident IDincident_idtextRequired
The incident's id, from 'List incidents', 'Declare incident' or a trigger.
Messagemessagetext
What has changed or what is happening now. Markdown works.
New statusincident_status_idtext
Move the incident to this status with the update.
New severityseverity_idtext
Move the incident to this severity with the update.

Outputs

incident_updateobject
The update shared
Example output
{
  "incident_update": {
    "created_at": "2026-10-15T09:00:00Z",
    "id": "01FCNDV6P870EA6S7TK1DSYDG5",
    "incident_id": "01FDAG4SAP5TYPT98WGR2N7W91",
    "message": "We have found the cause and are rolling back.",
    "new_incident_status": {
      "category": "live",
      "description": "We are looking into it.",
      "id": "01FCNDV6P870EA6S7TK1DSYD5H",
      "name": "Investigating",
      "rank": 2
    },
    "new_severity": {
      "description": "Issues causing significant impact.",
      "id": "01FH5TZRWMNAFB0DZ23FD1TV96",
      "name": "Major",
      "rank": 3
    },
    "updater": {
      "user": {
        "email": "jo@example.com",
        "id": "01G0J1EXE7AXZ2C93K61WBPYEH",
        "name": "Jo Bloggs",
        "slack_user_id": "U0123ABC"
      }
    }
  }
}

Update follow-up

Change a follow-up's title, description, status, assignee or labels. Only the fields you fill in change.

Inputs

Follow-up IDfollow_up_idtextRequired
The follow-up's id, from 'List follow-ups' or 'Create follow-up'.
Titletitletext
A new title. Leave empty to keep it.
Descriptiondescriptiontext
A new description. Leave empty to keep it.
Statusstatustext
Outstanding, completed or not doing. Leave empty to keep it.One of: outstanding, completed, not_doing (Not doing).
Assigneeassignee_idtext
Assign it to this person. Leave empty to keep who has it.
Labelslabelslist
Replace its labels with these. Leave empty to keep them.

Outputs

follow_upobject
The follow-up
Example output
{
  "follow_up": {
    "assignee": {
      "email": "jo@example.com",
      "id": "01G0J1EXE7AXZ2C93K61WBPYEH",
      "name": "Jo Bloggs",
      "slack_user_id": "U0123ABC"
    },
    "completed_at": "",
    "created_at": "2026-10-15T09:00:00Z",
    "description": "So we hear before customers do.",
    "id": "01FCNDV6P870EA6S7TK1DSYDG7",
    "incident_id": "01FDAG4SAP5TYPT98WGR2N7W91",
    "labels": [
      "monitoring"
    ],
    "status": "outstanding",
    "title": "Add an alert for checkout errors",
    "updated_at": "2026-10-15T09:00:00Z"
  }
}

Update incident

Change an incident's name, summary, severity, status or call link, or give someone a role. Only the fields you fill in change.

Inputs

Incident IDincident_idtextRequired
The incident's id, from 'List incidents', 'Declare incident' or a trigger.
Namenametext
A new name. Leave empty to keep it.
Summarysummarytext
A new summary. Leave empty to keep it.
Severityseverity_idtext
A new severity. Leave empty to keep it.
Statusincident_status_idtext
A new status. It can move within a stage, from triage or active to post-incident or closed, or from post-incident to closed.
Call linkcall_urltext
The link to the incident's call, such as a Zoom or Meet link.
Role to assignrole_idtext
A role, such as Incident Lead, to give to the person chosen next.
Give the role torole_user_idtext
The person who takes the role chosen.
Tell the incident channelnotify_channeltrue/false
Post the change in the incident's Slack channel.Default: false.

Outputs

incidentobject
The incident
Example output
{
  "incident": {
    "call_url": "https://zoom.us/j/123",
    "created_at": "2026-10-15T09:00:00Z",
    "id": "01FDAG4SAP5TYPT98WGR2N7W91",
    "incident_role_assignments": [
      {
        "assignee": {
          "email": "jo@example.com",
          "id": "01G0J1EXE7AXZ2C93K61WBPYEH",
          "name": "Jo Bloggs",
          "slack_user_id": "U0123ABC"
        },
        "role": {
          "description": "Runs the response.",
          "id": "01FCNDV6P870EA6S7TK1DSYDG9",
          "name": "Incident Lead",
          "role_type": "lead",
          "shortform": "lead"
        }
      }
    ],
    "incident_status": {
      "category": "live",
      "description": "We are looking into it.",
      "id": "01FCNDV6P870EA6S7TK1DSYD5H",
      "name": "Investigating",
      "rank": 2
    },
    "incident_type": {
      "description": "Something customers can see is broken.",
      "id": "01FCNDV6P870EA6S7TK1DSYDG2",
      "is_default": true,
      "name": "Production outage"
    },
    "mode": "standard",
    "name": "Checkout is failing for some users",
    "permalink": "https://app.incident.io/incidents/123",
    "reference": "INC-123",
    "severity": {
      "description": "Issues causing significant impact.",
      "id": "01FH5TZRWMNAFB0DZ23FD1TV96",
      "name": "Major",
      "rank": 3
    },
    "slack_channel_id": "C02AW36C1M5",
    "slack_channel_name": "inc-123-checkout-is-failing",
    "slack_channel_url": "https://slack.com/app_redirect?channel=C02AW36C1M5",
    "summary": "Card payments fail with a timeout.",
    "updated_at": "2026-10-15T09:00:00Z",
    "visibility": "public"
  }
}

Update incident action

Change an action's description, status or assignee, such as marking it completed. Only the fields you fill in change.

Inputs

Action IDincident_action_idtextRequired
The action's id, from 'List incident actions' or 'Create incident action'.
Descriptiondescriptiontext
A new description. Leave empty to keep it.
Statusstatustext
Outstanding, completed or not doing. Leave empty to keep it.One of: outstanding, completed, not_doing (Not doing).
Assigneeassignee_idtext
Assign it to this person. Leave empty to keep who has it.

Outputs

incident_actionobject
The action
Example output
{
  "incident_action": {
    "assignee": {
      "email": "jo@example.com",
      "id": "01G0J1EXE7AXZ2C93K61WBPYEH",
      "name": "Jo Bloggs",
      "slack_user_id": "U0123ABC"
    },
    "completed_at": "",
    "created_at": "2026-10-15T09:00:00Z",
    "description": "Roll back the payments service",
    "id": "01FCNDV6P870EA6S7TK1DSYDG8",
    "incident_id": "01FDAG4SAP5TYPT98WGR2N7W91",
    "status": "outstanding",
    "updated_at": "2026-10-15T09:00:00Z"
  }
}

On this page