Incident management and response platform
Incident management and response platform On Nagent, incident.io is exposed as a fully-configurable developer tools integration that any agent can call — 86 actions, and API key authentication. No code is required to wire incident.io into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use incident.io to automate the kinds of tasks developer tools teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire incident.io into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against incident.io, with input parameters and output schema. Drop these into any step of an agent built in Helix.
INCIDENT_IO_CREATE_ALERT_ATTRIBUTES_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 allow you to extract and organize information from incoming alerts.
Input parameters
Unique name of this attribute
Engine resource name for this attribute. Common types include 'String' for text values, or 'CatalogEntry\["<catalog_id>"\]' for catalog entry references.
Whether this attribute is an array
Whether this attribute is required. If this field is not set, the existing setting will be preserved.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_CREATE_ALERT_ROUTES_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, grouping rules, and templates.
Input parameters
The name of this alert route config, for the user's reference
Whether this alert route is enabled or not
Version of the alert route configuration
Whether this alert route is private. Private alert routes will only create private incidents from alerts.
The expressions used in this template
Which alert sources should this alert route match?
Channel configuration for this alert route
Incident configuration for this alert route
What condition groups must be true for this alert route to fire?
Escalation configuration for this alert route
Template for incidents created by this alert route
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_CREATE_ALERT_SOURCES_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.
Input parameters
Name of the alert source to be created
Template configuration that defines how alerts from this source should be parsed and formatted. Includes title, description, expressions, and attribute mappings.
Type of alert source. Common types include 'http' for HTTP webhook alerts and 'manual' for manually created alerts.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_CREATE_CATALOG_ENTRIES_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 items like teams, services, or custom resources in your incident management workflow.
Input parameters
Human readable name of this catalog entry
When catalog type is ranked, this is used to help order things
Optional aliases that can be used to reference this entry
An optional alternative ID for this entry, which is ensured to be unique for the type
ID of the catalog type this entry belongs to
Values of this entry, keyed by attribute ID. Each attribute can have either a single value or an array of values. For string attributes use {value: {literal: 'string_value'}}, for references use {value: {literal: 'id', reference: 'type'}}, for arrays use {array_value: \[{literal: 'value'}\]}
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_CREATE_CATALOG_TYPES_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 infrastructure components.
Input parameters
Human readable name of this catalog type
Whether entries in this catalog type can be ranked
The type name of this catalog type, to be used when defining attributes. This is immutable once created. For custom types, it must follow the pattern Custom\["SomeName"\]. If not provided, defaults to the name field.
Categories that this catalog type belongs to for organization purposes
Key-value annotations that can track metadata about this catalog type
Human readable description of this catalog type
URL of the external repository where this catalog type is managed
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_CREATE_CUSTOM_FIELD_OPTIONS_V1Tool 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.
Input parameters
Human readable name for the custom field option
Sort key used to order the custom field options correctly. Lower values appear first.
ID of the custom field this option belongs to
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_CREATE_CUSTOM_FIELDS_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.
Input parameters
Human readable name for the custom field. Maximum 50 characters.
Type of custom field. Determines how the field data is stored and displayed.
Description of the custom field. Provides context about what this field represents.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_CREATE_ESCALATIONS_V2Tool to create an escalation in incident.io. Use when you need to page users to respond to alerts. You must specify either an escalation_path_id or direct targets (users/schedules).
Input parameters
Title for the escalation
Direct targets (users/schedules) to escalate to. Either this or escalation_path_id must be specified.
Priority level for the escalation
Custom message to include with the escalation notification
Unique key to ensure idempotent requests. Use this to prevent accidental duplicate escalations.
ID of escalation path to use. Either this or targets must be specified.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_CREATE_INCIDENT_ROLES_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 and ensure the right people are engaged during incident response.
Input parameters
Human readable name of the incident role
Short human readable name for Slack. Note that this will be empty for the 'reporter' role.
Describes the purpose of the role
Provided to whoever is nominated for the role. Note that this will be empty for the 'reporter' role.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_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'.
Input parameters
Unique name of this status
Whether the status should be considered 'live' (now renamed to active), 'learning' (now renamed to post-incident) or 'closed'. The triage and declined statuses cannot be created or modified.
Rich text description of the incident status
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_CREATE_INCIDENTS_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 idempotency_key and visibility setting. Optionally specify severity, incident type, custom fields, role assignments, and other attributes.
Input parameters
Mode for the incident - whether it's real, test, tutorial, or retrospective.
Explanation of the incident
Detailed description of the incident
Whether the incident should be open to anyone in your Slack workspace (public), or invite-only (private). For more information on Private Incidents see https://help.incident.io/articles/5905558102-can-we-mark-incidents-as-sensitive-and-restrict-access
Severity to create incident as
ID of the Slack team / workspace. This is only required if you are using a Slack Enterprise Grid with multiple teams.
Unique string used to de-duplicate incident create requests. Use this to prevent accidental duplicate incident creation.
Incident type to create this incident as
Incident status to assign to the incident
Set the incident's custom fields to these values
Assign incident roles to these people
Assign the incident's timestamps to these values
Name of the Slack channel to create for this incident
Options for retrospective incidents.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_CREATE_MANAGED_RESOURCES_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 Terraform or a custom automation tool. This helps track which resources are controlled externally and should not be modified through the dashboard.
Input parameters
How this resource is managed (dashboard, terraform, or external tool)
The URL of the external repository where this resource is managed (if applicable)
Annotations that track metadata about this resource. Key-value pairs to store additional information.
The ID of the related resource that you want to mark as managed
The type of the related resource being managed
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_CREATE_SEVERITIES_V1Tool 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.
Input parameters
Human readable name of the severity
Rank to help sort severities (lower numbers are less severe)
Description of the severity
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_DELETE_ALERT_ATTRIBUTES_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.
Input parameters
The unique identifier of the alert attribute to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_DELETE_ALERT_ROUTES_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.
Input parameters
Unique identifier for this alert route config
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_DELETE_ALERT_SOURCES_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.
Input parameters
The unique identifier of the alert source to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_DELETE_CATALOG_ENTRIES_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 catalog.
Input parameters
ID of the catalog entry to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_DELETE_CATALOG_TYPES_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.
Input parameters
ID of the catalog type to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_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.
Input parameters
Unique identifier for the custom field to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_DELETE_CUSTOM_FIELD_OPTIONS_V1Tool to delete a custom field option in incident.io. Use when you need to permanently remove a custom field option by its ID.
Input parameters
Unique identifier for the custom field option to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_DELETE_CUSTOM_FIELDS_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.
Input parameters
Unique identifier for the custom field to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_DELETE_ESCALATION_PATHS_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.
Input parameters
Unique identifier for this escalation path.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_DELETE_INCIDENT_ROLES_V2Tool to delete an incident role by ID. Use when you need to permanently remove an incident role from incident.io.
Input parameters
Unique identifier for the incident role to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
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.
Input parameters
Unique ID of the incident status to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_DELETE_SCHEDULES_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.
Input parameters
Unique internal ID of the schedule to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_DELETE_SEVERITYTool to delete a severity in incident.io. Use when you need to permanently remove a severity level from your incident management configuration.
Input parameters
Unique identifier of the severity to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_DELETE_WORKFLOWS_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.
Input parameters
Unique identifier for the workflow to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_EDIT_INCIDENTS_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.
Input parameters
The unique identifier of the incident that you want to edit
Incident fields to update
Should we send Slack channel notifications to inform responders of this update? Note that this won't work if the Slack channel has already been archived.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_GET_ALERT_ATTRIBUTES_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 accepts arrays.
Input parameters
The unique identifier for the alert attribute to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_GET_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 bindings, and incident template.
Input parameters
Unique identifier for this alert route config
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_GET_ALERT_SOURCES_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.
Input parameters
The unique identifier of the alert source to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_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.
Input parameters
ID of the catalog entry to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_GET_CATALOG_TYPES_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.
Input parameters
ID of the catalog type to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_GET_CUSTOM_FIELD_OPTIONS_V1Tool to retrieve a specific custom field option by its ID. Use when you need details about a custom field option in incident.io.
Input parameters
Unique identifier for the custom field option
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
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.
Input parameters
Unique identifier for the custom field
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_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 V2 endpoint.
Input parameters
Unique identifier for the custom field
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_GET_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 related incidents/alerts.
Input parameters
Unique identifier for the escalation to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_GET_INCIDENT_ROLES_V2Tool to retrieve a specific incident role by ID using V2 API. Use when you need to get details about a specific incident role.
Input parameters
Unique identifier for the role
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_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.
Input parameters
Unique ID of the incident status to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_GET_INCIDENT_TIMESTAMPS_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.
Input parameters
Unique ID of this incident timestamp
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_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.
Input parameters
Unique identifier for this Incident Type
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_GET_INCIDENT_V2Tool 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.
Input parameters
Unique identifier for the incident
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_GET_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 configuration.
Input parameters
Unique internal ID of the schedule
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_GET_SEVERITIES_V1Tool to retrieve a specific severity by ID from incident.io. Use when you need to fetch details about a particular severity level.
Input parameters
Unique identifier of the severity to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_GET_USERS_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.
Input parameters
Unique identifier of the user
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_GET_WORKFLOWS_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.
Input parameters
Unique identifier for the workflow
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_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 returns actions from 'real' incidents only.
Input parameters
Find actions related to this specific incident by its ID.
Filter to actions marked as being follow up actions. Set to true to get only follow-up actions, false for non-follow-up actions.
Mode of incidents to filter by.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_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.
Input parameters
Find actions related to this incident
Incident mode filter options.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_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.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_LIST_ALERT_ROUTES_V2Tool to list alert routes from incident.io. Use when you need to retrieve configured alert routes with pagination support.
Input parameters
Cursor for pagination - the ID of the last alert route on the previous page
Number of alert routes to return per page. Must be between 1 and 50.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_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.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_LIST_ALERTS_V2Tool to list alerts from incident.io. Use when you need to retrieve alerts for the organisation with pagination support.
Input parameters
Cursor for pagination - the ID of the last alert on the previous page
Number of alerts to return per page. Must be at least 1.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_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.
Input parameters
Cursor for pagination. Pass the value from pagination_meta.after to load the next page.
Number of records per page to return (required by API)
Filter entries by identifier (alias). Searches across ID, external ID, aliases, or name.
ID of the catalog type to retrieve entries for
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_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 are available for updating catalog type schemas.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_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 includes both synced types backed by external resources and custom catalog types.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_LIST_ESCALATION_PATHS_V2Tool to list escalation paths from incident.io. Use when you need to retrieve configured escalation paths with pagination support.
Input parameters
Cursor for pagination - the ID of the last escalation path on the previous page
Number of escalation paths to return per page. Must be between 1 and 25.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_LIST_ESCALATIONS_V2Tool to list escalations from incident.io. Use when you need to retrieve escalations for the organisation with pagination support.
Input parameters
Cursor for pagination - the ID of the last escalation on the previous page
Number of escalations to return per page. Must be at least 1.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_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.
Input parameters
Find follow-ups related to this incident
Incident mode filter options.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_LIST_IDENTITY_V1Tool to retrieve identity information for the current API key. Use to check which organization and roles are associated with the API key.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_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 incident_id or alert_id.
Input parameters
Filter by alert_id to find the incident that a particular alert triggered
Number of incident alerts to return per page. Must be at least 1.
Filter by incident_id to find all alerts attached to a particular incident
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_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 requests. Filter by incident ID, external resource ID, or resource type to narrow results.
Input parameters
Filter by the ID of the resource in the external system (e.g., PagerDuty incident ID, Jira issue key).
Filter attachments by incident ID. Use this to retrieve all attachments for a specific incident.
Enum for external resource types that can be attached to incidents.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_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 associations.
Input parameters
Cursor for pagination. Pass a record ID to get the next page.
Number of results per page. Default: 25, max: 250.
The ID of the incident to fetch relationships for
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_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.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_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 support.
Input parameters
An incident's ID. This endpoint will return a list of incidents after this ID in relation to the API response order.
Number of records to return per page
Filter for incidents with mode in this list (e.g., 'standard', 'retrospective', 'test', 'tutorial'). Defaults to \['standard', 'retrospective'\] if not provided.
Filter for incidents with severity rank greater than or equal to this severity ID. Use operator 'gte'.
Filter for incidents with severity rank less than or equal to this severity ID. Use operator 'lte'.
Filter for incidents with status IDs not in this list. Use operator 'not_in'.
Filter for incidents with status IDs in this list. Use operator 'one_of'.
Filter for incidents created at or after this ISO 8601 timestamp. Use operator 'gte'.
Filter for incidents created at or before this ISO 8601 timestamp. Use operator 'lte'.
Filter for incidents updated at or after this ISO 8601 timestamp. Use operator 'gte'.
Filter for incidents updated at or before this ISO 8601 timestamp. Use operator 'lte'.
Filter for incidents with severity IDs not in this list. Use operator 'not_in'.
Filter for incidents with severity IDs in this list. Use operator 'one_of'.
Filter for incidents with incident type IDs not in this list. Use operator 'not_in'.
Filter for incidents with incident type IDs in this list. Use operator 'one_of'.
Filter for incidents with status category not in this list. Use operator 'not_in'.
Filter for incidents with status category in this list (e.g., 'triage', 'live', 'closed'). Use operator 'one_of'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_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.
Input parameters
An record's ID. This endpoint will return a list of records after this ID in relation to the API response order.
Number of records to return per page. Must be at least 1.
Incident whose updates you want to list
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_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.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_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.
Input parameters
The ID of the schedule to get entries for.
The end of the window to get entries for. ISO 8601 timestamp.
The start of the window to get entries for. ISO 8601 timestamp.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_LIST_SCHEDULES_V2Tool to list schedules from incident.io. Use when you need to retrieve on-call schedules with pagination support.
Input parameters
A schedule's ID. This endpoint will return a list of schedules after this ID in relation to the API response order.
Integer number of records to return
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_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.
Input parameters
A status page's ID. This endpoint will return a list of status pages after this ID in relation to the API response order.
Integer number of records to return
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_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.
Input parameters
An record's ID. This endpoint will return a list of records after this ID in relation to the API response order.
Filter by email address
Integer number of records to return
Filter by Slack user ID
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_LIST_WORKFLOWS_V2Tool to list workflows from incident.io. Use when you need to retrieve configured workflows with pagination support.
Input parameters
Cursor for pagination - the ID of the last workflow on the previous page
Number of workflows to return per page. Must be at least 1.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_UPDATE_ALERT_ATTRIBUTES_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 required or an array.
Input parameters
The unique identifier of the alert attribute to update
Unique name of this attribute
Engine resource name for this attribute. Common types include 'String' for text values, or 'CatalogEntry\["<catalog_id>"\]' for catalog entry references.
Whether this attribute is an array
Whether this attribute is required
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_UPDATE_ALERT_SOURCES_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, description, expressions, and attributes.
Input parameters
Unique identifier of the alert source to update. This is a required path parameter.
Human-readable name for the alert source that will be displayed in the UI
Template configuration that defines how alerts from this source are processed and displayed
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_UPDATE_CATALOG_ENTRIES_BULK_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 efficient than updating entries individually. The API returns 204 No Content on success.
Input parameters
Array of entries to create or update. Each entry must include an entry_id, name, and attribute_values.
How to handle entries not in the payload. Use 'delete_matching_on_rules' to delete entries that match certain rules but are not in this payload.
ID of the catalog type to bulk update entries for
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_UPDATE_CATALOG_ENTRIES_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: All attribute values must be provided - any not specified will be cleared.
Input parameters
ID of the catalog entry to update. This is the unique identifier for the entry.
Name is the human readable name of this entry. This is a required field.
When catalog type is ranked, this is used to help order things. Lower numbers appear first.
Optional aliases that can be used to reference this entry. These provide alternative identifiers for the entry.
An optional alternative ID for this entry, which is ensured to be unique for the type. Useful for integration with external systems.
Values of this entry. A dictionary where keys are attribute IDs and values are the attribute bindings. All attribute values must be provided - any not specified will be cleared.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_UPDATE_CATALOG_TYPES_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 properties.
Input parameters
ID of the catalog type to update
Name of the catalog type
Whether entries can be ranked
Categories for organization
Key-value annotations
Description of the catalog type
URL of the source repository
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_UPDATE_CUSTOM_FIELD_OPTION_V1Tool to update a custom field option in incident.io. Use when you need to modify the value, sort order, or parent custom field of an existing option.
Input parameters
Unique identifier for the custom field option to update
Human readable name for the custom field option
Sort key used to order the custom field options correctly. Lower values appear first. Defaults to 1000 if not specified.
ID of the custom field this option belongs to
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_UPDATE_CUSTOM_FIELDS_V1Tool to update an existing custom field configuration in incident.io. Use when you need to modify custom field properties such as name, description, visibility settings, or requirement rules.
Input parameters
Unique identifier for the custom field to update. This is a required path parameter.
Human readable name for the custom field. Maximum 50 characters.
When this custom field must be set during the incident lifecycle (deprecated).
Description of the custom field explaining its purpose.
When this custom field must be set during the incident lifecycle.
Whether a custom field should be shown in the incident update modal.
Whether a custom field should be shown in the incident resolve modal. If this custom field is required before resolution, but no value has been set for it, the field will be shown in the resolve modal whatever the value of this setting.
Whether a custom field should be shown in the incident creation modal. This must be true if the field is always required.
Whether a custom field should be shown in the list of fields as part of the announcement post when set.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_UPDATE_CUSTOM_FIELDS_V2Tool to update an existing custom field in incident.io using the V2 API. Use when you need to modify the name or description of a custom field.
Input parameters
Unique identifier for the custom field to update. This is a required path parameter.
Human readable name for the custom field. Maximum 50 characters.
Description of the custom field explaining its purpose.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_UPDATE_ESCALATION_PATHS_V2Tool to update an escalation path in incident.io. Use when you need to modify the configuration of an existing escalation path, including its name, escalation levels, targets, conditions, or working hours.
Input parameters
Unique identifier for the escalation path to update
The name of this escalation path, for the user's reference
The nodes that form the levels and branches of this escalation path
List of team IDs that this escalation path is associated with
The working hours for this escalation path
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_UPDATE_INCIDENT_ROLES_V2Tool to update an existing incident role in incident.io using the V2 API. Use when you need to modify the name, description, instructions, or shortform of an incident role.
Input parameters
Unique identifier for the role to update
Human readable name of the incident role
Short human readable name for Slack. Note that this will be empty for the 'reporter' role.
Describes the purpose of the role
Provided to whoever is nominated for the role. Note that this will be empty for the 'reporter' role.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_UPDATE_INCIDENT_STATUSTool to update an existing incident status in incident.io. Use when you need to modify the name or description of an incident status. Note that only live and learning statuses can be fully configured.
Input parameters
Unique ID of the incident status to update
Unique name of this status
Rich text description of the incident status
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_UPDATE_SCHEDULES_V2Tool to update an existing schedule in incident.io. Use when you need to modify schedule properties such as name, timezone, rotations, layers, or holiday configurations.
Input parameters
Unique identifier for the schedule to update
Schedule properties to update
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_UPDATE_SCHEMA_CATALOG_TYPES_V3Tool to update the schema of a catalog type in incident.io V3 API. Use when you need to add, modify, or remove attributes from a catalog type's schema. The version parameter must match the current schema version.
Input parameters
ID of the catalog type to update schema for
Version number of the schema. Must match the current version to prevent conflicts.
List of attributes that define the schema. This replaces the entire schema, so include all attributes you want to keep.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_UPDATE_SEVERITIES_V1Tool to update a severity in incident.io. Use when you need to modify the name, description, or rank of an existing severity level.
Input parameters
Unique identifier of the severity to update.
Human readable name of the severity.
Rank to help sort severities (lower numbers are less severe).
Description of the severity. Supports Markdown formatting.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INCIDENT_IO_UPDATE_WORKFLOWS_V2Tool to update an existing workflow in incident.io using the V2 API. Use when you need to modify workflow configuration including name, conditions, steps, expressions, and execution settings.
Input parameters
Unique identifier of the workflow to update. This is a required path parameter.
The human-readable name of the workflow.
Delay configuration for workflow execution.
Enum for workflow state.
List of steps to execute as part of the workflow.
Folder to display the workflow in.
Once For strategy to apply to this workflow. List of references that determine uniqueness.
Shortform used to trigger manual workflows in Slack - e.g. `/inc workflows page-ceo`.
Annotations that track metadata about this resource.
The expressions used in the workflow.
List of conditions to apply to the workflow.
Which incidents should the workflow be applied to? (newly_created or newly_created_and_active).
Whether to continue executing the workflow if a step fails.
Which modes of incident this should run on (defaults to just standard incidents).
Whether to include private incidents.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 73 agents privately built on Nagent that already use incident.io.
Build on Nagent
Connect incident.io to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find incident.io, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, incident.io is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once incident.io is connected, you configure its 86 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop incident.io steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a incident.io event fires, the agent kicks off automatically.
Every incident.io action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While incident.io ships with 86 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching incident.io together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build incident.io-based workflows tailored to your business.