Incident.io
Connecting Incident.io to NeuBird enables seamless incident management, on-call routing, and alert orchestration. Once connected, alerts can automatically create, update, or resolve incidents in Incident.io, providing visibility, context, and automated escalation paths.
This integration ensures that:
- Incidents are created with the appropriate metadata (service, severity, tags) directly from NeuBird alerts
- Status and updates (acknowledgements, resolutions) are synced bi-directionally
- On-call schedules from Incident.io are respected when routing alerts
- You maintain a single source of truth for incident lifecycle management
Create an API Key
Section titled “Create an API Key”Follow these steps to create a dedicated API key in Incident.io.
-
Open Settings
- Sign in to Incident.io.
- Click your organization name and choose Settings.

-
Open API Keys
- In the Settings sidebar, under Extend, select API Keys.

-
Create a new API key
- Click Add new.
- Give the key a clear name, for example
NeuBird - 2025-10-05. - Choose the minimal permissions NeuBird needs. At minimum select:
- Incidents: Read all incidents (required)
- Incidents: Create incidents
- Incidents: Update incidents
- On-call / Schedules: Read (recommended if NeuBird should respect on-call routing)
- If Incident.io uses different scope labels, pick the equivalent scopes that allow creating, updating, and reading incidents and on-call schedules.

-
Save and copy the API key
- Save the key and copy the generated token immediately. Treat the token like a secret.
Connection Fields
Section titled “Connection Fields”| Field | Required | Description |
|---|---|---|
| Name | Yes | A descriptive name for this connection |
| Description | No | An overview of what this connection is used for |
| API Token | Yes | The API token generated from Incident.io settings |
For general instructions on creating and managing connections, see the Connections Overview.