---
title: Email alerts
description: Send Glowo alerts to an email address, with one-click acknowledge and pause links.
sidebar:
  icon: mail
  label: Email
---

{/* Source of truth: packages/shared/src/notifications.ts — emailChannelSchema.
    Action links: packages/shared/src/routes.ts notifications.actions.* */}

The simplest channel, and the one worth having even if you rely on something
else day to day.

## Configuration

| Field | Value |
| --- | --- |
| `address` | A single valid email address |

One address per channel. For a team, either point it at a distribution list you
already run, or create one channel per person — the second option lets you scope
each person to different monitors.

## One-click actions

Glowo alert emails carry action links so you can respond without opening the
dashboard:

- **Acknowledge** — silences repeat alerts for the current episode. One click,
  no confirmation step.
- **Pause** — opens a confirmation page first, then pauses the monitor.
- **Resume** — restarts a paused monitor.

These links are signed, bound to a single alert episode, and expire. The
acknowledge link is safe to click more than once; the pause link is single-use
and deliberately requires the extra confirmation, so that a mail client
prefetching links cannot pause your monitors.

See [Acknowledging alerts](/alerting/acknowledging) for what acknowledgement
actually does.

## Deliverability

Email is the channel most likely to be delayed or filtered, which makes it a
poor sole channel for anything urgent.

- Add the Glowo sending domain to your allow-list.
- Check spam filtering before you trust it for on-call.
- For anything that needs to wake someone, pair it with
  [SMS](/alerting/sms) or [PagerDuty](/alerting/pagerduty).

:::note
Email is not rate limited per recipient by Glowo, but your mail provider may
throttle a burst. A monitor that flaps can generate a lot of mail — tune
[confirmations](/monitors/confirmations) rather than muting the channel.
:::