Nightlamp uses AgentDraft for email-flow healthchecks.
Nightlamp monitors the paths that fail quietly: magic-link login, OTP login, signup confirmation, incident alert delivery, and round-trip email delivery. AgentDraft supplies the mailbox Nightlamp can poll during those checks, so the monitor can prove the email actually arrived instead of only proving an HTTP endpoint responded.
Disclosure: Nightlamp is a first-party product. This is a production use-case writeup, not an independent customer endorsement.
Updated
A normal uptime check can tell you whether a page returns 200. It cannot tell you whether a signup confirmation email arrived, whether a magic link was captured, whether SPF/DKIM/DMARC passed, or whether an incident alert reached the channel humans rely on.
Nightlamp's AgentDraft integration closes that gap. One org-scoped AgentDraft mailbox can back the workspace: incident alerts can be delivered there, and email-flow monitors can wait for real messages in the same mailbox before marking the journey healthy.
The public Nightlamp docs describe AgentDraft as an org-scoped integration. The key is stored encrypted, masked after connection, and then used by monitors that need mailbox evidence:
Nightlamp email_flow monitor │ ├─▶ trigger app action → send magic link, OTP, alert, or test email │ ├─▶ poll AgentDraft mailbox → find messages after this monitor run started │ ├─▶ assert delivery facts → subject/body, SPF, DKIM, DMARC, link host │ └─▶ optionally follow link → verify magic-link response without storing secrets
The mailbox is not marketing decoration. It is the stateful part of the healthcheck: without an inbox, the monitor can only infer that an email might have been sent. With AgentDraft, it can assert that the message appeared and inspect the delivery facts Nightlamp cares about.
This is a different kind of customer story from calendar scheduling. The shared resource is an inbox, not a meeting slot. The same product principle still applies: give an autonomous system a typed operational surface, then make the evidence queryable.
- One mailbox can back a workspace. Nightlamp's docs describe one AgentDraft connection per workspace for alert delivery and email-flow QA.
- The monitor checks real email outcomes. Magic-link, OTP, signup confirmation, incident alert, and round-trip delivery flows can all use mailbox evidence.
- Sensitive values stay out of stored history. Nightlamp stores derived facts and redacted previews rather than raw bearer links, OTPs, or cookies.
“Nightlamp uses AgentDraft as an org-scoped mailbox integration: alert delivery when incidents open, and a QA inbox when monitors need to prove real email arrived.”
- Nightlamp's AgentDraft email-flow guide — the public integration docs behind this writeup.
- Email-flow monitoring for agents — how AgentDraft mailboxes support QA workflows.
- AgentDraft docs — mailbox, API key, and webhook surfaces for builders.