---
title: "Connect your app to incident.io"
description: "<p><a href=\"https://incident.io/\">incident.io</a> is an incident management platform for coordinating response, managing on-call schedules, communicating status, and tracking follow-up work."
---

> Documentation Index
> Fetch the complete documentation index at: https://rshift.helpcent.re/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect your app to incident.io

<p><a href="https://incident.io/">incident.io</a> is an incident management platform for coordinating response, managing on-call schedules, communicating status, and tracking follow-up work. The incident.io connector lets your RShift Sites app read and manage operational data through the incident.io API.</p>
<p>incident.io is available as an <a href="/sites/integrations/app-connectors/">app + chat connector</a>: one shared connection that works in the project chat while you build and in your published apps.</p>
<p>With incident.io, your app can:</p>
<ul>
<li>List incidents and display their status, severity, timeline, and updates</li>
<li>Create and update incidents when the connected API key has the required permissions</li>
<li>Track follow-ups and outstanding response work</li>
<li>Review alerts and on-call schedules</li>
<li>Display status page information</li>
<li>Read and manage catalog data for services, teams, and other operational resources</li>
</ul>
<p>incident.io is a good fit when you want to bring incident response data into an internal tool, customer-facing status experience, or operational dashboard.</p>
<h2>Common use cases and example apps</h2>
<p>Use incident.io when your app needs operational data or incident-response actions alongside its existing workflows.</p>
<table>
<thead>
<tr>
<th style="text-align: left">Example app</th>
<th style="text-align: left">Example prompt</th>
<th style="text-align: left">Description</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align: left"><strong>Incident command dashboard</strong></td>
<td style="text-align: left"><em>Use incident.io and build a dashboard that lists open incidents with severity, status, commander, and the latest update.</em></td>
<td style="text-align: left"><strong>Give responders a focused view of active incidents.</strong><br />The app reads current incident data and highlights the details that teams need during response.</td>
</tr>
<tr>
<td style="text-align: left"><strong>Incident intake tool</strong></td>
<td style="text-align: left"><em>Use incident.io and build an internal form that creates a new incident with a summary and severity.</em></td>
<td style="text-align: left"><strong>Declare incidents from a workflow tailored to your team.</strong><br />The app validates the form and creates the incident when the connected key has permission to manage incidents.</td>
</tr>
<tr>
<td style="text-align: left"><strong>Follow-up tracker</strong></td>
<td style="text-align: left"><em>Use incident.io and build a tracker for open follow-ups grouped by incident, assignee, and due date.</em></td>
<td style="text-align: left"><strong>Keep post-incident work visible until it is complete.</strong><br />The app reads follow-ups and organizes them into an actionable operations view.</td>
</tr>
<tr>
<td style="text-align: left"><strong>On-call directory</strong></td>
<td style="text-align: left"><em>Use incident.io and build an on-call directory that shows the current and upcoming responder for each schedule.</em></td>
<td style="text-align: left"><strong>Help teams find the right responder quickly.</strong><br />The app reads on-call schedules and presents current and upcoming coverage.</td>
</tr>
<tr>
<td style="text-align: left"><strong>Status page viewer</strong></td>
<td style="text-align: left"><em>Use incident.io and build a public status page that shows active incidents and recent updates.</em></td>
<td style="text-align: left"><strong>Communicate service health in an app you control.</strong><br />The app reads status page data and renders incident updates for your audience.</td>
</tr>
<tr>
<td style="text-align: left"><strong>Alert review console</strong></td>
<td style="text-align: left"><em>Use incident.io and build a console that groups recent alerts by source, priority, and related incident.</em></td>
<td style="text-align: left"><strong>Turn incoming alerts into a reviewable operations queue.</strong><br />The app reads alert data and helps operators identify patterns and escalation needs.</td>
</tr>
<tr>
<td style="text-align: left"><strong>Service catalog explorer</strong></td>
<td style="text-align: left"><em>Use incident.io and build a searchable service catalog with owners, teams, and related operational metadata.</em></td>
<td style="text-align: left"><strong>Make service ownership easier to discover.</strong><br />The app reads incident.io catalog entries and presents them in a searchable directory.</td>
</tr>
</tbody>
</table>
<h2>How to connect incident.io</h2>
<p>Who can create incident.io connections depends on your plan and workspace settings. See <a href="/sites/integrations/admin-controls/#who-can-create-connections-and-clients">Who can create connections and clients</a>.</p>
<p>App + chat connectors are available by default on Free, Pro, and Business plans. On Enterprise plans, they are effectively disabled at first: <a href="/sites/integrations/admin-controls/#who-can-create-connections-and-clients">Who can create connections and clients</a> defaults to <strong>No one</strong> until an admin changes it in <strong>Connectors → Admin settings → App + chat connectors</strong>.</p>
<p>You can create multiple incident.io connections using different API keys, which is useful for separating environments, incident.io accounts, or permission sets.</p>
<p>When the connection is created, you can <a href="/sites/integrations/app-connectors/#link-a-connection-to-a-project">link it to the projects</a> where you want to use it. Anyone building in a project can ask RShift Sites in the project chat to link their project to it.</p>
<h3>Prerequisites</h3>
<p>Before connecting incident.io, make sure you have:</p>
<ul>
<li>An incident.io account with access to create API keys</li>
<li>An incident.io API key with the permissions your app needs</li>
<li>Permission to <strong>create connections</strong> in your RShift Sites workspace (see <a href="/sites/integrations/admin-controls/#who-can-create-connections-and-clients">Who can create connections and clients</a>)</li>
</ul>
<blockquote>
<p><strong>Note</strong></p>
<p>API requests through this connector count toward incident.io's API limits and any applicable incident.io plan usage. Billing and quota are handled directly by incident.io, not RShift Sites.</p>
</blockquote>
<h3>Step 1: Get an incident.io API key</h3>
<p>An incident.io API key lets your RShift Sites app authenticate with the incident.io API. You choose what the key can do when you create it, using account-level permissions, team-scoped permissions, or both.</p>
<p>To create an incident.io API key:</p>
<p><strong>Open API key settings</strong></p>
<p>Sign in to <a href="https://app.incident.io/~/settings/api-keys">incident.io API key settings</a>.</p>
<p><strong>Create an API key</strong></p>
<p>Create a new key and give it a descriptive name, for example <code>RShift Sites production</code>.</p>
<p><strong>Choose permissions</strong></p>
<p>Select only the permissions your app needs. Include write permissions only if the app creates or changes incidents, follow-ups, or catalog data.</p>
<p><strong>Copy the API key</strong></p>
<p>Copy the key when incident.io displays it and store it securely. incident.io only shows the token once.</p>
<blockquote>
<p><strong>Danger</strong></p>
<p>Your API key functions like a password. Paste it only into the incident.io connection form in RShift Sites. Do not put it in a prompt, URL, browser code, source file, or chat message.</p>
</blockquote>
<p>See incident.io documentation for more: <a href="https://docs.incident.io/api-reference/introduction#authentication">incident.io API authentication</a>.</p>
<h3>Step 2: Connect incident.io to RShift Sites</h3>
<p>Open the connection form and enter the API key you created in incident.io.</p>
<p><strong>Open incident.io in Connectors</strong></p>
<p>Open <a href="https://lovable.dev/dashboard?connectors"><strong>Connectors</strong></a> and select <strong>incident.io</strong>. See <a href="/sites/integrations/introduction/#where-to-find-connectors">Where to find connectors</a> for other ways to open the connector catalog.</p>
<p><strong>Add a connection</strong></p>
<p>Click <strong>Add connection</strong>.</p>
<p><strong>Configure the connection</strong></p>
<ol>
<li><strong>Display name</strong>: name the connection, for example <code>incident.io Prod</code>. This name is only used inside RShift Sites to identify the connection.</li>
<li><strong>API key</strong>: paste the incident.io API key.</li>
</ol>
<p><strong>Choose who can use this connection</strong></p>
<p>Under <strong>Sharing</strong>, the connection is private to you by default and shows a <strong>Private</strong> label. To share it, click <strong>Share with others</strong>. Then add workspace members by email, or click <strong>Invite entire workspace</strong> to make the connection available to everyone in your RShift Sites workspace.</p>
<pre><code>See [Who can use connections and clients](/sites/integrations/admin-controls/#who-can-use-connections-and-clients) for more information.
</code></pre>
<p><strong>Connect</strong></p>
<p>Click <strong>Connect</strong>. RShift Sites verifies the key with incident.io before saving the connection.</p>
<p>When connected, anyone building in a project can ask RShift Sites in the project chat to link their project to incident.io (based on configured connection-level access). Your RShift Sites apps can then call incident.io through RShift Sites' server-side connector gateway without exposing the incident.io API key to browser code.</p>
<h2>Limitations</h2>
<p>The incident.io connector uses a shared API key and keeps requests behind RShift Sites' server-side gateway.</p>
<ul>
<li>Each connection uses one shared incident.io API key. The connector does not support per-end-user incident.io login.</li>
<li>The connected key controls what data the app can read and change. RShift Sites cannot grant permissions that the key does not have.</li>
<li>RShift Sites does not rotate incident.io API keys automatically. To rotate a key, create a new key in incident.io and update the RShift Sites connection.</li>
<li>Calls must run through RShift Sites' server-side connector gateway. Do not call <code>api.incident.io</code> directly from browser code or expose the API key in generated app code.</li>
</ul>
<h2>Troubleshooting</h2>
<p>Use the incident.io response status to identify credential, permission, and rate-limit problems.</p>
<ul>
<li>A <code>401</code> response usually means the key is invalid or has been revoked. Create a replacement key in incident.io and update the connection.</li>
<li>A <code>403</code> response means the key does not have permission for that endpoint. Create or update a key with the required incident.io permissions. Retrying the same request does not fix a missing permission.</li>
<li>incident.io applies rate limits, including a default limit of 1,200 requests per minute per API key and lower limits on some endpoints. Cache repeated reads and honor <code>429</code> responses and the <code>Retry-After</code> header.</li>
</ul>
<h2>Manage your {connector_0} connection</h2>
<p>Connections are managed from <a href="https://lovable.dev/dashboard?connectors"><strong>Connectors</strong></a>: select <strong>{connector_0}</strong>, then open the connection.</p>
<ul>
<li><strong>Unlink projects</strong> to remove {connector_0} access from specific projects while keeping the connection available for others. See <a href="/sites/integrations/app-connectors/#unlink-projects-from-a-connection">Unlink projects from a connection</a> for the steps.</li>
<li><strong>Delete the connection</strong> to remove it from the workspace entirely. Deleting is permanent. It removes the credentials from all linked projects, and app features that use {connector_0} stop working until a new connection is added. See <a href="/sites/integrations/app-connectors/#delete-a-connection">Delete a connection</a> for the steps and who can delete.</li>
</ul>
<h2>Related topics</h2>
<ul>
<li><a href="/sites/integrations/apollo/">Connect your app to Apollo.io</a></li>
<li><a href="/sites/integrations/gatewayapi/">Connect your app to GatewayAPI</a></li>
<li><a href="/sites/integrations/gong/">Connect your app to Gong</a></li>
<li><a href="/sites/integrations/firebase-cloud-messaging/">Connect your app to Firebase Cloud Messaging</a></li>
<li><a href="/sites/integrations/slack/">Connect your app to Slack</a></li>
</ul>

Source: https://rshift.helpcent.re/sites/integrations/incidentio/index.mdx
