Connect incident.io with Hookshot™ and your stack

Incident management and response platform

Tools and triggers

What Agents can do in incident.io

Available tools and events after incident.io is connected.

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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.

Setup

Connect incident.io in Hookshot™

Pick a scope, then confirm what can start a Protege and what it can do.

Trigger Access

What can start a Protege from this app.

Tool Access

What a Protege can do after it starts.

Connection scope

Prefer team for production.

Team

Shared credential for production and unattended runs.

Personal

Tied to one user—only when the workflow needs their account.

Chat

Team-scoped for supported chat surfaces.

Full setup guide

Build with us

See Hookshot™ in your stack.

Request early access or book a live walkthrough with the team.

Request Demo
Hookshot™ setup screen — AI agent workflow configuration with model selection, trigger status, and governance controls.