Connect incident.io to your AI agent

Developer Tools 86 actions available

Incident management and response platform

We set up the connection using your own incident.io account, with keys you control, and keep it running. Your agent picks it up and starts doing the work.

What your agent can do in incident.io

Each one is a real action the agent can take on its own, the same things a person clicking around incident.io could do. Read-only by default; write actions are confirmed against your policy.

  • Create Alert Attribute 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 informa…
  • Create Alert Route 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.
  • Create Alert Source 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.
  • Create Catalog Entry 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 reso…
  • Create Catalog Type 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.
  • Create Custom Field Option 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.
  • Create Custom Field 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.
  • Create Escalation 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).
  • Create Incident Role 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…
  • 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'.
  • Create Incident 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 seve…
  • Create Managed Resource 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 hel…
  • Create Severity 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.
  • Delete Alert Attribute 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.
  • Delete Alert Route 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.
  • Delete Alert Source 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.
  • Delete Catalog Entry 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.
  • Delete Catalog Type 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.
  • 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.
  • Delete Custom Field Option Tool to delete a custom field option in incident.io. Use when you need to permanently remove a custom field option by its ID.
  • Delete Custom Field 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.
  • Delete Escalation Path 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.
  • Delete Incident Role V2 Tool to delete an incident role by ID. Use when you need to permanently remove an incident role from 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.
  • Delete Schedule 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.
  • 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.
  • Delete Workflow 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.
  • Edit Incident 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.
  • Show Alert Attribute 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.
  • Show 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.
  • Show Alert Source 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.
  • 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.
  • Get Catalog Type 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.
  • Get Custom Field Option Tool to retrieve a specific custom field option by its ID. Use when you need details about a custom field option in incident.io.
  • Get Custom Field 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.
  • 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.
  • Show 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.
  • Get Incident Role 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.
  • 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.
  • Get Incident Timestamp 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.
  • 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.
  • Get Incident by ID (V2) Tool to retrieve a specific incident by ID using V2 API. Use when you need detailed information about an incident including duration metrics, timestamps, and workload data.
  • Show 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.
  • Get Severity V1 Tool to retrieve a specific severity by ID from incident.io. Use when you need to fetch details about a particular severity level.
  • Get User 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.
  • Get Workflow 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.
  • 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…
  • 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.
  • 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.
  • List Alert Routes V2 Tool to list alert routes from incident.io. Use when you need to retrieve configured alert routes with pagination support.
  • 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.
  • List Alerts V2 Tool to list alerts from incident.io. Use when you need to retrieve alerts for the organisation with pagination support.
  • 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.
  • 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…
  • 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 ext…
  • List Escalation Paths V2 Tool to list escalation paths from incident.io. Use when you need to retrieve configured escalation paths with pagination support.
  • List Escalations V2 Tool to list escalations from incident.io. Use when you need to retrieve escalations for the organisation with pagination support.
  • 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.
  • Get API Key Identity Tool to retrieve identity information for the current API key. Use to check which organization and roles are associated with the API key.
  • 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.
  • 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, externa…
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • List Schedules V2 Tool to list schedules from incident.io. Use when you need to retrieve on-call schedules with pagination support.
  • 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.
  • 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.
  • List Workflows V2 Tool to list workflows from incident.io. Use when you need to retrieve configured workflows with pagination support.
  • Update Alert Attribute 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.
  • Update Alert Source 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.
  • Bulk Update Catalog Entries 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. T…
  • Update Catalog Entry 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 -…
  • Update Catalog Type 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.
  • 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.
  • 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.
  • Update Custom Field 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.
  • Update Escalation Path 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.
  • Update Incident Role 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.
  • 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.
  • Update Schedule 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.
  • Update Catalog Type Schema 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.
  • Update Severity Tool to update a severity in incident.io. Use when you need to modify the name, description, or rank of an existing severity level.
  • Update Workflow 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.

How we connect it

  1. 1

    Connect your account

    You create a key in incident.io, a key you create and control, and paste it in once. It lives in a secrets store on your server, not with us.

  2. 2

    Set the guardrails

    Read-only by default. You choose which write actions the agent may take, and anything outside that policy gets confirmed with you first.

  3. 3

    We keep it running

    Health checks on every connection, updates handled for you, and we watch the first week of activity to make sure the work lands.

incident.io questions, answered.

With a key you create and control. You paste it in once, it is stored in a secrets store on your server, permissions are scoped to the minimum the agent needs, and you can revoke it at any time.
The actions incident.io's API allows, the same things a person clicking around the app could do. Connections start read-only by default; write actions are confirmed against the policy you set before the agent takes them.
Connections are priced per tool on top of the base plan. Some are included, some are premium. See pricing for how connection charges work.
Standard tools are ready inside 7 business days of the setup call. We test the connection end to end, walk you through how the agent uses it, and watch the first week of activity.

Ready to put incident.io to work?

Tell us what your team runs on. We set up the connection, secure it, and your agent takes it from there.

All product names, logos, and brands are property of their respective owners; used for identification only. ZeroToClaw is not affiliated with or endorsed by incident.io.