# incident.io

Incident management and response platform

- **Category:** developer tools
- **Auth:** API_KEY
- **Composio Managed App Available?** N/A
- **Tools:** 86
- **Triggers:** 0
- **Slug:** `INCIDENT_IO`
- **Version:** 20260312_00

## Tools

### Create Alert Attribute V2

**Slug:** `INCIDENT_IO_CREATE_ALERT_ATTRIBUTES_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | Yes | Unique name of this attribute |
| `type` | string | Yes | Engine resource name for this attribute. Common types include 'String' for text values, or 'CatalogEntry["<catalog_id>"]' for catalog entry references. |
| `array` | boolean | Yes | Whether this attribute is an array |
| `required` | boolean | Yes | Whether this attribute is required. If this field is not set, the existing setting will be preserved. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Alert Route V2

**Slug:** `INCIDENT_IO_CREATE_ALERT_ROUTES_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | Yes | The name of this alert route config, for the user's reference |
| `enabled` | boolean | Yes | Whether this alert route is enabled or not |
| `version` | integer | No | Version of the alert route configuration |
| `is_private` | boolean | Yes | Whether this alert route is private. Private alert routes will only create private incidents from alerts. |
| `expressions` | array | No | The expressions used in this template |
| `alert_sources` | array | No | Which alert sources should this alert route match? |
| `channel_config` | array | No | Channel configuration for this alert route |
| `incident_config` | object | Yes | Incident configuration for this alert route |
| `condition_groups` | array | No | What condition groups must be true for this alert route to fire? |
| `escalation_config` | object | Yes | Escalation configuration for this alert route |
| `incident_template` | object | Yes | Template for incidents created by this alert route |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Alert Source V2

**Slug:** `INCIDENT_IO_CREATE_ALERT_SOURCES_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | Yes | Name of the alert source to be created |
| `template` | object | Yes | Template configuration that defines how alerts from this source should be parsed and formatted. Includes title, description, expressions, and attribute mappings. |
| `source_type` | string | Yes | Type of alert source. Common types include 'http' for HTTP webhook alerts and 'manual' for manually created alerts. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Catalog Entry V3

**Slug:** `INCIDENT_IO_CREATE_CATALOG_ENTRIES_V3`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | Yes | Human readable name of this catalog entry |
| `rank` | integer | No | When catalog type is ranked, this is used to help order things |
| `aliases` | array | No | Optional aliases that can be used to reference this entry |
| `external_id` | string | No | An optional alternative ID for this entry, which is ensured to be unique for the type |
| `catalog_type_id` | string | Yes | ID of the catalog type this entry belongs to |
| `attribute_values` | object | Yes | 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Catalog Type V3

**Slug:** `INCIDENT_IO_CREATE_CATALOG_TYPES_V3`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | Yes | Human readable name of this catalog type |
| `ranked` | boolean | No | Whether entries in this catalog type can be ranked |
| `type_name` | string | No | 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` | array | No | Categories that this catalog type belongs to for organization purposes |
| `annotations` | object | No | Key-value annotations that can track metadata about this catalog type |
| `description` | string | Yes | Human readable description of this catalog type |
| `source_repo_url` | string | No | URL of the external repository where this catalog type is managed |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Custom Field Option

**Slug:** `INCIDENT_IO_CREATE_CUSTOM_FIELD_OPTIONS_V1`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `value` | string | Yes | Human readable name for the custom field option |
| `sort_key` | integer | No | Sort key used to order the custom field options correctly. Lower values appear first. |
| `custom_field_id` | string | Yes | ID of the custom field this option belongs to |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Custom Field V2

**Slug:** `INCIDENT_IO_CREATE_CUSTOM_FIELDS_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | Yes | Human readable name for the custom field. Maximum 50 characters. |
| `field_type` | string ("single_select" | "multi_select" | "text" | "link" | "numeric") | Yes | Type of custom field. Determines how the field data is stored and displayed. |
| `description` | string | Yes | Description of the custom field. Provides context about what this field represents. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Escalation V2

**Slug:** `INCIDENT_IO_CREATE_ESCALATIONS_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `title` | string | Yes | Title for the escalation |
| `targets` | array | No | Direct targets (users/schedules) to escalate to. Either this or escalation_path_id must be specified. |
| `priority` | string | No | Priority level for the escalation |
| `custom_message` | string | No | Custom message to include with the escalation notification |
| `idempotency_key` | string | Yes | Unique key to ensure idempotent requests. Use this to prevent accidental duplicate escalations. |
| `escalation_path_id` | string | No | ID of escalation path to use. Either this or targets must be specified. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Incident Role V2

