Transactional Emails

Code-defined transactional emails with admin-editable copy, test sends and a send log

Community 9 71/wk MIT v0.1.1

Installation

pnpm add @payload-solutions/plugin-emails

About

Transactional Emails lets developers define each system email in code and lets editors change its wording in the admin. Each email has a key, typed input from the application, a list of variables the copy may use, and default subject and body text. Editors change the subject, body and recipients in a rich text editor, preview with sample data, send themselves a test, and switch non-critical emails off.

Application code sends an email with one typed call, and the result says whether it was sent, skipped, queued or failed. A log keeps a record of every send, test sends included. The branding lives in a shared template in code, so editor changes cannot break the layout.

Package info

Package name
@payload-solutions/plugin-emails
Latest version
0.1.1
Unpacked size
507 kB
License
MIT
Weekly downloads
71
Last publish
Oct 24, 2026

More from mpresecan

View profile

Schedules one-off, recurring and cron-based actions that run on the Payload job queue

Scaffolds a SaaS project on Payload with database, auth, billing and storage chosen up front

Cookie banner, script gating, legal pages and consent records managed in the admin

Newsletters sent through Resend Broadcasts, with Payload collections as subscriber sources

Triggers Vercel deploy hooks after Payload content changes, with status and rollback

React components and hooks for cookie consent, gated scripts and Consent Mode

Similar plugins

More in Email

Adds document and field comments with @mentions to the Payload admin panel

Sends transactional emails when orders are created or change status

Emails the shop once when a product or variant hits its low stock level

Recovers abandoned Payload carts with timed recovery emails and order attribution

Public sponsor list with tiers, private contacts and emailed sponsor updates

In-site notices and email copies with per-person preferences and a retrying queue