Connect your app to incident.io
Connect your Lovable app to incident.io to display live incidents, manage follow-ups, and review on-call schedules. You provide an API key in the Connectors settings, and Lovable handles the connection securely behind the scenes.
Anyone building operational dashboards, status pages, or internal incident response tools using data from incident.io.
Do this, in order
- 1
Create a new API key in your incident.io settings with only the read or write permissions your app needs, and copy the secret token.
Your app needs authorization to read or update incident.io data, and incident.io only displays the token once.
- 2
Open the Connectors page in Lovable, find incident.io, and click Connect.
This opens the configuration screen where you register the credentials for your workspace.
- 3
Enter a display name, paste your API key into the form, and select your sharing preferences.
This securely stores the secret key in Lovable without exposing it in your app source code.
- 4
Click Connect to save and verify the connection.
Lovable tests the key with incident.io to confirm it is valid before saving.
- 5
In your Lovable project chat, ask Lovable to link your project to your incident.io connection and generate your incident features.
Connecting the project activates the server-side integration so your app can fetch live incident data.
Paste this into your project
Use incident.io and build an incident command dashboard that lists open incidents with severity, status, commander, and the latest update.
Words decoded
- API key
- A secret password that lets your software communicate securely with an external service.
- Rate limit
- A restriction set by a service on how many requests an app can make within a certain amount of time.
Where people get stuck
- Never paste your incident.io API key into your project chat, prompts, or frontend code; only enter it in the Connectors form.
- If your app needs to create or update incidents, you must select write permissions when creating the key in incident.io, or requests will return a 403 error.
- The connector uses a single shared key for the whole app, meaning it does not log in individual app users with their personal incident.io accounts.
- Do not call incident.io directly from browser code; always let Lovable route requests through its server-side gateway.
The short version, steps, decoder and prompt on this page are written automatically from Lovable's own documentation and can lag or misread it. The official page is always the authority.