incident.io Integration — Automate incident.io with AI on Beauto

Incident management and response platform

Category: developer tools · 86 actions available

What you can automate with incident.io

Beauto connects incident.io with 900+ other apps so you can build AI-powered workflows in minutes. Trigger automations from incident.io events, enrich incident.io data with AI, or sync incident.io with the rest of your stack — without writing code.

  • Sync incident.io data with Gmail, Slack, Notion, HubSpot, Google Sheets, and more
  • Trigger AI agents on new incident.io events and route the output anywhere
  • Schedule recurring incident.io tasks — daily reports, cleanups, or bulk updates
  • Use natural language to describe the workflow; Beauto builds it for you

incident.io actions Beauto supports

  • 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 informat
  • 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 V2 — Tool to create a catalog entry in incident.io. 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 inci
  • 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 resou
  • 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 — Tool to create a new incident role in incident.io. Use when you need to define a new role type that can be assigned during incidents. Roles help organize responsibilities and ensure the right people are engaged during in
  • 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 d
  • 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 V1 — Tool to create a new incident in incident.io. Use when you need to report and track an operational issue or outage. Requires at minimum an idempotency_key and visibility setting.
  • 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 sever
  • 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 help
  • 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 V2 — Tool to delete a catalog entry from incident.io. Use when you need to remove a catalog entry that is no longer needed.
  • 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 V2 — Tool to delete a catalog type from incident.io. Use when you need to remove a catalog type that is no longer needed.
  • 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 Role V1 — Tool to delete an incident role by ID. Use when you need to 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.
  • Show Entry Catalog V2 — 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, values, and associated catalog type.
  • 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 V2 — Tool to retrieve a specific catalog type by ID from incident.io. Use when you need to get details about a catalog type's configuration, schema, or metadata.

Related integrations

Browse all 900+ integrations →

Get started with incident.io on Beauto

Sign up free, connect your incident.io account in one click, and describe the workflow you want in plain English. Beauto's AI handles the rest — no API keys or code required.

Try Beauto free · Browse all 900+ integrations · How it works