Black Friday is here 🔥 Get Wensity Pro for 20% less with

Use Wensity email templates.

This guide covers how to add the Wensity email templates, 65 emails in 7 styles built with React Email, to your project, set your brand once, and send them with Resend or any other provider. Each email is a single .tsx file you own: there is no template package to keep updated, and nothing calls Wensity when an email is sent.

Install an email

Log in once with an API token from your dashboard, then add an email by its style and name. Browse them all on Email templates; every page shows the install command for the email you are looking at.

terminal
npx wensity@latest login
npx wensity@latest emails add prism/invoice
npx wensity@latest emails add ledger
npx wensity@latest emails list

A bare style (emails add ledger) adds every email in it. react-email is installed for you with your package manager unless you pass --no-install. --dry-run shows what would be written, and --dir puts the files somewhere else.

Where the files go

Emails land in emails/<style>/, or src/emails/<style>/ when your project has a src folder. Each style folder holds its emails and one kit:

emails/
emails/
prism/
kit.tsx # the token block and the blocks every Prism email shares
invoice.tsx # one email: a default export, typed props, PreviewProps
payment-failed.tsx

Every email takes the data that changes per send as typed props: names, links, codes, amounts, order lines. PreviewProps on each component holds sample values for the preview server, so an email renders on its own before you wire it up.

Set your brand in the kit

The top of each kit.tsx is a token block. Change it once and every email in that style follows.

TokenWhat it sets
brand, taglineThe name in the header and footer, and the line under it in the footer.
ColoursThe style's accent and ink, such as violet in Prism or forest and sage in Grove. The light and dark palettes sit just under the token block.
font, fontCssThe font stack and the stylesheet it loads from. The system fonts after Satoshi are what clients without web fonts show.
appUrl, shopUrl, helpUrlWhere the header, buttons and help links point.
assetsUrlWhere the style's pictures and icons are served from. See Host the images.
address, socialsThe postal address and social links in the footer.

Once you change a kit.tsx, the CLI never replaces it: adding more emails from that style keeps your brand. Pass --force only when you want our version back.

Preview them locally

React Email ships a preview server. Point it at your emails folder to see every template with its PreviewProps, switch between desktop and mobile, and send yourself a test:

terminal
npx react-email dev --dir emails

The kit files have no default export, so the preview server lists only the emails.

Send with Resend

Resend renders React Email components for you, so you can pass the email itself:

app/api/invoice/route.ts
import { Resend } from "resend";
import InvoiceEmail from "@/emails/prism/invoice";
const resend = new Resend(process.env.RESEND_API_KEY);
await resend.emails.send({
from: "Northfield Studio <billing@northfield.studio>",
to: client.email,
subject: `Invoice #${invoice.number}`,
react: (
<InvoiceEmail
sender="Northfield Studio"
client={client.name}
invoiceNumber={invoice.number}
amount={invoice.total}
due={invoice.dueDate}
items={invoice.lines}
payUrl={invoice.payUrl}
/>
),
});

Send with other providers

Every provider takes HTML. render() from react-email turns an email into the HTML and, with plainText, the text part that keeps it out of spam filters:

lib/send-reset.ts
import { render } from "react-email";
import nodemailer from "nodemailer";
import PasswordResetEmail from "@/emails/ledger/password-reset";
const email = <PasswordResetEmail email={user.email} resetUrl={url} requestedAt={when} device={device} location={city} />;
await nodemailer.createTransport(process.env.SMTP_URL).sendMail({
from: "Halden <hello@halden.com>",
to: user.email,
subject: "Reset your password",
html: await render(email),
text: await render(email, { plainText: true }),
});

The same two render() calls work with AWS SES, Postmark, SendGrid, Mailgun and Plunk: pass the HTML and text to their send call.

Dark mode

Every email has a light and a dark palette. The light colours are inline, so every client starts from them. The dark colours sit in one <style> block under prefers-color-scheme: dark, applied by class, and pictures that have a dark version swap with them. Apple Mail, iOS Mail and Outlook for Mac switch on their own.

Gmail and Outlook.com ignore that block and apply their own dark mode, which recolours some text and backgrounds on their terms. That is the client's choice, and no template can fully stop it; the light palette was chosen so those recoloured versions stay readable.

Each email also takes a mode prop ("light" or "dark") that pins one look. It is for previews and screenshots only. Leave it out when you send.

Outlook and Gmail

Outlook for Windows draws email with Word's engine, which supports less CSS than any other client:

  • Corners are square and gradients and shadows are dropped. Buttons keep their solid fill and label, and React Email's Button keeps their padding.
  • Web fonts are not loaded, so text falls back to the system fonts after Satoshi in the font stack (Segoe UI on Windows).
  • Pictures with a separate dark version are hidden from Outlook with mso-hide, so it never shows both.

Gmail clips any email over about 102 KB behind a "View entire message" link. Rendered Wensity emails are well under that, so keep long lists short when you pass your own data. Pictures are PNG and JPG only, because WebP and AVIF still fail in Outlook and some Gmail apps.

Test before you launch

Send each email to the inboxes your users have, light and dark, desktop and phone, before you turn it on. Clients change their rendering without notice.

Host the images

Each kit's assetsUrl points at Wensity's image host so the emails render the moment you install them. Before you send to real customers, upload the pictures you use to your own storage or CDN, keep the same file names, and change assetsUrl to that folder. Then a change on our side can never alter an email in your users' inboxes.

Ask your agent

The Wensity MCP server finds and installs email templates from Claude Code, Cursor, VS Code or Codex. Ask for "a password reset email in the Prism style" and it plans the files, shows you what it will write, and installs the same files as the CLI.

Pro and license

Every email template comes with Wensity Pro (Annual or Lifetime) and uses the token saved by wensity login. Templates are under the Wensity UI Commercial License: use and change them in unlimited projects for yourself and your clients, one developer per license, and never redistribute them as templates.

When a Pro Annual plan ends

Emails already in your projects stay licensed to you and keep sending. Adding new emails and viewing their source stops until you renew.