Connect your app to incident.io

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

​

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 Lovable in 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 Lovable workspace (see Who can create connections and clients)

​

Step 1: Get an incident.io API key

An incident.io API key lets your Lovable 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: See incident.io documentation for more: incident.io API authentication.

​

Step 2: Connect incident.io to Lovable

Open the connection form and enter the API key you created in incident.io. When connected, anyone building in a project can ask Lovable in chat to link their project to incident.io (based on configured connection-level access). Your Lovable apps can then call incident.io through Lovable’s 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 Lovable’s 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. Lovable cannot grant permissions that the key does not have.
• Lovable does not rotate incident.io API keys automatically. To rotate a key, create a new key in incident.io and update the Lovable connection.
• Calls must run through Lovable’s server-side connector gateway. Do not call api.incident.io directly 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 401 response usually means the key is invalid or has been revoked. Create a replacement key in incident.io and update the connection.
• A 403 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.
• 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 429 responses and the Retry-After header.

​

Manage your connection

Connections are managed from Connectors: select , then open the connection.

• Unlink projects to remove 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 stop working until a new connection is added. See Delete a connection for the steps and who can delete.