Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.tallwatch.com/llms.txt

Use this file to discover all available pages before exploring further.

Email is Tallwatch’s default delivery channel. Every workspace ships with an auto-created email channel called Default Alerts seeded with the workspace creator’s email. You can add more email channels at any time and put up to 50 recipients on each one. The email itself is delivered through Resend and includes a one-click unsubscribe header so recipients can opt out without needing dashboard access.

​
Before you start

  • The email addresses you want alerts to go to. Distribution lists work fine (e.g. oncall@yourcompany.com).
  • If you want emails from your own domain, you’ll need to verify a sending domain — see Custom sending domain below.

​
Step 1: Add the channel

1

Open the channels page

Go to Settings → Alerts → Channels in the dashboard and click Add channel.
2

Pick Email

Select the Email kind. Give the channel a name that describes the audience: Billing stakeholders, Infra on-call, Founders.
3

Add recipients

The recipient field is a chip input. Type an email, press Enter or comma, and the address turns into a chip. Repeat for each recipient. Max 50 per channel.Click the × on a chip to remove an address. Hit Backspace in an empty input to remove the last chip.
4

Save and test

Click Save, then click Send test alert. Every recipient should receive the test email within a few seconds.
The recipient list is sent as a single Resend API call with the array as the to field. Every recipient is visible to every other recipient — no bcc obscuring. If you need stealth delivery to specific addresses, create separate channels for them.

​
What the alert looks like

A clean, transactional-style HTML email with:
  • The monitor name and incident status in the subject line and the heading
  • A summary block with failing regions, duration, and check error class
  • A primary View incident button linking to the incident detail page
  • The List-Unsubscribe header (RFC 8058) so inbox providers offer one-click unsubscribe
A plain-text fallback is generated automatically for clients that don’t render HTML.

​
Default Alerts auto-channel

Every new workspace has a Default Alerts channel auto-created with the creator’s email and synced to all members as they join. Read Default Alerts for how to opt out and when to outgrow it.

​
Custom sending domain

By default, emails come from onboarding@resend.dev — Resend’s sandbox sender. The catch: the sandbox can only deliver to the email address that owns the Resend account. For production use, set up a custom sending domain.
1

Verify a domain with Resend

In your Resend dashboard, add the domain you want to send from (e.g. tallwatch.yourcompany.com). Add the SPF + DKIM + DMARC records Resend provides to your DNS.
2

Update Tallwatch

Open Settings → Email in the dashboard and set the From address to something like Alerts <alerts@tallwatch.yourcompany.com>. The RFC-822 Name <addr> form renders a friendly sender name in inbox clients.
3

Confirm delivery

Send another test alert. Resend’s dashboard shows the delivery result and the recipient inbox should show the new sender.
Until your sending domain is verified, alerts to anyone other than the Resend account owner will silently fail. Resend marks them as bounced in their dashboard but the failure is opaque from Tallwatch. Set up a sending domain before relying on email for production alerts.

​
Troubleshooting

Check the Resend dashboard for the delivery status of the send. Common causes:
  • You’re still on the sandbox sender (onboarding@resend.dev) and the recipient isn’t your Resend account owner. Verify a sending domain — see above.
  • The recipient inbox marked the message as spam. Check the spam folder. Improve deliverability by setting up SPF/DKIM/DMARC on your sending domain.
  • The recipient address has a typo. Open the channel and confirm each chip is the address you expect.
Usually a per-recipient bounce — a misspelled address, a closed mailbox, or a corporate firewall. Resend’s dashboard shows per-recipient delivery state. Remove dead addresses from the channel.
Resend honours the unsubscribe via its suppression list. Once an address is suppressed for your account it will not receive any more emails from you, including alerts. To re-subscribe, the recipient must opt back in (or you remove the suppression in Resend’s dashboard).
You can, but it’s usually wasteful. A single channel with 50 chips is one Resend API call. 50 channels with one chip each is 50 calls and 50 channel rows to manage. Use multiple channels only when you want different escalation routing per recipient.

​
Reference

PropertyValue
Channel kindemail
Required configto (1-50 email addresses, array)
Sending domainonboarding@resend.dev by default; verifiable per workspace
Send rate limit1 per 30 s per channel (queued, not dropped)
Retry policyUp to 3 attempts on 5xx, then queued for the next 30-s slot
Outbound toResend API