**Slug:** `INCIDENT_IO_CREATE_INCIDENT_ROLES_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | Yes | Human readable name of the incident role |
| `shortform` | string | Yes | Short human readable name for Slack. Note that this will be empty for the 'reporter' role. |
| `description` | string | Yes | Describes the purpose of the role |
| `instructions` | string | Yes | Provided to whoever is nominated for the role. Note that this will be empty for the 'reporter' role. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Incident Status

**Slug:** `INCIDENT_IO_CREATE_INCIDENT_STATUS`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | Yes | Unique name of this status |
| `category` | string ("live" | "learning" | "closed") | Yes | 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. |
| `description` | string | Yes | Rich text description of the incident status |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Incident V2

**Slug:** `INCIDENT_IO_CREATE_INCIDENTS_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `mode` | string ("standard" | "retrospective" | "test" | "tutorial") | No | Mode for the incident - whether it's real, test, tutorial, or retrospective. |
| `name` | string | No | Explanation of the incident |
| `summary` | string | No | Detailed description of the incident |
| `visibility` | string ("public" | "private") | Yes | 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_id` | string | No | Severity to create incident as |
| `slack_team_id` | string | No | ID of the Slack team / workspace. This is only required if you are using a Slack Enterprise Grid with multiple teams. |
| `idempotency_key` | string | Yes | Unique string used to de-duplicate incident create requests. Use this to prevent accidental duplicate incident creation. |
| `incident_type_id` | string | No | Incident type to create this incident as |
| `incident_status_id` | string | No | Incident status to assign to the incident |
| `custom_field_entries` | array | No | Set the incident's custom fields to these values |
| `incident_role_assignments` | array | No | Assign incident roles to these people |
| `incident_timestamp_values` | array | No | Assign the incident's timestamps to these values |
| `slack_channel_name_override` | string | No | Name of the Slack channel to create for this incident |
| `retrospective_incident_options` | object | No | Options for retrospective incidents. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Managed Resource V2

**Slug:** `INCIDENT_IO_CREATE_MANAGED_RESOURCES_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `managed_by` | string ("dashboard" | "terraform" | "external") | Yes | How this resource is managed (dashboard, terraform, or external tool) |
| `source_url` | string | No | The URL of the external repository where this resource is managed (if applicable) |
| `annotations` | object | Yes | Annotations that track metadata about this resource. Key-value pairs to store additional information. |
| `resource_id` | string | Yes | The ID of the related resource that you want to mark as managed |
| `resource_type` | string ("escalation_path" | "schedule" | "workflow") | Yes | The type of the related resource being managed |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Severity

**Slug:** `INCIDENT_IO_CREATE_SEVERITIES_V1`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | Yes | Human readable name of the severity |
| `rank` | integer | No | Rank to help sort severities (lower numbers are less severe) |
| `description` | string | Yes | Description of the severity |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Alert Attribute V2

**Slug:** `INCIDENT_IO_DELETE_ALERT_ATTRIBUTES_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | The unique identifier of the alert attribute to delete |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Alert Route V2

**Slug:** `INCIDENT_IO_DELETE_ALERT_ROUTES_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier for this alert route config |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Alert Source V2

**Slug:** `INCIDENT_IO_DELETE_ALERT_SOURCES_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | The unique identifier of the alert source to delete |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Catalog Entry V3

**Slug:** `INCIDENT_IO_DELETE_CATALOG_ENTRIES_V3`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | ID of the catalog entry to delete |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Catalog Type V3

**Slug:** `INCIDENT_IO_DELETE_CATALOG_TYPES_V3`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | ID of the catalog type to delete |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Custom Field

**Slug:** `INCIDENT_IO_DELETE_CUSTOM_FIELD`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier for the custom field to delete. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Custom Field Option

**Slug:** `INCIDENT_IO_DELETE_CUSTOM_FIELD_OPTIONS_V1`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier for the custom field option to delete |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Custom Field V2

**Slug:** `INCIDENT_IO_DELETE_CUSTOM_FIELDS_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier for the custom field to delete |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Escalation Path V2

