Configure email notifications for monitor alerts, incidents, and security findings.
Email Notifications
Email is the default notification channel in Seenty. It is available on all plans and requires no additional setup -- every organization automatically receives email alerts.
How it works
When a monitored event occurs (downtime, recovery, incident, SSL expiration, or new security finding), Seenty sends an email to the configured recipients. Emails are sent from notifications@seenty.com and include:
- Subject line with the alert type and affected resource (e.g., "Monitor DOWN: api.example.com").
- Alert details including the resource name, current status, timestamp, and relevant context.
- Direct link to the affected resource in your Seenty dashboard for quick investigation.
Default behavior
On the Hobby plan, email alerts are sent to the organization owner only. On Starter and higher plans, you can configure additional email recipients.
Email is always the first channel in any notification sequence. When a monitor fails and an incident is created, the on-call responder receives an email immediately -- before any delay-based channels (SMS, push) are triggered.
Email notifications for on-call incidents cannot be disabled. They serve as the baseline alert channel. Additional channels like SMS and Push are layered on top through your personal notification rules.
Configuration
Navigate to notification channels
Go to Integrations > Notification Channels.
Add an email channel
Click Add Channel and select Email. Enter the recipient email address and a friendly name for the channel (e.g., "DevOps Team Email").
Test the channel
Click Test to send a test notification to the configured email address. Check your inbox (and spam folder) to confirm delivery.
Assign to monitors
Add the email channel to the monitors or escalation policies that should use it.
Alert types
Email notifications are sent for the following events:
| Event | Description |
|---|---|
| Monitor Down | A monitor has detected that the target is unreachable or returning errors. |
| Monitor Up | A previously failing monitor has recovered. |
| SSL Expiration Warning | An SSL certificate is approaching its expiration date (configurable thresholds: 30, 14, 7, 3, 1 days). |
| Incident Created | A new incident has been triggered, either automatically by a monitor or manually. |
| Incident Updated | An incident has been acknowledged, had its severity changed, or received a new event. |
| Incident Resolved | An incident has been resolved. |
| Security Finding | A new critical or high-severity security finding has been detected. |
Troubleshooting
Not receiving emails?
- Check your spam or junk folder -- automated alert emails can sometimes be caught by spam filters.
- Add
notifications@seenty.comto your email contacts or safe sender list. - Verify that the email address configured in the channel is correct.
- If using a corporate email, check with your IT team whether the domain
seenty.comis allowed through your email gateway.
Receiving too many emails?
- Adjust your monitor check intervals to reduce the frequency of flapping alerts.
- Configure recovery confirmation (requiring multiple consecutive successful checks before sending an "Up" notification).
- Use escalation policies with appropriate delays to avoid duplicated alerts across channels.