incident.io integration

Developer tools connector, available on Zeplik

incident.io is available as an integration on Zeplik, the AI assistant that works across every model in one chat. Connect incident.io and Zeplik can act on your software development for you: Incident management and response platform. You stay in the conversation while the assistant does the work in incident.io directly.

Zeplik exposes 59 read actions and 41 write actions for incident.io. Read actions run automatically; write actions stay off until you enable write access in Settings, so nothing is changed in incident.io without your consent.

Try incident.io on Zeplik

Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.

What Zeplik can do with incident.io

Read from incident.io (59)

Runs automatically in any conversation.

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

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

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

  • Get catalog entries 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 types 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.

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

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

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

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

  • Get incident roles v1

    Tool to retrieve a specific incident role by ID. Use when you need to get details about a specific incident role.

and 47 more.

Act in incident.io (41)

Runs only after you enable write access.

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

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

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

  • Create catalog entries 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 incident management workflow.

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

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

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

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

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

  • Create incident roles v1

    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 incident response.

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

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

and 29 more.

How to connect incident.io

  1. Sign in to Zeplik

    Create a free Zeplik account or sign in. New accounts start with free credits, so you can try incident.io immediately.

  2. Connect incident.io

    Open Settings and go to Connectors, then press Connect on incident.io. You can also connect from the incident.io page in the app.

  3. Add your incident.io API key

    Paste your incident.io API key when prompted. Zeplik stores it securely on the server and starts working with incident.io right away.

Frequently asked questions

Can I use incident.io with Zeplik?
Yes. incident.io is available as an integration on Zeplik. Connect it once and the AI assistant can work with your incident.io account inside any conversation.
What can Zeplik do with incident.io?
Once connected, Zeplik has 59 read and 41 write actions for incident.io. Incident management and response platform.
How do I connect incident.io to Zeplik?
You connect incident.io by pasting your own incident.io API key in Settings under Connectors. There is no separate app to install.
Does Zeplik change things in incident.io without asking?
No. Zeplik reads from incident.io by default. Any action that changes data in incident.io requires write access, which stays off until you enable it in Settings under Connectors.
How much does connecting incident.io cost?
Connecting incident.io is free. You only spend Zeplik credits when the assistant runs, and new accounts start with free credits.

Related developer tools integrations

Connect incident.io to your AI assistant

Every model, one chat. Bring incident.io into Zeplik and let the assistant do the work.