[ TUTORIAL ]

Set up NightOwl with free SendGrid SMTP

Industry-standard transactional SMTP on a $0 100/day tier in about 10 minutes. Six steps, screenshots, no card.

QUICK ANSWER

Can I use SendGrid's free tier for NightOwl alerts?

Yes — SendGrid (Twilio SendGrid) gives you 100 emails/day free forever. Plug smtp.sendgrid.net:587 + the literal string `apikey` as username + an SG.xxx API key as password into NightOwl's email channel form. The 100/day cap is the tightest of the major free transactional providers (Brevo gives 300/day, Resend gives 100/day inside 3,000/month), but SendGrid has the strongest brand recognition for compliance contexts.

Updated · 2026-04-27

What you'll have at the end

A configured email alert channel in NightOwl that sends through SendGrid with a 100/day free quota and 5-20 second delivery on quiet sends. New issues, resolved issues, missed scheduled tasks, and queue failures land in your inbox.

END STATE

What you're aiming for: NightOwl alerts arriving via SendGrid within 5-20 seconds, from your verified sender.

Why SendGrid's free tier works for NightOwl

Three properties make SendGrid a credible free-tier choice — even if not the most generous:

  • 100 emails/day forever — enough for most Laravel alert volumes since NightOwl groups exceptions by fingerprint (one issue.new alert per new fingerprint, not per occurrence).
  • Industry-standard brand — for compliance, audit, or contractual contexts that ask "what's your transactional provider?", SendGrid is universally recognized.
  • Mature deliverability tooling — Activity Feed, suppression lists, bounce handling, and event webhooks all work on the free tier.

Three catches worth knowing up front:

  • Free-tier IP pool deliverability has been uneven post-Twilio. Reports of corporate Outlook and Gmail-for-Business inboxes flagging SendGrid free-tier mail are common since 2022. Domain authentication helps significantly. This is SendGrid's free tier, not NightOwl — verify in SendGrid's Activity Feed where you'll see "Delivered" vs. "Bounced" vs. "Deferred" per recipient.
  • 100/day cap is tight. A noisy app can blow through this fast. Hitting the cap returns HTTP 401/429 on the SMTP transaction. NightOwl retries, but sustained overrun stalls alerts.
  • The literal-string-`apikey`-as-username convention surprises everyone. If you use your account email as the username (the obvious choice), auth fails. Use the literal four-character string.

Step 1 — Sign up for SendGrid free

Head to sendgrid.com/free and create an account. The free 100/day tier doesn't require a credit card. SendGrid's onboarding asks for company details — answer honestly; their anti-abuse heuristics tune on the responses, and accounts that look like throwaways sometimes get held for manual review.

STEP 01

The free tier is the default. SendGrid will prompt for marketing-email setup during onboarding — skip those if you only want transactional.

Step 2 — Verify a sender

In the SendGrid dashboard, go to Settings → Sender Authentication. You have two options:

  • Single Sender Verification — fastest. Enter the email address you want NightOwl alerts to come from, click the link in the validation email. Done in a minute.
  • Domain Authentication — better. Add CNAME records to your DNS to authenticate the whole domain. Unlocks branded sending and significantly better deliverability. 5 minutes plus DNS propagation.

Start with Single Sender if you just want a working test alert. Plan to do Domain Authentication before going to production — SendGrid's deliverability gap between unauthenticated and authenticated domains is meaningful.

STEP 02

Single sender works for a test alert. Domain authentication is the production answer.

Step 3 — Create an API key with Mail Send permission

Go to Settings → API Keys → Create API Key. Name it "NightOwl". For permissions, pick Full Access (simplest) or Restricted Access with Mail Send explicitly enabled (more secure).

SendGrid shows the key once, prefixed SG.. Copy it. If you lose it, generate another and revoke the old.

STEP 03

The API key is the SMTP password. If you choose Restricted Access, make sure Mail Send is explicitly toggled on — it's not in the default-on set.

Step 4 — Open the NightOwl email channel form

Sign in to the NightOwl dashboard. Pick your application, then go to Settings → Issues. Scroll to the Email section and click Configure SMTP (or Add another if you already have an email channel).

STEP 04

The Email section lives under the Issues tab alongside Integrations (Slack/Discord) and Webhooks.

Step 5 — Fill in SendGrid's SMTP settings

Plug these values into the NightOwl email channel form:

Field Value
Channel NameOn-call Email
Hostsmtp.sendgrid.net
Port587
EncryptionTLS
Usernameapikey
Password<SG.... API key from Step 3>
From Address<the verified sender from Step 2>
From NameNightOwl Alerts
To Addressesteam@yourdomain.com

The Username is literally the four-letter string apikey — not your email, not your account name. This is SendGrid's convention; the API key is what authenticates.

The From Address must be a verified sender (or any address on an authenticated domain).

STEP 05

If the test step fails with auth errors, the most common cause is using your account email as the username instead of the literal string 'apikey'.

Step 6 — Test, then subscribe to alert events

Save the channel and click Send Test. NightOwl fires a synthetic alert through SendGrid. Quiet sends arrive in 5-20 seconds. Cross-check SendGrid's Activity → Activity Feed — every send shows there with "Processed → Delivered → (Open)" timestamps.

