Integrations / incident.io
incident.io
incident.io incident management for incidents, alerts, follow-ups, catalog entries, severities, and response workflows.
API key
Indexes
Actions
Events
What Telara does
Capability matrix
Before you connect
Prerequisites
An incident.io organization you can administer.
Permission to create an API key.
Vendor setup
Get the credential
1
Create an API key
In incident.io, open Settings → API keys. Create a key that can read the incidents Telara should see.
2
Paste in Telara
Settings → Integrations → incident.io.
In Telara
Connect in Telara
API key
incident.io API key.
In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.
Fields Telara asks for
- API token
Knowledge
What gets indexed
| Resource | Coverage |
|---|---|
| Incidents | Partial — not every record the vendor holds is synced |
| Action item | Partial — not every record the vendor holds is synced |
Sync
Freshness & sync
| Resource | Lag | Deletions |
|---|---|---|
| Incidents | Up to 1 hour | Removed records disappear on the next full sync |
| Action item | Up to 1 day | Removed records disappear on the next full sync |
Data handling
Permissions & data handling
Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.
Excluded from semantic search: Incidents, Action item.
After connect
Verify it worked
After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.
Honesty
Known limitations
The key inherits that user’s (or bot’s) visibility. Private incidents stay private.
API keys are shown once — store it in Telara immediately.