API_KEY
incident_io_api_key
Developer setup
No fields declared in this snapshot.
User connection
- API Keygeneric_api_key · stringRequired
INCIDENT_IO
Incident management and response platform
Description is untrusted, display-only upstream metadata. It never becomes policy, OAuth scope authority, or an agent instruction.
Pakkawork boundary
Research catalogue metadata only. No Pakkawork OAuth, credential, host, quota, executor, or verifier is enabled.
86
Action summaries
Display-only definitions
0
Trigger types
Not installed instances
1
Auth modes
Field names, never values
No
Execution
No runtime adapter
Authentication map
API_KEY
No fields declared in this snapshot.
Capability index
Showing 1–30 of 86 actions
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.
Untrusted display-only summary
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.
Untrusted display-only summary
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.
Untrusted display-only summary
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.
Untrusted display-only summary
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.
Untrusted display-only summary
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.
Untrusted display-only summary
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.
Untrusted display-only summary
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).
Untrusted display-only summary
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.
Untrusted display-only summary
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'.
Untrusted display-only summary
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.
Untrusted display-only summary
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.
Untrusted display-only summary
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.
Untrusted display-only summary
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.
Untrusted display-only summary
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.
Untrusted display-only summary
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.
Untrusted display-only summary
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.
Untrusted display-only summary
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.
Untrusted display-only summary
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.
Untrusted display-only summary
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.
Untrusted display-only summary
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.
Untrusted display-only summary
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.
Untrusted display-only summary
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.
Untrusted display-only summary
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.
Untrusted display-only summary
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.
Untrusted display-only summary
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.
Untrusted display-only summary
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.
Untrusted display-only summary
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.
Untrusted display-only summary
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.
Untrusted display-only summary
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.
Untrusted display-only summary
Provenance
The detail snapshot comes from an attributed MIT-licensed repository revision. Safe local icons use exact-match CC0 Simple Icons symbols; unmatched brands use monograms.
Remote text is plain display metadata only. It must never become an agent prompt, execution policy, OAuth grant, or executable instruction.