Incident.io

Incident.io: Overview and setup

Automate incident creation and management with the Incident.io integration.

The Incident.io integration connects incident monitoring directly to your Atomicwork workflows, enabling your IT and engineering teams to seamlessly create, manage, and track incidents in one place, without switching platforms.

Your teams can automatically create incidents when critical alerts are detected, update incident severity and status as situations evolve, and notify Slack incident channels. This accelerates incident response, reduces context switching, and ensures critical issues are tracked consistently.

Usecases

By connecting Incident.io, your teams can:

Automate incident creation: Trigger incident creation in Incident.io when critical alerts or events are detected in Atomicwork.
Incident lifecycle management: Update incident severity, status, and details as part of escalation or resolution workflows.
Incident tracking: List and retrieve incidents for dashboards, reporting, or status checks.
Slack integration: Notify incident channels in Slack when incidents are updated.
Retrospective incidents: Create retrospective incidents for post-mortem analysis.

Permissions

To connect Incident.io with Atomicwork, you need:

Org admin access on Atomicwork
An Incident.io API key with the following scopes:

Permission	Purpose

Action	Description
Create incident	Create a new incident with name, summary, visibility (public/private), severity, mode (standard/retrospective/test/tutorial), status, and type. Includes idempotency key to prevent duplicate creation.
Get incident	Retrieve details of a specific incident by ID.
Update incident	Update an incident's name, summary, severity, or status. Optionally notify the Slack incident channel.
List incidents	List incidents with pagination and status category filtering.
Call API	Execute a generic API call to any Incident.io endpoint.

Error	Cause	Resolution
"api_key is null" or "No valid API key available"	The integration configuration is missing the API key or it's blank.	Re-enter your API key in the integration settings.
Invalid Incident.io API key (401)	The API key is invalid or has been revoked.	Generate a new API key in the Incident.io dashboard with the required permissions.
API key does not have permission to list severities (403)	The API key lacks the required permissions.	Ensure your API key has read access to severities, statuses, types, and incidents in the Incident.io dashboard.
4xx Client Errors	Invalid incident ID, bad request body, or missing required fields.	Verify the incident ID exists, check that all required fields are provided, and ensure request body formatting is correct.
5xx Server Errors	Incident.io API may be experiencing issues.	Check the Incident.io status page and retry later.

Incidents: Read	To list and retrieve incident details.
Incidents: Write/Create	To create and update incidents.
Severities: Read	To list configured severity levels and validate the API key during setup.
Incident Statuses: Read	To list all configured incident statuses.
Incident Types: Read	To list all configured incident types.

Incident.io

Incident.io

Incident.io: Overview and setup

Usecases

Permissions

Incident.io

Incident.io

Incident.io: Overview and setup

Usecases

Permissions

Setup

Supported workflow actions

Troubleshoot common errors