**Slug:** `INCIDENT_IO_DELETE_ESCALATION_PATHS_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier for this escalation path. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Incident Role V2

**Slug:** `INCIDENT_IO_DELETE_INCIDENT_ROLES_V2`

Tool to delete an incident role by ID. Use when you need to permanently remove an incident role from incident.io.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier for the incident role to delete |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Incident Status V1

**Slug:** `INCIDENT_IO_DELETE_INCIDENT_STATUS_V1`

Tool to delete an incident status by its ID. Use when you need to remove an incident status from the system.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique ID of the incident status to delete. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Schedule V2

**Slug:** `INCIDENT_IO_DELETE_SCHEDULES_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique internal ID of the schedule to delete |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Severity

**Slug:** `INCIDENT_IO_DELETE_SEVERITY`

Tool to delete a severity in incident.io. Use when you need to permanently remove a severity level from your incident management configuration.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier of the severity to delete. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Workflow V2

**Slug:** `INCIDENT_IO_DELETE_WORKFLOWS_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier for the workflow to delete |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Edit Incident V2

**Slug:** `INCIDENT_IO_EDIT_INCIDENTS_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | The unique identifier of the incident that you want to edit |
| `incident` | object | Yes | Incident fields to update |
| `notify_incident_channel` | boolean | Yes | 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Alert Attribute V2

**Slug:** `INCIDENT_IO_GET_ALERT_ATTRIBUTES_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | The unique identifier for the alert attribute to retrieve |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Alert Routes V2

**Slug:** `INCIDENT_IO_GET_ALERT_ROUTES_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier for this alert route config |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Alert Source V2

**Slug:** `INCIDENT_IO_GET_ALERT_SOURCES_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | The unique identifier of the alert source to retrieve |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Catalog Entry V3

**Slug:** `INCIDENT_IO_GET_CATALOG_ENTRY_V3`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | ID of the catalog entry to retrieve |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Catalog Type V3

**Slug:** `INCIDENT_IO_GET_CATALOG_TYPES_V3`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | ID of the catalog type to retrieve |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Custom Field Option

**Slug:** `INCIDENT_IO_GET_CUSTOM_FIELD_OPTIONS_V1`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier for the custom field option |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Custom Field V1

**Slug:** `INCIDENT_IO_GET_CUSTOM_FIELD_V1`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier for the custom field |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Custom Field V2

**Slug:** `INCIDENT_IO_GET_CUSTOM_FIELD_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier for the custom field |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Escalations V2

**Slug:** `INCIDENT_IO_GET_ESCALATIONS_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier for the escalation to retrieve |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Incident Role V2

**Slug:** `INCIDENT_IO_GET_INCIDENT_ROLES_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier for the role |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Incident Status

**Slug:** `INCIDENT_IO_GET_INCIDENT_STATUS`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique ID of the incident status to retrieve |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Incident Timestamp V2

**Slug:** `INCIDENT_IO_GET_INCIDENT_TIMESTAMPS_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique ID of this incident timestamp |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Incident Type

**Slug:** `INCIDENT_IO_GET_INCIDENT_TYPE`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier for this Incident Type |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Incident by ID (V2)

**Slug:** `INCIDENT_IO_GET_INCIDENT_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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier for the incident |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Show Schedules V2

**Slug:** `INCIDENT_IO_GET_SCHEDULES_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique internal ID of the schedule |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Severity V1

**Slug:** `INCIDENT_IO_GET_SEVERITIES_V1`

Tool to retrieve a specific severity by ID from incident.io. Use when you need to fetch details about a particular severity level.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier of the severity to retrieve |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get User V2

**Slug:** `INCIDENT_IO_GET_USERS_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier of the user |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Workflow V2

