incident.io 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.
incident.io is available as an app + chat connector: one shared connection that works in the project chat while you build and in your published apps.
With incident.io, your app can:
- List incidents and display their status, severity, timeline, and updates
- Create and update incidents when the connected API key has the required permissions
- Track follow-ups and outstanding response work
- Review alerts and on-call schedules
- Display status page information
- Read and manage catalog data for services, teams, and other operational resources
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.
Common use cases and example apps
Use incident.io when your app needs operational data or incident-response actions alongside its existing workflows.
| Example app | Example prompt | Description |
|---|---|---|
| Incident command dashboard | Use incident.io and build a dashboard that lists open incidents with severity, status, commander, and the latest update. | Give responders a focused view of active incidents. The app reads current incident data and highlights the details that teams need during response. |
| Incident intake tool | Use incident.io and build an internal form that creates a new incident with a summary and severity. | Declare incidents from a workflow tailored to your team. The app validates the form and creates the incident when the connected key has permission to manage incidents. |
| Follow-up tracker | Use incident.io and build a tracker for open follow-ups grouped by incident, assignee, and due date. | Keep post-incident work visible until it is complete. The app reads follow-ups and organizes them into an actionable operations view. |
| On-call directory | Use incident.io and build an on-call directory that shows the current and upcoming responder for each schedule. | Help teams find the right responder quickly. The app reads on-call schedules and presents current and upcoming coverage. |
| Status page viewer | Use incident.io and build a public status page that shows active incidents and recent updates. | Communicate service health in an app you control. The app reads status page data and renders incident updates for your audience. |
| Alert review console | Use incident.io and build a console that groups recent alerts by source, priority, and related incident. | Turn incoming alerts into a reviewable operations queue. The app reads alert data and helps operators identify patterns and escalation needs. |
| Service catalog explorer | Use incident.io and build a searchable service catalog with owners, teams, and related operational metadata. | Make service ownership easier to discover. The app reads incident.io catalog entries and presents them in a searchable directory. |
How to connect incident.io
Who can create incident.io connections depends on your plan and workspace settings. See Who can create connections and clients.
App + chat connectors are available by default on Free, Pro, and Business plans. On Enterprise plans, they are effectively disabled at first: Who can create connections and clients defaults to No one until an admin changes it in Connectors → Admin settings → App + chat connectors.
You can create multiple incident.io connections using different API keys, which is useful for separating environments, incident.io accounts, or permission sets.
When the connection is created, you can link it to the projects 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.
Prerequisites
Before connecting incident.io, make sure you have:
- An incident.io account with access to create API keys
- An incident.io API key with the permissions your app needs
- Permission to create connections in your RShift Sites workspace (see Who can create connections and clients)
Step 1: Get an incident.io API key
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.
To create an incident.io API key:
Open API key settings
Sign in to incident.io API key settings.
Create an API key
Create a new key and give it a descriptive name, for example RShift Sites production.
Choose permissions
Select only the permissions your app needs. Include write permissions only if the app creates or changes incidents, follow-ups, or catalog data.
Copy the API key
Copy the key when incident.io displays it and store it securely. incident.io only shows the token once.
See incident.io documentation for more: incident.io API authentication.
Step 2: Connect incident.io to RShift Sites
Open the connection form and enter the API key you created in incident.io.
Open incident.io in Connectors
Open Connectors and select incident.io. See Where to find connectors for other ways to open the connector catalog.
Add a connection
Click Add connection.
Configure the connection
- Display name: name the connection, for example
incident.io Prod. This name is only used inside RShift Sites to identify the connection. 2. API key: paste the incident.io API key.
Choose who can use this connection
Under Sharing, the connection is private to you by default and shows a Private label. To share it, click Share with others. Then add workspace members by email, or click Invite entire workspace to make the connection available to everyone in your RShift Sites workspace.
See Who can use connections and clients for more information.
Connect
Click Connect. RShift Sites verifies the key with incident.io before saving the connection.
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.
Limitations
The incident.io connector uses a shared API key and keeps requests behind RShift Sites’ server-side gateway.
- Each connection uses one shared incident.io API key. The connector does not support per-end-user incident.io login.
- The connected key controls what data the app can read and change. RShift Sites cannot grant permissions that the key does not have.
- 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.
- Calls must run through RShift Sites’ server-side connector gateway. Do not call
api.incident.iodirectly from browser code or expose the API key in generated app code.
Troubleshooting
Use the incident.io response status to identify credential, permission, and rate-limit problems.
- A
401response usually means the key is invalid or has been revoked. Create a replacement key in incident.io and update the connection. - A
403response 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. - 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
429responses and theRetry-Afterheader.
Manage your {connector_0} connection
Connections are managed from Connectors: select {connector_0}, then open the connection.
- Unlink projects to remove {connector_0} access from specific projects while keeping the connection available for others. See Unlink projects from a connection for the steps.
- Delete the connection 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 Delete a connection for the steps and who can delete.