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

# Integrations Overview

> Connect DevHelm with Slack, PagerDuty, GitHub Actions, and more — all available integrations

DevHelm integrates with your existing tools for alerting, incident management, CI/CD, and observability. Set up an integration once and reference it from your [notification policies](/alerting/notification-policies) or CI/CD pipelines.

## Alert channels

Route incident notifications to your team through these integrations:

<CardGroup cols={3}>
  <Card title="Slack" icon="slack" href="/integrations/slack">
    Incoming webhook notifications.
  </Card>

  <Card title="PagerDuty" icon="pager" href="/integrations/pagerduty">
    Events API v2 trigger-resolve.
  </Card>

  <Card title="OpsGenie" icon="bell" href="/integrations/opsgenie">
    Alert API integration.
  </Card>

  <Card title="Discord" icon="discord" href="/integrations/discord">
    Webhook notifications.
  </Card>

  <Card title="Microsoft Teams" icon="microsoft" href="/integrations/teams">
    Incoming webhook connector.
  </Card>

  <Card title="Webhooks" icon="webhook" href="/integrations/webhooks">
    Custom HTTP endpoints with HMAC signing.
  </Card>

  <Card title="Email" icon="envelope" href="/integrations/email">
    Email notifications to any address.
  </Card>
</CardGroup>

### Channel lifecycle models

Alert channels have two delivery models. Understanding the difference helps you choose the right integration:

| Model               | Channels                              | Behavior                                                                                                  |
| ------------------- | ------------------------------------- | --------------------------------------------------------------------------------------------------------- |
| **Fire-and-forget** | Email, Slack, Discord, Teams, Webhook | Each notification is self-contained. Incident created and resolved messages are independent.              |
| **Trigger-resolve** | PagerDuty, OpsGenie                   | Opens an alert on incident creation and explicitly resolves it, maintaining state in the external system. |

For more details, see [Alert channels](/alerting/channels).

## CI/CD

Deploy monitoring configuration automatically from your CI/CD pipeline:

<CardGroup cols={2}>
  <Card title="GitHub Actions" icon="github" href="/integrations/github-actions">
    Official setup-devhelm action for automated deploys.
  </Card>

  <Card title="Generic CI/CD" icon="rotate" href="/integrations/generic-ci">
    Use the CLI in GitLab CI, Jenkins, CircleCI, and more.
  </Card>
</CardGroup>

## Observability

DevHelm can push incidents into your observability stack as events:

<CardGroup cols={3}>
  <Card title="Datadog" icon="dog" href="/integrations/datadog">
    Incidents as Datadog Events.
  </Card>
</CardGroup>

DevHelm does not currently **export metrics** (time-series data) to external platforms such as Prometheus or Grafana. To pull DevHelm data into another tool, you can also:

* **[Webhooks](/integrations/webhooks)** — push incident events to any HTTP endpoint with HMAC-signed payloads.
* **[REST API](/api-reference)** — pull monitor results, uptime stats, and incident history into your own pipeline.

If metrics export is critical to your workflow, please [open a request on GitHub](https://github.com/devhelmhq/mono/issues/new) so we can gauge demand.

## Next steps

<CardGroup cols={2}>
  <Card title="Alerting overview" icon="bell" href="/alerting/overview">
    Understand how channels fit into notification policies.
  </Card>

  <Card title="Alerting guide" icon="wrench" href="/guides/alerting">
    End-to-end guide for setting up alerting.
  </Card>
</CardGroup>