**Slug:** `INCIDENT_IO_GET_WORKFLOWS_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier for the workflow |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Actions V1

**Slug:** `INCIDENT_IO_LIST_ACTIONS_V1`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `incident_id` | string | No | Find actions related to this specific incident by its ID. |
| `is_follow_up` | boolean | No | Filter to actions marked as being follow up actions. Set to true to get only follow-up actions, false for non-follow-up actions. |
| `incident_mode` | string ("real" | "test" | "tutorial") | No | Mode of incidents to filter by. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Actions V2

**Slug:** `INCIDENT_IO_LIST_ACTIONS_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `incident_id` | string | No | Find actions related to this incident |
| `incident_mode` | string ("standard" | "retrospective" | "test" | "tutorial" | "stream") | No | Incident mode filter options. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Alert Attributes V2

**Slug:** `INCIDENT_IO_LIST_ALERT_ATTRIBUTES_V2`

Tool to list all available alert attributes. Use when you need to retrieve the schema of attributes that can be used with alerts.

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Alert Routes V2

**Slug:** `INCIDENT_IO_LIST_ALERT_ROUTES_V2`

Tool to list alert routes from incident.io. Use when you need to retrieve configured alert routes with pagination support.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `after` | string | No | Cursor for pagination - the ID of the last alert route on the previous page |
| `page_size` | integer | No | Number of alert routes to return per page. Must be between 1 and 50. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Alert Sources V2

**Slug:** `INCIDENT_IO_LIST_ALERT_SOURCES_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Alerts V2

**Slug:** `INCIDENT_IO_LIST_ALERTS_V2`

Tool to list alerts from incident.io. Use when you need to retrieve alerts for the organisation with pagination support.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `after` | string | No | Cursor for pagination - the ID of the last alert on the previous page |
| `page_size` | integer | No | Number of alerts to return per page. Must be at least 1. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Catalog Entries V3

**Slug:** `INCIDENT_IO_LIST_CATALOG_ENTRIES_V3`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `after` | string | No | Cursor for pagination. Pass the value from pagination_meta.after to load the next page. |
| `page_size` | integer | Yes | Number of records per page to return (required by API) |
| `identifier` | string | No | Filter entries by identifier (alias). Searches across ID, external ID, aliases, or name. |
| `catalog_type_id` | string | Yes | ID of the catalog type to retrieve entries for |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Catalog Resources V3

**Slug:** `INCIDENT_IO_LIST_CATALOG_RESOURCES_V3`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Catalog Types V3

**Slug:** `INCIDENT_IO_LIST_CATALOG_TYPES_V3`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Escalation Paths V2

**Slug:** `INCIDENT_IO_LIST_ESCALATION_PATHS_V2`

Tool to list escalation paths from incident.io. Use when you need to retrieve configured escalation paths with pagination support.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `after` | string | No | Cursor for pagination - the ID of the last escalation path on the previous page |
| `page_size` | integer | No | Number of escalation paths to return per page. Must be between 1 and 25. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Escalations V2

**Slug:** `INCIDENT_IO_LIST_ESCALATIONS_V2`

Tool to list escalations from incident.io. Use when you need to retrieve escalations for the organisation with pagination support.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `after` | string | No | Cursor for pagination - the ID of the last escalation on the previous page |
| `page_size` | integer | No | Number of escalations to return per page. Must be at least 1. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Follow-ups V2

**Slug:** `INCIDENT_IO_LIST_FOLLOW_UPS_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `incident_id` | string | No | Find follow-ups related to this incident |
| `incident_mode` | string ("standard" | "retrospective" | "test" | "tutorial" | "stream") | No | Incident mode filter options. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get API Key Identity

**Slug:** `INCIDENT_IO_LIST_IDENTITY_V1`

Tool to retrieve identity information for the current API key. Use to check which organization and roles are associated with the API key.

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Incident Alerts V2

