Connect your app to incident.io

1. 1

   Sign in to incident.io and go to your API key settings.

   You need an API key from incident.io to allow Lovable to securely access your incident.io data.

2. 2

   Create a new API key, give it a clear name like 'Lovable production', and choose only the permissions your app needs.

   Naming helps you identify the key later, and limiting permissions improves security by only granting necessary access.

3. 3

   Copy the API key that incident.io displays and store it securely.

   This key is like a password and is shown only once; you'll need it for the next step.

4. 4

   In Lovable, go to 'Connectors', select 'incident.io', and click 'Add connection'.

   This opens the form where you'll tell Lovable how to connect to incident.io.

5. 5

   Give your connection a 'Display name' (e.g., 'incident.io Prod'), paste the API key you copied, and choose who in your workspace can use this connection.

   The display name helps you recognize the connection in Lovable, the API key authenticates Lovable with incident.io, and setting access controls who can use this connection in their projects.

6. 6

   Click 'Connect'.

   Lovable will verify the key and save the connection, making incident.io available for your projects.

Connect my app to incident.io to manage incidents and alerts. I need to list incidents, create new ones, track follow-ups, and display on-call schedules.

API key

A secret code that acts like a password, allowing one computer program (like Lovable) to securely access another program's services (like incident.io) on your behalf.

Connector

A built-in tool in Lovable that helps your app talk to other online services, like incident.io, without you needing to write complex code for it.

Permissions

Specific rights or abilities granted to your API key, determining what actions your Lovable app can perform in incident.io (e.g., just read information, or also create/change things).

Server-side gateway

A secure middleman that handles communication between your Lovable app and incident.io. It keeps your secret API key hidden and protects it from being exposed in your app's public-facing code.

• Do not put your incident.io API key in a prompt, URL, browser code, source file, or chat message, as it functions like a password.
• Ensure your incident.io API key has the correct permissions for what your app needs to do; a 403 error means missing permissions.
• Be aware that API requests count towards incident.io's API limits and billing, not Lovable's.
• If you get a 401 error, your API key might be invalid or revoked; you'll need to create a new one in incident.io and update the connection in Lovable.