incident.io

• New incident.io incidentRuns when an incident is declared in incident.io.
• incident.io incident updatedRuns when anything about an incident changes in incident.io: its name, summary, status, severity, roles or fields.
• incident.io incident status changedRuns when an incident moves to a new status in incident.io, such as from Investigating to Fixing, or is resolved or closed.
• incident.io incident severity changedRuns when an incident's severity is raised or lowered in incident.io.
• New incident.io follow-upRuns when a follow-up is added to an incident in incident.io.
• incident.io follow-up status changedRuns when a follow-up is completed, marked not doing, or reopened in incident.io.
• New incident.io incident actionRuns when an action is added to an incident in incident.io.
• New incident.io alertRuns when an alert fires in incident.io, from any of your alert sources.
• incident.io alert resolvedRuns when an alert is resolved in incident.io.
• New incident.io escalationRuns when someone is paged through incident.io On-call.
• incident.io escalation status changedRuns when a page is acknowledged, resolved, expires or is cancelled in incident.io On-call.
• incident.io on-call changedRuns when who is on call for a schedule changes in incident.io: at a handover, or when someone covers a shift.

• List incidentsList 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.
• Get incidentGet one incident with its status, severity, type, roles and Slack channel.
• Declare incidentDeclare an incident. incident.io opens its Slack channel and runs your workflows as it would for one declared by hand.
• Update incidentChange an incident's name, summary, severity, status or call link, or give someone a role. Only the fields you fill in change.
• 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.
• List incident updatesList the updates shared on an incident, or on every incident.
• Get incident settingsGet the severities, statuses, incident types and roles your organization uses, with their ids.
• List follow-upsList follow-ups (work to do after an incident), on one incident or all, oldest first.
• Get follow-upGet one follow-up with its status, assignee and labels.
• Create follow-upAdd a follow-up to an incident: something to do once it is over.
• Update follow-upChange a follow-up's title, description, status, assignee or labels. Only the fields you fill in change.
• Delete follow-upDelete a follow-up from its incident.
• List incident actionsList actions (tasks to do while an incident is under way), on one incident or all, oldest first.
• Create incident actionAdd an action to an incident: a task to do while it is under way.
• Update incident actionChange an action's description, status or assignee, such as marking it completed. Only the fields you fill in change.
• List alertsList alerts from your monitoring tools, newest first, filtered by status, source or when they fired.
• Get alertGet one alert with its status, source and links.
• Resolve alertMark a firing alert resolved. Alerts from tools that resolve their own, such as Datadog, can only be resolved there.
• 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.
• List schedulesList your on-call schedules with who is on call on each right now.
• Get who is on callFind who is on call for a schedule now, or at a time you choose.
• 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.
• Page peoplePage people now, through an escalation path or directly, with incident.io's on-call notifications (an escalation).
• List escalationsList pages sent to people, filtered by state, escalation path or time.
• List usersList the people in your incident.io organization, or find one by email.

No actions match that.