**Slug:** `INCIDENT_IO_LIST_INCIDENT_ALERTS_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `alert_id` | string | No | Filter by alert_id to find the incident that a particular alert triggered |
| `page_size` | integer | Yes | Number of incident alerts to return per page. Must be at least 1. |
| `incident_id` | string | No | Filter by incident_id to find all alerts attached to a particular incident |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Incident Attachments V1

**Slug:** `INCIDENT_IO_LIST_INCIDENT_ATTACHMENTS_V1`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `external_id` | string | No | Filter by the ID of the resource in the external system (e.g., PagerDuty incident ID, Jira issue key). |
| `incident_id` | string | No | Filter attachments by incident ID. Use this to retrieve all attachments for a specific incident. |
| `resource_type` | string ("pager_duty_incident" | "opsgenie_alert" | "datadog_monitor_alert" | "github_pull_request" | "gitlab_merge_request" | "sentry_issue" | "jira_issue" | "atlassian_statuspage_incident" | "zendesk_ticket" | "google_calendar_event" | "outlook_calendar_event" | "scrubbed" | "statuspage_incident") | No | Enum for external resource types that can be attached to incidents. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Incident Relationships V1

**Slug:** `INCIDENT_IO_LIST_INCIDENT_RELATIONSHIPS_V1`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `incident_id` | string | Yes | The ID of the incident to fetch relationships for |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Incident Roles V2

**Slug:** `INCIDENT_IO_LIST_INCIDENT_ROLES_V2`

Tool to list all incident roles for an organization using V2 API. Use when you need to retrieve available incident roles and their configurations.

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Incidents V2

**Slug:** `INCIDENT_IO_LIST_INCIDENTS_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `after` | string | No | An incident's ID. This endpoint will return a list of incidents after this ID in relation to the API response order. |
| `page_size` | integer | No | Number of records to return per page |
| `mode_one_of` | array | No | Filter for incidents with mode in this list (e.g., 'standard', 'retrospective', 'test', 'tutorial'). Defaults to ['standard', 'retrospective'] if not provided. |
| `severity_gte` | string | No | Filter for incidents with severity rank greater than or equal to this severity ID. Use operator 'gte'. |
| `severity_lte` | string | No | Filter for incidents with severity rank less than or equal to this severity ID. Use operator 'lte'. |
| `status_not_in` | array | No | Filter for incidents with status IDs not in this list. Use operator 'not_in'. |
| `status_one_of` | array | No | Filter for incidents with status IDs in this list. Use operator 'one_of'. |
| `created_at_gte` | string | No | Filter for incidents created at or after this ISO 8601 timestamp. Use operator 'gte'. |
| `created_at_lte` | string | No | Filter for incidents created at or before this ISO 8601 timestamp. Use operator 'lte'. |
| `updated_at_gte` | string | No | Filter for incidents updated at or after this ISO 8601 timestamp. Use operator 'gte'. |
| `updated_at_lte` | string | No | Filter for incidents updated at or before this ISO 8601 timestamp. Use operator 'lte'. |
| `severity_not_in` | array | No | Filter for incidents with severity IDs not in this list. Use operator 'not_in'. |
| `severity_one_of` | array | No | Filter for incidents with severity IDs in this list. Use operator 'one_of'. |
| `incident_type_not_in` | array | No | Filter for incidents with incident type IDs not in this list. Use operator 'not_in'. |
| `incident_type_one_of` | array | No | Filter for incidents with incident type IDs in this list. Use operator 'one_of'. |
| `status_category_not_in` | array | No | Filter for incidents with status category not in this list. Use operator 'not_in'. |
| `status_category_one_of` | array | No | Filter for incidents with status category in this list (e.g., 'triage', 'live', 'closed'). Use operator 'one_of'. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Incident Updates V2

**Slug:** `INCIDENT_IO_LIST_INCIDENT_UPDATES_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `after` | string | No | An record's ID. This endpoint will return a list of records after this ID in relation to the API response order. |
| `page_size` | integer | No | Number of records to return per page. Must be at least 1. |
| `incident_id` | string | No | Incident whose updates you want to list |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List IP allowlists

**Slug:** `INCIDENT_IO_LIST_IP_ALLOWLISTS`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Schedule Entries V2

**Slug:** `INCIDENT_IO_LIST_SCHEDULE_ENTRIES_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `schedule_id` | string | Yes | The ID of the schedule to get entries for. |
| `entry_window_end` | string | No | The end of the window to get entries for. ISO 8601 timestamp. |
| `entry_window_start` | string | No | The start of the window to get entries for. ISO 8601 timestamp. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Schedules V2

**Slug:** `INCIDENT_IO_LIST_SCHEDULES_V2`

Tool to list schedules from incident.io. Use when you need to retrieve on-call schedules with pagination support.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `after` | string | No | A schedule's ID. This endpoint will return a list of schedules after this ID in relation to the API response order. |
| `page_size` | integer | No | Integer number of records to return |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Status Pages V2

**Slug:** `INCIDENT_IO_LIST_STATUS_PAGES_V2`

