Quick summary
- You can bring incidents from incident.io into Assuric instead of retyping them.
- The Import button on the incidents page only appears once an admin connects incident.io under Workspace → Integrations.
- Imported incidents stay in sync with incident.io for fields like title and status, so edit them in incident.io.
Connect incident.io
Only admins can connect or disconnect incident.io.1
Create an API key in incident.io
As an admin in incident.io, go to Settings → API keys and click Add new. Name the key, tick only View data, like public incidents and organisation settings, and click Create. Copy the key straight away: incident.io only shows it once.
2
Connect it in Assuric
Go to Workspace → Integrations and click Connect on the Incident.io card. Paste the key into Incident.io API key and click Validate: Assuric confirms your incident.io workspace or names the permission the key is missing. Then click Connect: Assuric syncs on a schedule, and Import appears on the incidents page.
Import incidents
1
Select the incidents
Click Import on the incidents page to open the Import from Incident.io dialog, which lists your latest incident.io incidents that aren’t in Assuric yet. Click Sync Now to refresh the list, then tick each incident you want. If you filter the list, use only one multi-select filter at a time.
2
Choose where they land, then import
Under Import to, tick Clinical, Security or both, and pick the Products the incidents affect. Then click Import N, where N is how many you selected. It’s available once Clinical or Security is ticked.
- Incident ID, Incident Title, Summary, Status, Severity and Date Occurred filled in and kept in sync, so change them in incident.io.
- Source set to Incident.io, so you can filter for it.
- An Imported from Incident.io link to the original, with a refresh icon to pull the latest data.
Related articles
Manage your incident log
Link imported incidents and track them to closure.
Create an incident
Add an incident by hand.