Most server alerting starts the same way: you curl a Slack webhook from a health-check script, or you point your monitoring SaaS at an SMTP relay, and you call it a day. That works right up until the thing you're alerting about is the thing that breaks the alert. The box that can't reach the internet can't curl Slack. The relay credentials expire and every cron alert silently vanishes for a month before anyone notices. And the moment you're on a bare VM, an air-gapped build node, or a customer's on-prem box, "just install Postfix and configure SPF" turns a five-minute task into an afternoon.
What you actually want for a whole category of alerts — cron failures, backup reports, threshold breaches, deploy summaries, nightly audit digests — is dead simple: a real email address you own, that any machine with a single binary can send from, with no mail server to babysit. That's what a Nylas Agent Account plus the Nylas CLI gives you, and that's what this post builds.
I work on the Nylas CLI, so the terminal commands below are the exact ones I reach for. I'll show both angles for every operation — the nylas command and the raw curl HTTP call — because in practice your scripts shell out to the CLI but your services hit the API, and you'll end up wanting both.
