> ## Documentation Index
> Fetch the complete documentation index at: https://docs.squasher.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations overview

> Find the integration you need: notification and paging tools, inbound alert sources, code and issue trackers, and migrations from other tools.

Integrations connect Squasher to the tools your team already uses to respond to incidents. To send
errors, logs, traces, or metrics into Squasher from a platform such as Vercel, Railway, AWS, or
Kubernetes, see [Choose how to send data](/integrations/logging-overview).

## Notifications and paging

Send incident notifications to the places responders already watch. Routing rules live in
[Notifications and alert routing](/features/alerts).

| Integration                          | What it does                                                                       |
| ------------------------------------ | ---------------------------------------------------------------------------------- |
| [Slack](/integrations/slack)         | Use Squasher from Slack channels your team already uses.                           |
| [Telegram](/integrations/telegram)   | Send Squasher incident notifications to a Telegram chat or forum topic.            |
| [PagerDuty](/integrations/pagerduty) | Route Squasher incidents to PagerDuty and migrate responder schedules when needed. |

## Inbound alert sources

Open, update, and resolve Squasher incidents from alerts raised by other monitoring systems. Start
with [Inbound alert connectors](/integrations/alert-connectors).

| Source                                                                    | What it does                                                                     |
| ------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
| [AWS CloudWatch alerts](/integrations/aws-cloudwatch-alerts)              | Turn signed CloudWatch alarm transitions delivered by Amazon SNS into incidents. |
| [Datadog monitor alerts](/integrations/datadog-alerts)                    | Send Datadog monitor lifecycle transitions to Squasher incidents.                |
| [Grafana Alerting](/integrations/grafana-alerts)                          | Turn Grafana webhook contact-point notifications into Squasher incidents.        |
| [Prometheus Alertmanager](/integrations/prometheus-alertmanager)          | Send Alertmanager webhook v4 notifications to Squasher incidents.                |
| [PagerDuty Events API v2 inbound](/integrations/pagerduty-events-inbound) | Accept Events API v2-compatible alert lifecycles as Squasher incidents.          |
| [Generic alert webhook](/integrations/generic-alert-webhook)              | Raise and resolve Squasher incidents from any alerting system over HTTPS.        |

## Code, issues, and context

| Integration                    | What it does                                                                |
| ------------------------------ | --------------------------------------------------------------------------- |
| [GitHub](/integrations/github) | Link repositories and open pull requests for hosted fix runs.               |
| [Linear](/integrations/linear) | Create and update Linear issues from new Squasher error groups.             |
| [Notion](/integrations/notion) | Connect selected Notion pages and data sources for read-only agent context. |

## Migrate from another tool

| From               | Guide                                                                                    |
| ------------------ | ---------------------------------------------------------------------------------------- |
| Sentry             | [Migrate from Sentry](/integrations/sentry)                                              |
| Datadog            | [Migrate from Datadog](/migrations/datadog-to-squasher)                                  |
| Better Stack       | [Migrate from Better Stack](/migrations/betterstack-to-squasher)                         |
| Axiom              | [Migrate from Axiom](/migrations/axiom-to-squasher)                                      |
| Splunk HEC         | [Migrate from Splunk HEC](/integrations/splunk-hec)                                      |
| Loki               | [Migrate from Loki](/integrations/loki)                                                  |
| Grafana OnCall     | [Migrate from Grafana OnCall](/migrations/grafana-oncall-to-squasher)                    |
| Opsgenie           | [Migrate from Opsgenie](/integrations/opsgenie)                                          |
| A Vercel log drain | [Move from a Vercel drain to the Squasher SDK](/migrations/vercel-drain-to-squasher-sdk) |

## Manage integrations from code

Agents and scripts can list integration setup metadata with the [Integrations API](/api-reference/integrations)
and manage provider connections with the [Provider connections API](/api-reference/provider-connections).
The CLI can start browser-backed setup for supported providers; see
[CLI sign-in and integration setup](/integrations/cli-oauth).