Sanaf AI
Start free
Developer Tools

incident.io, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your incident.io account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Developer Tools
  • Connects with a key
  • 100 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What incident.io is

Incident management and response platform

You paste in a key from your own incident.io account. It is kept encrypted, and you can withdraw it from inside incident.io whenever you like.

How a run works

One message in, the work done in incident.io.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in incident.io. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own incident.io account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

100 tools it already has

What it can do in incident.io

These are the ready-made tools your AI employee already has in incident.io. It is not limited to them, but it never has to be taught these.

  • Bulk Update Catalog Entries V3Tool to bulk update catalog entries in incident.io v3 API. Use when you need to create or update multiple catalog entries at once for a specific catalog type. This is more efficien
  • Create Alert Attribute V2Tool to create an alert attribute in incident.io. Use when you need to define structured data fields that can be parsed from alerts coming in via alert sources. Alert attributes al
  • Create Alert Route V2Tool to create an alert route in incident.io. Use when you need to configure how alerts should be processed, routed, and potentially converted into incidents based on conditions, g
  • Create Alert Source V2Tool to create a new alert source in incident.io. Use when you need to set up a new integration for receiving alerts from external systems via HTTP webhooks or manual entry.
  • Create Catalog Entry V2Tool to create a catalog entry in incident.io. Use when you need to add a new entry to a catalog type with specific attribute values. Catalog entries represent items like teams, se
  • Create Catalog Entry V3Tool to create a catalog entry in incident.io using the V3 API. Use when you need to add a new entry to a catalog type with specific attribute values. Catalog entries represent ite
  • Create Catalog Type V3Tool to create a new catalog type in incident.io V3 API. Use when you need to define custom resource types for your organization's catalog, such as teams, services, or infrastructu
  • Create Custom Field OptionTool to create a new custom field option in incident.io. Use when you need to add a new selectable value to an existing custom field.
  • Create Custom Field V2Tool to create a custom field in incident.io using the V2 API. Use when you need to add a new custom field to track additional information during incidents.
  • Create Escalation V2Tool to create an escalation in incident.io. Use when you need to page users to respond to alerts. You must specify either an escalationpathid or direct targets (users/schedules).
  • Create Incident RoleTool to create a new incident role in incident.io. Use when you need to define a new role type that can be assigned during incidents. Roles help organize responsibilities and ensur
  • Create Incident Role V2Tool to create a new incident role in incident.io using the V2 API. Use when you need to define a new role type that can be assigned during incidents to organize responsibilities a
  • Create Incident StatusTool to create a new incident status in incident.io. Use when you need to add a custom status for categorizing incidents as 'live' (active), 'learning' (post-incident), or 'closed'
  • Create Incident V1Tool to create a new incident in incident.io. Use when you need to report and track an operational issue or outage. Requires at minimum an idempotencykey and visibility setting.
  • Create Incident V2Tool to create a new incident in incident.io using the V2 API. Use when you need to report and track an operational issue or outage. Requires at minimum an idempotencykey and visib
  • Create Managed Resource V2Tool to create a managed resource in incident.io. Use when you need to mark a resource (schedule, escalation path, or workflow) as being managed by an external system like Terrafor
  • Create SeverityTool to create a new severity level in incident.io. Use when you need to define a new severity classification for incidents with a specific rank and description.
  • Delete Alert Attribute V2Tool to delete an alert attribute from incident.io. Use when you need to remove an alert attribute that is no longer needed or was created in error.
  • Delete Alert Route V2Tool to delete an alert route from incident.io. Use when you need to remove an alert route configuration that is no longer needed or was created in error.
  • Delete Alert Source V2Tool to delete an alert source from incident.io. Use when you need to remove an alert source that is no longer needed or was created in error.
  • Delete Catalog Entry V2Tool to delete a catalog entry from incident.io. Use when you need to remove a catalog entry that is no longer needed.
  • Delete Catalog Entry V3Tool to archive a catalog entry from incident.io using V3 API. Use when you need to remove a catalog entry that is no longer needed. This operation archives the entry from the cata
  • Delete Catalog Type V2Tool to delete a catalog type from incident.io. Use when you need to remove a catalog type that is no longer needed.
  • Delete Catalog Type V3Tool to archive a catalog type and all its entries from incident.io. Use when you need to remove a catalog type that is no longer needed.
  • Delete Custom FieldTool to delete a custom field from incident.io. Use when you need to remove a custom field definition. The deletion is permanent and cannot be undone.
  • Delete Custom Field OptionTool to delete a custom field option in incident.io. Use when you need to permanently remove a custom field option by its ID.
  • Delete Custom Field V2Tool to delete a custom field from incident.io using the V2 API. Use when you need to permanently remove a custom field definition by its ID.
  • Delete Escalation Path V2Tool to delete an escalation path from incident.io. Use when you need to remove an escalation path that is no longer needed or was created in error.
  • Delete Incident Role V1Tool to delete an incident role by ID. Use when you need to remove an incident role from incident.io.
  • Delete Incident Role V2Tool to delete an incident role by ID. Use when you need to permanently remove an incident role from incident.io.
  • Delete Incident Status V1Tool to delete an incident status by its ID. Use when you need to remove an incident status from the system.
  • Delete Schedule V2Tool to delete a schedule from incident.io. Use when you need to remove a schedule that is no longer needed or was created in error.
  • Delete SeverityTool to delete a severity in incident.io. Use when you need to permanently remove a severity level from your incident management configuration.
  • Delete Workflow V2Tool to delete a workflow from incident.io using the V2 API. Use when you need to permanently remove a workflow definition by its ID.
  • Edit Incident V2Tool to edit an existing incident in incident.io. Use when you need to update incident details like name, summary, severity, status, custom fields, or role assignments.
  • Get API Key IdentityTool to retrieve identity information for the current API key. Use to check which organization and roles are associated with the API key.
  • Get Catalog Entry V3Tool to retrieve a specific catalog entry by ID from incident.io. Use when you need to get details about a catalog entry including its attributes and values.
  • Get Catalog Type V2Tool to retrieve a specific catalog type by ID from incident.io. Use when you need to get details about a catalog type's configuration, schema, or metadata.
  • Get Catalog Type V3Tool to retrieve a specific catalog type by ID from incident.io V3 API. Use when you need to get details about a catalog type's configuration, schema, or metadata.
  • Get Custom Field OptionTool to retrieve a specific custom field option by its ID. Use when you need details about a custom field option in incident.io.
  • Get Custom Field V1Tool to retrieve details of a specific custom field by ID in incident.io. Use when you need information about a custom field's configuration, options, or metadata.
  • Get Custom Field V2Tool to retrieve details of a specific custom field by ID using the V2 API in incident.io. Use when you need information about a custom field's configuration or metadata from the V
  • Get Incident by ID (V1)Tool to retrieve a specific incident by ID. Use when you need detailed information about an incident.
  • Get Incident by ID (V2)Tool to retrieve a specific incident by ID using V2 API. Use when you need detailed information about an incident including duration metrics, timestamps, and workload data.
  • Get Incident RoleTool to retrieve a specific incident role by ID. Use when you need to get details about a specific incident role.
  • Get Incident Role V2Tool to retrieve a specific incident role by ID using V2 API. Use when you need to get details about a specific incident role.
  • Get Incident StatusTool to retrieve details of a specific incident status by ID. Use when you need to get information about a particular incident status configuration.
  • Get Incident Timestamp V2Tool to retrieve a specific incident timestamp by ID using V2 API. Use when you need to get details about a specific incident timestamp configuration.
  • Get Incident TypeTool to retrieve detailed information about a specific incident type by ID. Use when you need to view configuration details, settings, or properties of a particular incident type.
  • Get Severity V1Tool to retrieve a specific severity by ID from incident.io. Use when you need to fetch details about a particular severity level.
  • Get User V2Tool to retrieve a specific user by ID from incident.io using V2 API. Use when you need to get detailed information about a user including their role assignments.
  • Get Workflow V2Tool to retrieve a specific workflow by ID from incident.io. Use when you need to get details about a workflow's configuration, steps, conditions, and triggers.
  • List Actions V1Tool to list actions from incidents. Use when you need to retrieve actions associated with incidents, filter by follow-up status, or get actions for a specific incident. By default
  • List Actions V2Tool to retrieve a list of actions from incident.io. Use when you need to view existing actions, optionally filtered by incident ID or incident mode.
  • List Alert Attributes V2Tool to list all available alert attributes. Use when you need to retrieve the schema of attributes that can be used with alerts.
  • List Alert Routes V2Tool to list alert routes from incident.io. Use when you need to retrieve configured alert routes with pagination support.
  • List Alert Sources V2Tool to list all configured alert sources in incident.io. Use when you need to retrieve alert sources that send alerts to incident.io for routing.
  • List Alerts V2Tool to list alerts from incident.io. Use when you need to retrieve alerts for the organisation with pagination support.
  • List Catalog Entries V2Tool to list entries from a catalog type in incident.io. Use when you need to retrieve catalog entries for a specific catalog type with pagination support.
  • List Catalog Entries V3Tool to list entries from a catalog type in incident.io. Use when you need to retrieve catalog entries for a specific catalog type with pagination and filtering support.
  • List Catalog Resources V2Tool to retrieve all available catalog resource types. Use when you need to list the types of data that can be held within the catalog or see what attribute types are available for
  • List Catalog Resources V3Tool to retrieve all available catalog resource types from the V3 API. Use when you need to list the types of data that can be held within the catalog or see what attribute types a
  • List Catalog Types V2Tool to retrieve all catalog types configured for an organization. Use when you need to list available catalog types or understand the catalog schema structure.
  • List Catalog Types V3Tool to retrieve all catalog types configured for an organization using V3 API. Use when you need to list available catalog types or understand the catalog schema structure. This i
  • List Custom Field Options V1Tool to list all options for a specific custom field in incident.io. Use when you need to retrieve available values for dropdown or multi-select custom fields.
  • List Custom Fields V1Tool to list all custom fields for an organization. Use when you need to retrieve the available custom fields and their configurations.
  • List Custom Fields V2Tool to list all custom fields V2 for an organization. Use when you need to retrieve the available custom fields and their configurations using the V2 API.
  • List Escalation Paths V2Tool to list escalation paths from incident.io. Use when you need to retrieve configured escalation paths with pagination support.
  • List Escalations V2Tool to list escalations from incident.io. Use when you need to retrieve escalations for the organisation with pagination support.
  • List Follow-ups V2Tool to retrieve a list of follow-ups from incident.io. Use when you need to view existing follow-ups, optionally filtered by incident ID or incident mode.
  • List Incident Alerts V2Tool to list incident alerts from incident.io. Use when you need to retrieve connections between incidents and alerts with optional filtering by incidentid or alertid.
  • List Incident Attachments V1Tool to list incident attachments from incident.io. Use when you need to retrieve external resources linked to incidents, such as PagerDuty incidents, Jira issues, or GitHub pull r
  • List Incident Relationships V1Tool to list incident relationships for a given incident. Use when you need to retrieve relationships between incidents such as blocking dependencies, causal links, or general asso
  • List Incident Roles V1Tool to list all incident roles for an organization. Use when you need to retrieve available incident roles and their configurations.
  • List Incident Roles V2Tool to list all incident roles for an organization using V2 API. Use when you need to retrieve available incident roles and their configurations.
  • List Incident Statuses V1Tool to list all incident statuses configured for an organization. Use when you need to retrieve available status options for incidents or understand the status workflow.
  • List Incident Timestamps V2Tool to list all incident timestamp configurations using V2 API. Use when you need to retrieve available incident timestamps and their settings.
  • List Incident Types V1Tool to list all incident types for an organization. Use when you need to retrieve available incident types or understand incident type configurations.
  • List Incident Updates V2Tool to list incident updates from incident.io. Use when you need to retrieve updates for incidents with optional filtering by incident ID and pagination support.
  • List Incidents V1Tool to list incidents from incident.io. Use when you need to retrieve incidents with optional filtering by status and pagination support.
  • List Incidents V2Tool to list incidents from incident.io using the V2 API. Use when you need to retrieve incidents with advanced filtering by status, severity, type, timestamps, and pagination supp
  • List IP allowlistsTool to retrieve the current IP allowlist configuration for incident.io. Use when you need to check which IP addresses are allowed to access the incident.io API.
  • List Schedule Entries V2Tool to list schedule entries for a specific schedule in incident.io. Use when you need to retrieve on-call schedule entries for a given time window.
  • List Schedules V2Tool to list schedules from incident.io. Use when you need to retrieve on-call schedules with pagination support.
  • List Severities V1Tool to retrieve all incident severities configured for an organization. Use when you need to list available severity levels for incidents or determine valid severity options for i
  • List Status Pages V2Tool to list status pages from incident.io. Use when you need to retrieve public or customer status pages with pagination support.
  • List Users V2Tool to list users in incident.io. Use when you need to retrieve users with their role information, filter by email or Slack user ID, with pagination support.
  • List Workflows V2Tool to list workflows from incident.io. Use when you need to retrieve configured workflows with pagination support.
  • Show Alert Attribute V2Tool to retrieve a specific alert attribute by its ID from incident.io. Use when you need to get details about an alert attribute such as its type, whether it's required, or if it
  • Show Alert Routes V2Tool to retrieve a specific alert route configuration by its ID from incident.io. Use when you need to view the details of an alert route, including its conditions, escalation bind
  • Show Alert Source V2Tool to retrieve a specific alert source by its ID from incident.io. Use when you need to get details about an alert source configuration including its template and HTTP options.
  • Show Entry Catalog V2Tool to retrieve a specific catalog entry by ID from incident.io. Use when you need to get details about a catalog entry including its attributes, values, and associated catalog ty
  • Show Escalations V2Tool to retrieve a specific escalation by ID from incident.io. Use when you need detailed information about an escalation including its status, priority, creator, events, and relat
  • Show Schedules V2Tool to retrieve a specific schedule by ID from incident.io using V2 API. Use when you need to view details about an on-call schedule, including rotations, shifts, and configuratio
  • Update Alert Attribute V2Tool to update an alert attribute in incident.io. Use when you need to modify the configuration of an existing alert attribute such as changing its name, type, or whether it's requ
  • Update Alert Source V2Tool to update an existing alert source configuration in incident.io. Use when you need to modify alert source properties such as name or template configuration including title, de
  • Update Catalog Entry V2Tool to update an existing catalog entry in incident.io. Use when you need to modify catalog entry properties such as name, attributes, aliases, or ranking.
  • Update Catalog Entry V3Tool to update an existing catalog entry in incident.io using the v3 API. Use when you need to modify catalog entry properties such as name, attributes, aliases, or ranking. Note:
  • Update Catalog Type V2Tool to update a catalog type in incident.io. Use when you need to modify the configuration of an existing catalog type such as its name, description, display settings (color and i
  • Update Catalog Type V3Tool to update a catalog type in incident.io V3 API. Use when you need to modify the configuration of an existing catalog type such as its name, description, annotations, or other
Access, and who is in charge of it

You stay the boss of your incident.io account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own incident.io account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in incident.io is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in incident.io and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about incident.io

Can an AI employee really work inside incident.io?
Yes. It signs in to your own incident.io account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of incident.io?
No. Nothing moves and nothing is replaced. Your records stay in incident.io, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my incident.io account?
You paste in a key from your own incident.io account. It is kept encrypted, and you can withdraw it from inside incident.io whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in incident.io?
It has 100 ready-made tools in incident.io today, among them Bulk Update Catalog Entries V3, Create Alert Attribute V2 and Create Alert Route V2. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use incident.io and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in incident.io and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in incident.io?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in incident.io is written down with what it did and when.