Tool to list status pages from incident.io. Use when you need to retrieve public or customer status pages with pagination support.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `after` | string | No | A status page's ID. This endpoint will return a list of status pages after this ID in relation to the API response order. |
| `page_size` | integer | No | Integer number of records to return |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Users V2

**Slug:** `INCIDENT_IO_LIST_USERS_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `after` | string | No | An record's ID. This endpoint will return a list of records after this ID in relation to the API response order. |
| `email` | string | No | Filter by email address |
| `page_size` | integer | No | Integer number of records to return |
| `slack_user_id` | string | No | Filter by Slack user ID |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Workflows V2

**Slug:** `INCIDENT_IO_LIST_WORKFLOWS_V2`

Tool to list workflows from incident.io. Use when you need to retrieve configured workflows with pagination support.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `after` | string | No | Cursor for pagination - the ID of the last workflow on the previous page |
| `page_size` | integer | No | Number of workflows to return per page. Must be at least 1. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Alert Attribute V2

**Slug:** `INCIDENT_IO_UPDATE_ALERT_ATTRIBUTES_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | The unique identifier of the alert attribute to update |
| `name` | string | Yes | Unique name of this attribute |
| `type` | string | Yes | Engine resource name for this attribute. Common types include 'String' for text values, or 'CatalogEntry["<catalog_id>"]' for catalog entry references. |
| `array` | boolean | Yes | Whether this attribute is an array |
| `required` | boolean | Yes | Whether this attribute is required |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Alert Source V2

**Slug:** `INCIDENT_IO_UPDATE_ALERT_SOURCES_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier of the alert source to update. This is a required path parameter. |
| `name` | string | Yes | Human-readable name for the alert source that will be displayed in the UI |
| `template` | object | Yes | Template configuration that defines how alerts from this source are processed and displayed |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Bulk Update Catalog Entries V3

**Slug:** `INCIDENT_IO_UPDATE_CATALOG_ENTRIES_BULK_V3`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `entries` | array | Yes | Array of entries to create or update. Each entry must include an entry_id, name, and attribute_values. |
| `delete_mode` | string | No | 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. |
| `catalog_type_id` | string | Yes | ID of the catalog type to bulk update entries for |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Catalog Entry V3

**Slug:** `INCIDENT_IO_UPDATE_CATALOG_ENTRIES_V3`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | ID of the catalog entry to update. This is the unique identifier for the entry. |
| `name` | string | Yes | Name is the human readable name of this entry. This is a required field. |
| `rank` | integer | No | When catalog type is ranked, this is used to help order things. Lower numbers appear first. |
| `aliases` | array | No | Optional aliases that can be used to reference this entry. These provide alternative identifiers for the entry. |
| `external_id` | string | No | An optional alternative ID for this entry, which is ensured to be unique for the type. Useful for integration with external systems. |
| `attribute_values` | object | Yes | 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Catalog Type V3

**Slug:** `INCIDENT_IO_UPDATE_CATALOG_TYPES_V3`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | ID of the catalog type to update |
| `name` | string | Yes | Name of the catalog type |
| `ranked` | boolean | No | Whether entries can be ranked |
| `categories` | array | No | Categories for organization |
| `annotations` | object | No | Key-value annotations |
| `description` | string | Yes | Description of the catalog type |
| `source_repo_url` | string | No | URL of the source repository |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Custom Field Option V1

**Slug:** `INCIDENT_IO_UPDATE_CUSTOM_FIELD_OPTION_V1`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier for the custom field option to update |
| `value` | string | Yes | Human readable name for the custom field option |
| `sort_key` | integer | No | Sort key used to order the custom field options correctly. Lower values appear first. Defaults to 1000 if not specified. |
| `custom_field_id` | string | Yes | ID of the custom field this option belongs to |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Custom Fields V1

**Slug:** `INCIDENT_IO_UPDATE_CUSTOM_FIELDS_V1`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier for the custom field to update. This is a required path parameter. |
| `name` | string | Yes | Human readable name for the custom field. Maximum 50 characters. |
| `required` | string ("never" | "before_closure" | "always") | No | When this custom field must be set during the incident lifecycle (deprecated). |
| `description` | string | Yes | Description of the custom field explaining its purpose. |
| `required_v2` | string ("never" | "before_resolution" | "always") | No | When this custom field must be set during the incident lifecycle. |
| `show_before_update` | boolean | Yes | Whether a custom field should be shown in the incident update modal. |
| `show_before_closure` | boolean | Yes | 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. |
| `show_before_creation` | boolean | Yes | Whether a custom field should be shown in the incident creation modal. This must be true if the field is always required. |
| `show_in_announcement_post` | boolean | No | Whether a custom field should be shown in the list of fields as part of the announcement post when set. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Custom Field V2

**Slug:** `INCIDENT_IO_UPDATE_CUSTOM_FIELDS_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier for the custom field to update. This is a required path parameter. |
| `name` | string | Yes | Human readable name for the custom field. Maximum 50 characters. |
| `description` | string | Yes | Description of the custom field explaining its purpose. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Escalation Path V2