Then tick which of the four issue-lifecycle events fire emails:

  • issue.new — a new exception fingerprint appears (always on)
  • issue.reopened — a previously-resolved issue fires again (recommended on)
  • issue.resolved — issue triaged closed (optional)
  • issue.ignored — issue muted (optional)

For solo triage, leave all four on. For team triage, just issue.new + issue.reopened avoids duplicate notifications. With SendGrid's tight 100/day cap, leaving lifecycle events off is also a way to conserve quota for what matters most.

STEP 06

Cross-reference NightOwl's last-delivery time with SendGrid's Activity Feed to confirm end-to-end success.

When to upgrade to SendGrid Essentials

Three signals it's time to leave the free tier:

  • You hit 100/day during a real incident — Essentials at $19.95/mo lifts to 50,000/month with no daily cap.
  • Deliverability to enterprise mailboxes is uneven — Essentials and Pro get progressively better IP pools; Pro+ unlocks dedicated IP for sender reputation isolation.
  • Compliance needs longer log retention — free tier keeps Activity Feed for 3 days; paid tiers go to 30+ days.

SendGrid vs Resend vs Brevo vs Gmail

All four work as NightOwl alert channels. Quick decision matrix:

  • SendGrid — strongest brand for compliance, smallest free tier (100/day), uneven free-tier deliverability since the Twilio acquisition.
  • Resend — fastest delivery, branded sender, 3,000/month. Best when you control DNS.
  • Brevo — biggest free quota (300/day), no domain required to start, EU infrastructure.
  • Gmail SMTP — zero-config, 500/day, but slow during incident bursts.

PREFER A WEBHOOK?

Slack and Discord channels are zero-config alternatives

NightOwl ships native Slack and Discord channels. Paste a webhook URL, done — no SMTP, no daily caps, instant delivery.

Email is good as a fallback when chat is down, but it doesn't have to be your primary channel.

Frequently asked questions

Can I use SendGrid's free tier for NightOwl alerts?

Yes. SendGrid (now Twilio SendGrid) gives you 100 emails/day free forever. NightOwl talks plain SMTP to smtp.sendgrid.net:587 with the literal string `apikey` as the username and your `SG.xxx...` API key as the password. Setup takes about 10 minutes including sender verification.

Why are my SendGrid alerts arriving late or in spam?

Two free-tier limitations, both SendGrid — neither is NightOwl. (1) Free-tier sends share IP pools with thousands of other accounts; deliverability to corporate Outlook and Gmail-for-Business has been historically uneven since the Twilio acquisition. (2) The 100/day cap triggers HTTP 401 / 429 responses during bursts; NightOwl retries with backoff, but sustained overrun stalls alert delivery. Typical quiet-period delivery: 5-20 seconds. *This is SendGrid's free tier, not NightOwl* — verify in SendGrid's own Activity Feed, where every send shows with a delivery status. Both clear up on Essentials ($19.95/mo+) with dedicated IP options.

Do I need to verify a sender or domain?

Yes — SendGrid blocks unverified senders. The fastest path: Single Sender Verification under Settings → Sender Authentication. Enter the email address you want NightOwl alerts to come from, click the link in the validation email. The better path: Domain Authentication, which adds CNAME records to your DNS and unlocks branded sending plus better deliverability. Domain auth takes 5 minutes plus DNS propagation.

What's the literal SMTP username for SendGrid?

The username is literally the string `apikey` — not your account email, not your username, just the four letters `apikey`. The actual API key value goes in the password field. This trips up most first-time SendGrid users.

What's the actual delivery speed?

Free tier, verified sender, well-warmed account: typically 5-20 seconds. Comparable to Brevo. Slower than Resend (1-3s) but with stronger brand recognition for compliance/audit conversations. SendGrid has been around longer than most competitors and is sometimes a contractual requirement.

How does the 100/day limit work?

It's a rolling 24-hour window. In practice, NightOwl groups exceptions by fingerprint and only fires `issue.new` once per new fingerprint, so alert volume usually stays well under 100/day during normal incidents. Sustained overrun returns HTTP 401/429 from SendGrid — you'll see the rejected sends in SendGrid's Activity Feed with the corresponding error code.

Why was my API key rejected even though I copied it correctly?

Three common causes: (1) the API key was created with restricted scopes that don't include 'Mail Send' — SendGrid hides this when you create with 'Restricted Access'. Recreate with Full Access or explicitly enable Mail Send. (2) The sender hasn't been verified yet — SendGrid accepts the auth but rejects messages with HTTP 403 referencing 'sender identity'. Verify your sender. (3) The account is paused for review — SendGrid sometimes flags new accounts for manual review; check the account status banner.

PRICING

Flat pricing. No event caps. No per-seat fees.

14-day free trial, no credit card. Your PostgreSQL, your data.

HOBBY

$5 /month

1 app · 14 days lookback · all Laravel events

TEAM

$15 /month

Up to 3 connected apps · unlimited environments · all Laravel events

AGENCY

$69 /month

Unlimited apps · unlimited agent instances · same flat rate at any traffic

Related