Sends Payload emails through the Resend REST API
Email adapters for Payload CMS 18
Send Payload CMS auth and transactional mail over SMTP with Nodemailer, or through the API of Resend, Amazon SES, SendGrid or another provider.
Sends Payload emails through any SMTP server or Nodemailer transport
Sends Payload auth emails and transactional mail through the Groundmail HTTP API
Adds GitHub sign-in to the Payload admin, gated by verified email or org access
Sends Payload emails through the useSend API with templates and scheduled delivery
Sends Payload transactional email through the Lettermint mail API
Sendmail, SMTP and mock mail adapter with an admin panel to test delivery
Sends Payload auth emails and outgoing mail through the SuperSend TX HTTP API
Sends Payload emails through the Brevo transactional email REST API
Sends Payload emails through the eusend EU-hosted transactional email API
Sends Payload email through the Cloudflare Email Service Workers binding
Sends Payload CMS email through the Brevo transactional email API
Sends Payload emails through Cloudflare Email Sending from Workers
Sends Payload CMS email through the Sweego REST API with a default sender
Sends Payload email through Amazon SES using your AWS region and credentials
Sends Payload emails through the AhaSend API, with attachments, headers and reply-to
Routes Payload outgoing email through the SendGrid REST API
Sends Payload emails through Azure Email Communication Services
About these packages
An email adapter decides how Payload sends mail. That covers password resets, email verification and anything you send with payload.sendEmail. You set one adapter in the email option of payload.config, and every message goes through it.
What these adapters cover
- The official Nodemailer adapter for SMTP and any Nodemailer transport
- The official Resend adapter for the Resend REST API
- HTTP API adapters for Amazon SES, SendGrid, Brevo and Azure
- Two Cloudflare Email adapters for sending from Workers
- Groundmail, useSend, Lettermint, AhaSend, Sweego and eusend APIs
- Mail Tester with mock transports and an in-admin deliverability check
Choosing an email adapter
If you already have SMTP credentials, the Nodemailer adapter is the shortest path. API adapters suit serverless platforms and Cloudflare Workers, where outgoing SMTP is often blocked or slow. Pick the provider that has already verified your sending domain, so the SPF and DKIM records exist. During development, the mock transport in Mail Tester keeps test mail away from real inboxes. Some API adapters, such as Lettermint and eusend, target the Payload 4 beta, so match the version on the card before you install. Editable templates and newsletters are among the email plugins.
Frequently asked questions
Does Payload CMS need an email adapter?
Payload starts without one, but logs a warning instead of delivering mail. Configure an adapter before you rely on password resets, email verification or notifications.
What is the difference between SMTP and API email adapters?
The Nodemailer adapter talks SMTP, which almost every mail server accepts. API adapters call the provider's HTTPS API instead. They are usually quicker to set up and work where SMTP ports are closed.
How do I add email templates or newsletters to Payload CMS?
An email adapter only delivers mail. Templates, scheduled sends and newsletters come from email plugins such as Transactional Emails, Mailing and Newsletter.



