Monitor Resend.Hear only when it matters.
Catch a sending domain going unverified before your email quietly stops arriving.
What Beaam does with Resend
Beaam reads each Resend sending domain's deliverability over the last 24 hours — bounce rate, complaint rate, delivery rate — and checks the domain is still verified. Email fails quietly: a domain whose DNS record was removed keeps accepting API calls and simply stops arriving.
What raises an incident
Curated deliberately: a short list worth your attention, not every metric that exists. Signals that can blip need repeated evidence before Beaam calls them; a reading that is definitive by nature — the provider reporting a failure outright — alerts on the first observation.
| Signal | When Beaam speaks up |
|---|---|
| Domain can send | Domain no longer verified → broken. |
| Bounce rate | After at least 25 messages: ≥ 3% over 24h → degraded; ≥ 4% (Resend's limit) → broken. |
| Complaint rate | Of delivered mail, after at least 1,250 deliveries: ≥ 0.06% → degraded; ≥ 0.08% (Resend's limit) → broken. |
| Failed email | One or more failed sends over 24h → degraded after confirmation. |
Also collected, but quiet
Charted on the service page and there for context when something does break — but it will not wake you unless you ask it to.
- Emails sent
- Bounces
- Bounce categories
- Delivery failures
- Delivered and received
- Spam complaints
- Delivery rate
What connecting needs
- Resend offers two kinds of access, full and sending-only, and reading domains needs full access. So sign-in requests
full_access, and an API key must be Full access — a grant that could send mail as your domain. Beaam never sends mail. - One Resend account per organization.
- Where Resend's metrics endpoint is not available on your account, Beaam falls back to the sent-mail list, capped at 2,000 messages.
What Beaam will not tell you
Stated rather than discovered later. Some of these are deliberate — an alert that is not about your system is noise — and some are simply where this integration's view ends.
- No rates on days with no mail. A bounce-rate alert waits for 25 sends, a complaint-rate alert for 1,250 deliveries.
- Opens and clicks are not alerted on.
- Resend's webhook events never stand in for liveness: a quiet webhook is not read as healthy.
- Resend publishes no change events, so there is nothing to correlate an incident against.
setup
Designed to stay small
Sign in with Resend — no key to create. Beaam watches every sending domain's bounce and complaint rates.
Beaam applies sensible defaults. Threshold configuration is optional, not onboarding.
access
One write, and revocable
Connecting creates one webhook in your Resend account, pointed at Beaam, so bounces and complaints arrive as they happen. A failed connect removes it again, and so does disconnecting. If Resend refuses, Beaam tells you which webhook to delete on its Webhooks page.
Beaam never changes your infrastructure. Credentials are encrypted with AES-256-GCM using a key held as a deploy secret, and are deleted immediately when you disconnect.
Questions
What does Beaam alert on for Resend?
4 signals can raise an incident: Domain can send, Bounce rate, Complaint rate, Failed email. Everything else is collected for context but stays quiet until you opt in.
How long does it take to connect Resend?
Sign in with Resend — no key to create. Beaam watches every sending domain's bounce and complaint rates. Most connections are watching within a few minutes, and you can send a test alert immediately to prove the path works end to end.
Does Beaam need write access to Resend?
No. Beaam only ever performs read operations — there is no code path that writes to a connected provider. Worth separating from that: what Beaam *does* and what a token *permits* are different things. Where Resend offers a read-scoped credential, use it; some providers only issue tokens carrying broader rights than Beaam uses, which is a property of their API rather than of Beaam's behaviour. Scope it as narrowly as the provider allows. Credentials are encrypted with AES-256-GCM before storage and deleted the moment you disconnect.
What does Resend monitoring cost?
The free plan covers two integrations and five watched services, with email, Slack and webhook alerts. Solo is $19/month flat for unlimited integrations, services and organizations, with collaborators included — there is no per-host, per-check or per-alert metering.
Watching more than Resend?
Most stacks are several services with seams between them, and the seams are where the damaging failures hide. Beaam correlates across every connected integration, so a database problem reads as one incident rather than five alarms from five tools.