Connect Claude & ChatGPT to incident.io

25 tools for incident.io

These tools are switched on when you connect. You can switch any of them off, or require your approval before it runs.

• create_follow_upChanges dataCreate a follow-up on an incident: `incident_id` and `title`, with optional description, assignee, team, priority and labels.
• create_incident_actionChanges dataCreate an action on an incident: `incident_id`, `description`, and an optional `assignee_id`.
• declare_incidentChanges dataDeclare a new incident with `name`, `summary`, `severity_id`, `visibility` (public or private) and a unique `idempotency_key`; optional incident type, status and role assignments. This creates a Slack channel and may page and notify people.
• find_usersFind users by `email` or `slack_user_id`, or list all users. Use this to get user IDs for assignments.
• get_api_identityGet the identity of the connected API key: organisation name and the roles it has.
• get_follow_upGet one follow-up by `follow_up_id`.
• get_incidentGet one incident by `incident_id`, including name, summary, status, severity, roles, custom fields and Slack channel.
• list_follow_upsList follow-ups, filtered by `incident_id` or assignee team.
• list_incident_actionsList incident actions (to-dos during an incident), filtered by `incident_id`.
• list_incident_activityList the activity log of an incident (`incident_id`): status changes, messages, role changes and more.
• list_incident_participantsList the people involved in an incident (`incident_id`).
• list_incident_rolesList the incident roles (for example incident lead) configured in your organisation.
• list_incident_statusesList the incident statuses configured in your organisation, with IDs and categories.
• list_incident_typesList the incident types configured in your organisation.
• list_incident_updatesList the updates shared on an incident (`incident_id`).
• list_incidentsList incidents, newest first by default. Filters are operator objects, for example `status_category` {"oneof": ["active"]} or `severity` {"oneof": [severity ID]}, plus created_at/updated_at ranges.
• list_on_call_entriesList who is on call for a schedule (`schedule_id`), optionally between `entry_window_start` and `entry_window_end`.
• list_on_call_schedulesList on-call schedules with their IDs, names and time zones.
• list_postmortemsList post-mortem documents, optionally for one `incident_id`.
• list_severitiesList the severity levels configured in your organisation, with IDs and ranks.
• list_teamsList the teams in your organisation.
• post_incident_updateChanges dataShare an update on an incident: `incident_id`, a unique `idempotency_key`, a Markdown `message`, and optionally a new severity or status. This is posted to the incident channel and subscribers.
• update_follow_upChanges dataUpdate a follow-up by `follow_up_id`. `title` and `status` (outstanding, completed or not_doing) are required; optionally change description, assignee or priority.
• update_incidentChanges dataEdit an incident by `incident_id`: pass the changes in `incident` (name, summary, severity_id, incident_status_id, role assignments, custom fields) and `notify_incident_channel` to choose whether Slack is notified.
• update_incident_actionChanges dataUpdate an incident action by `document_id` (the action ID): `description` and `status` (outstanding, completed or not_doing) are required; `assignee_id` is optional.

Questions