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

# Integrations

AppSignal connects to the tools your team already uses, for notifications, issue tracking, hosting, log pipelines, and external dashboards. Choose a category to get started.

<CardGroup cols={2}>
  <Card title="Notifiers" icon="bell" href="/application/integrations/slack">
    Send incident, uptime, and trigger notifications to Slack, PagerDuty, Microsoft Teams, and more.
  </Card>

  <Card title="Issue trackers" icon="ticket" href="/application/integrations/github">
    Create and link issues in GitHub, GitLab, Jira, Linear, and more.
  </Card>

  <Card title="Hosting & platforms" icon="cloud" href="/heroku/setup">
    Set up AppSignal on Heroku, Render, Vercel, Kubernetes, and other platforms.
  </Card>

  <Card title="Forwarders / pipelines" icon="diagram-project" href="/vector">
    Forward logs and metrics to AppSignal through Vector and other pipelines.
  </Card>

  <Card title="Dashboards" icon="table-columns" href="/application/integrations/geckoboard">
    Show AppSignal metrics on external dashboards like Geckoboard.
  </Card>
</CardGroup>

<h2 id="notifiers">
  Notifiers
</h2>

Notifiers are integrations that connect a 3rd party with the goal of sending notifications for incidents, uptime issues and custom metric triggers.

Integrations include [Slack](/application/integrations/slack), [OpsGenie](/application/integrations/opsgenie), [PagerDuty](/application/integrations/pagerduty) and [Microsoft Teams](/application/integrations/teams), see below for a full list of notifiers. To enable notifications for external services, go to the ["Notifications" page](https://appsignal.com/redirect-to/app?to=notifiers)

<h3 id="available-notifiers">
  Available Notifiers
</h3>

* [Discord](/application/integrations/discord)
* [Google Hangouts Chat](/application/integrations/hangouts)
* [Microsoft Teams](/application/integrations/teams)
* [OpsGenie](/application/integrations/opsgenie)
* [PagerDuty](/application/integrations/pagerduty)
* [Slack](/application/integrations/slack)
* [Squadcast](/application/integrations/squadcast)
* [Webhook](/application/integrations/webhooks)

<h2 id="third-party-webhook-integrations">
  Third-Party Webhook Integrations
</h2>

Many third-party notifiers offer their own documentation for connecting to AppSignal via our Webhook. For more details, you can read their documentation:

* [All Quiet](https://docs.allquiet.app/integrations/inbound/appsignal)
* [ilert](https://docs.ilert.com/inbound-integrations/appsignal)
* [Squadcast](https://support.squadcast.com/integrations/alert-source-integrations-native/appsignal)
* [Zenduty](https://www.zenduty.com/docs/appsignal-integration/)

<h2 id="issue-trackers">
  Issue Trackers
</h2>

The second category are integrations with issue trackers such as [GitHub](/application/integrations/github), [GitLab](/application/integrations/gitlab), [Trello](/application/integrations/trello) and [Jira](/application/integrations/jira), amongst others.

Besides email notifications we can send messages about new exceptions to several 3rd parties. Below is a list of supported external services. Visit our ["Integrations" page](https://appsignal.com/redirect-to/app?to=integrations) in the app navigation and fill out the form for each service you'd like to enable.

Issue tracker integrations are personal: you set them up per app, and each person who wants to use one sets up their own. The **Integrations** page in your personal settings lists every personal integration you have across apps, and is where you remove one.

<h3 id="available-issue-trackers">
  Available Issue Trackers
</h3>

* [Asana](/application/integrations/asana)
* [Shortcut](/application/integrations/shortcut)
* [GitHub](/application/integrations/github)
* [GitLab](/application/integrations/gitlab)
* [Jira](/application/integrations/jira)
* [Trello](/application/integrations/trello)
* [Linear](/application/integrations/linear)

<h2 id="hosting--platforms">
  Hosting & platforms
</h2>

Deploy and monitor AppSignal on your hosting provider or platform, with guides for installation, deploys, and log collection.

<h3 id="available-platforms">
  Available platforms
</h3>

* [Heroku](/heroku/setup)
* [Render](/render/setup)
* [Vercel](/vercel/overview)
* [Kubernetes](/kubernetes/metrics)
* [Netlify](/logging/platforms/netlify)
* [Scalingo](/logging/platforms/scalingo)
* [Clever Cloud](/logging/platforms/clevercloud)
* [Gigalixir](/logging/platforms/gigalixir)
* [AWS CloudWatch](/logging/platforms/cloudwatch)

<h2 id="forwarders-/-pipelines">
  Forwarders / pipelines
</h2>

Forward logs and metrics to AppSignal through data pipelines, enriching or routing them before they arrive.

<h3 id="available-forwarders">
  Available forwarders
</h3>

* [Vector](/vector)
* [Vector with MongoDB](/vector/mongodb)
* [Vector with PostgreSQL](/vector/postgresql)

<h2 id="dashboards">
  Dashboards
</h2>

Dashboards can be used to show certain metrics such as error rates, response times and throughput for apps.

<h3 id="available-dashboards">
  Available Dashboards
</h3>

* [Geckoboard](/application/integrations/geckoboard)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.