Email is Tallwatch’s default channel. Every workspace ships with an auto-created one called Default Alerts, seeded with the creator’s address. You can add more email channels whenever you like, with up to 50 recipients each. Delivery runs through Resend. Before you rely on email in production, verify a sending domain (covered below). Until then, the sandbox sender only reaches your own address.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.
1. Add the channel
Pick Email
Choose the Email kind and name it for the audience, like
Billing stakeholders or Infra on-call.Add recipients
The recipient field takes one address per chip. Type an address, press Enter or comma, and it becomes a chip. Up to 50 per channel. Click the × to remove one, or hit Backspace in an empty field to drop the last.
The whole list goes out in one Resend call with every address in the
to field, so recipients can see each other. If you need stealth delivery to certain people, put them on a separate channel.What the alert looks like
A transactional HTML email:- The monitor name and incident status in the subject and heading
- A summary with failing regions, duration, and check error class
- A View incident button linking to the incident detail page
- A
List-Unsubscribeheader (RFC 8058) so inboxes can offer one-click unsubscribe
Custom sending domain
By default, alerts come fromonboarding@resend.dev, Resend’s sandbox sender. The sandbox can only deliver to the address that owns your Resend account, so set up a real domain before production.
Verify a domain in Resend
Add your sending domain (for example
tallwatch.yourcompany.com) in the Resend dashboard, then add the SPF, DKIM, and DMARC records it gives you to your DNS.Set the from address
In Settings → Email, set From address to something like
Alerts <alerts@tallwatch.yourcompany.com>. The Name <addr> form renders a friendly sender name.Troubleshooting
The test dispatched, but no email arrived
The test dispatched, but no email arrived
Check the Resend dashboard for the send. Usual causes:
- You’re still on the sandbox sender and the recipient isn’t your Resend account owner. Verify a domain (above).
- The inbox flagged it as spam. Check the spam folder, and set up SPF, DKIM, and DMARC on your domain to improve deliverability.
- A recipient address has a typo. Open the channel and confirm each chip.
Some recipients get it, others don't
Some recipients get it, others don't
Usually a per-recipient bounce: a misspelled address, a closed mailbox, or a corporate filter. Resend’s dashboard shows per-recipient state. Remove dead addresses from the channel.
Someone clicked unsubscribe and now gets nothing
Someone clicked unsubscribe and now gets nothing
Resend honors the unsubscribe through its account-wide suppression list, which blocks every email to that address, including alerts. To undo it, the recipient opts back in or you remove the suppression in Resend.
Should I make one channel per recipient?
Should I make one channel per recipient?
Rarely. One channel with 50 chips is a single Resend call; 50 single-chip channels are 50 calls and 50 rows to manage. Split only when recipients need different escalation routing.
Reference
| Property | Value |
|---|---|
| Channel kind | email |
| Required config | to (1 to 50 addresses) |
| Sending domain | onboarding@resend.dev by default; verify your own per workspace |
| Delivery | Immediate, no proactive rate limit |
| Retry | Up to 3 inline attempts on a Resend 5xx, 429, or network error, then failed |
| Outbound to | Resend API |