Get InfraNest alerts in the inbox you already watch
The simplest alert destination to set up — just an address, nothing else
Email is the alert destination that needs nothing from another service — just the address you want messages sent to.
- No setup on the other end: unlike chat-based destinations, email needs no webhook, bot or API key, so there's nothing to configure outside InfraNest.
- Routed per object: a monitor, server, DNS zone or domain can each send its alerts to a different address, so you're not stuck with one inbox for everything.
- Works with distribution lists: point a destination at an address your mail provider manages to alert a whole team, not just one person.
NoteThis is separate from your personal notification settings — changing what you receive as a user is done elsewhere in your account, while a destination controls where an organisation's alerts go.
What it looks like in InfraNest
Or let an automation act on it
What you can do
Once Email is connected, this is what InfraNest can do with it.
- No webhook, bot or API key required
- Per-object routing to different addresses
- Built-in test send
- Works with mail-provider distribution lists
How to connect it
- 1
Open Alerts → Destinations
Go to Alerts → Destinations in InfraNest.
- 2
Add an Email destination
Select Add a destination, choose Email, and enter the address alerts should go to.
- 3
Send a test message
Select Test to confirm the address receives it, then check for typos or spam filtering if it doesn't arrive.
- 4
Save and start routing alerts
Save the destination, then choose Email when deciding which alerts a monitor, server, DNS zone or domain should send.
That’s it — Email is connected.
Full setup guideQuestions
#Do I need to set up anything on the email side first?
No. Unlike Slack, Teams, Discord or Telegram, email needs no webhook, bot or API key — just an address you watch.
#Can different alerts go to different addresses?
Yes. Routing is chosen per object, so a monitor, server, DNS zone or domain can each send to a different email destination.
#What happens if I stop watching the address I connected?
InfraNest keeps sending to whatever address is saved on the destination, so alerts will go unseen if nobody checks it. Update the address in Alerts → Destinations, or add a second destination for another recipient.
#Can InfraNest send to a team inbox instead of one person?
Yes — point the destination at a distribution list your mail provider manages, rather than an individual address.
#Why didn't the test message arrive?
Check your spam folder first, then confirm the address is spelled correctly. Some mail providers hold the first message from a new sender.
Often connected together
One dashboard for every provider
Add this integration, then the rest of your stack — domains, DNS, servers, certificates and monitoring in one place.
Free plan · No credit card required · Set up in minutes