---
title: "Connect Axiom"
description: "Send Axiom monitor alerts to Firefight through a Custom webhook notifier."
canonical: https://firefight.app/docs/alerts/axiom
---

# Connect Axiom

Firefight has a dedicated alert source for Axiom monitors. A Custom webhook notifier with its default body sends each monitor's alerts, and a threshold monitor resolves in Firefight when it closes.

## Set up the Firefight side

Go to **Settings → Alert Sources**, click **Add source**, give it a name like "Axiom production", and pick the **Axiom** 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 Axiom side

1. In Axiom, open **Monitors → Manage notifiers** and create a notifier of type **Custom webhook**.
2. Paste the ingest URL as the **Webhook URL** and keep the default body.
3. Add a header named `X-Firefight-Token` holding the token, then create the notifier.
4. Choose the notifier on each monitor that should alert.

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 monitor's name |
| `description` | The monitor's message, such as the value against its threshold |

## Firing and resolving

A monitor fires an alert when it opens and resolves it when it closes. A monitor that notifies by group gets one alert per group. A match monitor never closes, so its alerts stay firing. Resolve one by hand with **Resolve** on the **Alerts** page once it is dealt with.

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