# How we approach integrations at incident.io

DevFeed: [How we approach integrations at incident.io](<https://devfeed.tech/articles/how-we-approach-integrations-at-incident-io-11810.md>)

Original publisher: [Read original article](<https://incident.io/blog/how-we-approach-integrations>)

Author: Chris Evans

Published: 2023-01-23T00:00:00Z

Content type: opinion

Language: en

Sources: [The incident.io Blog](<https://devfeed.tech/sources/the-incident-io-blog.md>)

Topics: [incident management](<https://devfeed.tech/topics/incident-management.md>), [Incident response](<https://devfeed.tech/topics/incident-response.md>), [Software as a service](<https://devfeed.tech/topics/saas.md>), [Notion](<https://devfeed.tech/topics/notion.md>)

Tags: [incident](<https://devfeed.tech/tags/incident.md>), [incident-channel](<https://devfeed.tech/tags/incident-channel.md>), [incident-management](<https://devfeed.tech/tags/incident-management.md>), [incident-response](<https://devfeed.tech/tags/incident-response.md>), [integrations](<https://devfeed.tech/tags/integrations.md>), [on-call](<https://devfeed.tech/tags/on-call.md>), [outage](<https://devfeed.tech/tags/outage.md>), [post-mortem](<https://devfeed.tech/tags/post-mortem.md>), [saas](<https://devfeed.tech/tags/saas.md>), [slack-incident](<https://devfeed.tech/tags/slack-incident.md>)

## AI overview

The article explains why incident.io focuses on integrations instead of building every adjacent capability itself. It presents integrations as a strategic way to connect with tools organizations already use, including tools that may appear competitive, while positioning incident.io as a hub for incident management. The approach relies on specialized products such as PagerDuty, Opsgenie, and Jira for parts of the incident response process, including on-call paging.

## Source excerpt

Here are incident.io we have dozens of integrations with SaaS tools. But why have we not built out own versions of these tools? Simply put, we can't do everything.