---
title: Alerts | ReplayPilot Docs
description: Get a webhook or email the moment a session ends with an error.
canonical: https://replaypilot.com/docs/alerts
---

# Alerts | ReplayPilot Docs

Search docs…⌘KBrowse docs

Get started
- [Installation](/docs/getting-started)
- [What's new](/docs/whats-new)

Dashboard
- [Replays & the session player](/docs/replays)
- [Errors](/docs/errors)
- [Frustration signals](/docs/frustration)
- [Funnels](/docs/funnels)
- [Releases](/docs/releases)
- [Logs & network requests](/docs/logs)
- [Visitors](/docs/visitors)
- [Heatmaps](/docs/heatmaps)
- [Click map](/docs/click-map)
- [Cohort retention](/docs/cohorts)
- [Projects & project keys](/docs/projects)
- [Alerts](/docs/alerts)
- [Shared links](/docs/shared-links)

Integrations
- [Integrations](/docs/integrations)
- [MCP server](/docs/mcp-server)

Account & data
- [Billing & plans](/docs/billing)
- [Security & masking](/docs/security-masking)
- [Data retention & limits](/docs/retention-limits)
- [Team accounts](/docs/team-accounts)

# Alerts

Get a webhook or email the moment a session ends with an error.

## How alerts work

The Alerts page has two tabs: **Rules**, where you set up what should notify you, and **Delivery log**, where you see what went out.

An alert rule watches your project and sends a notification when something matches it. You choose what counts as a match, and which of your connected integrations should hear about it.

## The three kinds of rule

Every rule is one of three types:

- **Any error**: fires when any error happens in the project.

- **Any frustration signal**: fires when a visitor rage-clicks or dead-clicks something. See [Frustration signals](/docs/frustration) for what those mean.

- **Error rate**: fires when your project's recent error rate crosses a threshold you choose, from 1% to 100%. ReplayPilot calculates it over the project's last 50 sessions.

Every new project starts with an "any error" rule and an "any frustration" rule already turned on, so you get useful alerts from day one. Turn either off, or add more rules, on the Rules tab. [Projects & project keys](/docs/projects) covers new projects and their starting keys.

## Choosing where alerts go

Each rule can notify any number of your connected integrations: webhook, Slack, email, GitHub, Discord, Linear, GitLab, or Jira. Tick the ones you want on the rule itself.

You need to connect an integration before you can pick it here. See [Integrations](/docs/integrations) for how to connect one.

If two rules both match the same event and both point at the same integration, you still get one notification, not two. ReplayPilot de-duplicates by integration, not by rule.

Email alerts are available on Growth ($79/mo), Scale ($150/mo), and Enterprise. On Free or
Starter, ReplayPilot logs an email alert that would have fired as **skipped** instead of sending
it. Webhook and every other integration type work on every plan, subject to Free's
three-integration limit.

Saving a rule's integration list is all-or-nothing. ReplayPilot verifies that every selected integration belongs to the same project and is enabled and connected; if any selection is unavailable, the previous rule remains unchanged.

## When a rule fires

ReplayPilot checks alert rules at different points, depending on where the event comes from:

- For a session recording, it checks when the session **ends**.

- For an error reported through Sentry, it checks as soon as the error **comes in**.

If you add or change a rule, it applies to new sessions and new errors from that point on. A session that was already in progress when you made the change keeps using the rules that were active when it started.

## The delivery log

The Delivery log tab shows your most recent 200 deliveries for the project. For each one, you can see which integration it went to, which rule triggered it, and its status: **sent**, **failed**, or **skipped**. Where the delivery came from a session, there's a link straight to it.

If an integration's credentials stop working, for example a Slack token you revoked, ReplayPilot flags it **Reconnect** in the log instead of silently failing. Head to [Integrations](/docs/integrations) to reconnect it.

[← Projects & project keys](/docs/projects)[Shared links →](/docs/shared-links)