---
title: "Connect Honeybadger"
description: "Send Honeybadger errors, uptime checks and check ins to Firefight through the Webhook integration."
canonical: https://firefight.app/docs/alerts/honeybadger
---

# Connect Honeybadger

Firefight has a dedicated alert source for Honeybadger. Errors, uptime checks and check ins each become alerts that resolve when Honeybadger says they are resolved, back up or reporting again.

## Set up the Firefight side

Go to **Settings → Alert Sources**, click **Add source**, give it a name like "Honeybadger production", and pick the **Honeybadger** provider. When you create it, Firefight opens the source's setup. It shows the ingest URL and a **Copy token** button for the source's secret token, and the same steps as this page.

## Set up the Honeybadger side

1. In Honeybadger, open the project's settings, then **Alerts & Integrations**, and choose **Webhook**.
2. Paste the ingest URL as the URL.
3. Paste the token into the **Bearer token** field and save.

Requests that fail the check are rejected with `401`, and the source's row in **Settings → Alert Sources** shows the rejection.

## What Firefight reads

Each alert gets these fields, which you can match in your [routing rules](https://firefight.app/docs/alerts/routing-rules.md).

| Field | Value |
|---|---|
| `title` | The error's class and message, the site that is down, or the check in that is missing |
| `description` | Honeybadger's message |
| `service` | The Honeybadger project |
| `environment` | The error's environment |
| `url` | The error occurrence, the uptime check or the check ins page in Honeybadger |

The alert's title in Slack and on the dashboard links to its page in Honeybadger.

## Firing and resolving

An error fires when it occurs, is unresolved or passes its rate, and every later notice counts on the same alert until the error is resolved in Honeybadger. An uptime check fires when the site goes down and resolves when it is up. A check in fires when it is missing and resolves when it reports again. Other events, such as assignments, comments and deploys, are accepted and ignored.

See [Grouping & deduplication](https://firefight.app/docs/alerts/grouping-and-deduplication.md) for how repeat firings collapse into one alert.