**Slug:** `INCIDENT_IO_UPDATE_ESCALATION_PATHS_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier for the escalation path to update |
| `name` | string | Yes | The name of this escalation path, for the user's reference |
| `path` | array | Yes | The nodes that form the levels and branches of this escalation path |
| `team_ids` | array | No | List of team IDs that this escalation path is associated with |
| `working_hours` | array | No | The working hours for this escalation path |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Incident Role V2

**Slug:** `INCIDENT_IO_UPDATE_INCIDENT_ROLES_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier for the role to update |
| `name` | string | Yes | Human readable name of the incident role |
| `shortform` | string | Yes | Short human readable name for Slack. Note that this will be empty for the 'reporter' role. |
| `description` | string | Yes | Describes the purpose of the role |
| `instructions` | string | Yes | Provided to whoever is nominated for the role. Note that this will be empty for the 'reporter' role. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Incident Status

**Slug:** `INCIDENT_IO_UPDATE_INCIDENT_STATUS`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique ID of the incident status to update |
| `name` | string | Yes | Unique name of this status |
| `description` | string | Yes | Rich text description of the incident status |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Schedule V2

**Slug:** `INCIDENT_IO_UPDATE_SCHEDULES_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier for the schedule to update |
| `schedule` | object | Yes | Schedule properties to update |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Catalog Type Schema V3

**Slug:** `INCIDENT_IO_UPDATE_SCHEMA_CATALOG_TYPES_V3`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | ID of the catalog type to update schema for |
| `version` | integer | Yes | Version number of the schema. Must match the current version to prevent conflicts. |
| `attributes` | array | Yes | List of attributes that define the schema. This replaces the entire schema, so include all attributes you want to keep. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Severity

**Slug:** `INCIDENT_IO_UPDATE_SEVERITIES_V1`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier of the severity to update. |
| `name` | string | Yes | Human readable name of the severity. |
| `rank` | integer | No | Rank to help sort severities (lower numbers are less severe). |
| `description` | string | Yes | Description of the severity. Supports Markdown formatting. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Workflow V2

**Slug:** `INCIDENT_IO_UPDATE_WORKFLOWS_V2`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | Yes | Unique identifier of the workflow to update. This is a required path parameter. |
| `name` | string | Yes | The human-readable name of the workflow. |
| `delay` | object | No | Delay configuration for workflow execution. |
| `state` | string ("active" | "disabled" | "draft" | "error") | No | Enum for workflow state. |
| `steps` | array | Yes | List of steps to execute as part of the workflow. |
| `folder` | string | No | Folder to display the workflow in. |
| `once_for` | array | Yes | Once For strategy to apply to this workflow. List of references that determine uniqueness. |
| `shortform` | string | No | Shortform used to trigger manual workflows in Slack - e.g. `/inc workflows page-ceo`. |
| `annotations` | object | No | Annotations that track metadata about this resource. |
| `expressions` | array | Yes | The expressions used in the workflow. |
| `condition_groups` | array | Yes | List of conditions to apply to the workflow. |
| `runs_on_incidents` | string ("newly_created" | "newly_created_and_active") | Yes | Which incidents should the workflow be applied to? (newly_created or newly_created_and_active). |
| `continue_on_step_error` | boolean | Yes | Whether to continue executing the workflow if a step fails. |
| `runs_on_incident_modes` | array | Yes | Which modes of incident this should run on (defaults to just standard incidents). |
| `include_private_incidents` | boolean | Yes | Whether to include private incidents. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |