Send email with Node.js.

Use the official Parcel Wing SDK to send product and campaign email from Node.js with a clean, production-ready integration.

Start with one send, then grow into verified domains, deliverability tooling, and inbox visibility on the same platform.

View SDK on GitHub Open example repo

Featured snippetNode.js

Start with one send.

Create a client, call `send`, and get back the message record you can log or inspect.

SDK repo

Package

@parcelwing/node

Install

pnpm add @parcelwing/node

Node.js

1import { ParcelWing } from "@parcelwing/node";
2 
3const parcelWing = new ParcelWing({
4  apiKey: "pw_xxxxxxxxx",
5});
6 
7const emails = await parcelWing.emails.send({
8  from: "[email protected]",
9  to: "[email protected]",
10  subject: "Hello World",
11  html: "<strong>it works!</strong>",
12});
13 
14console.log(emails[0]);

Resources

Everything nearby while you integrate.

parcelwing-node

Browse the official SDK source, releases, and package history.

Example repo

Start from a small working app instead of assembling the first send by hand.

Quickstart docs

Wire up your API key, domain, and first message with the shortest path to green.

API reference

Keep the object model, method signatures, and send options close while you build.

Why this SDK

A Node.js SDK built for real product email.

Simple first send

Get from install to live email quickly without building around a throwaway demo integration.

Useful responses

The send API is shaped for app work: readable payloads in, useful message records out.

Production-friendly path

Use the same platform for password resets, invites, receipts, alerts, and lifecycle messaging.

Deliverability built in

Layer in domains, routing, and deeper delivery visibility when the stakes rise.

Workflow

Move from install to live sends fast.

Step 1

Install the SDK

Add `@parcelwing/node`, create a client, and keep configuration close to the rest of your app.

Step 2

Send your first email

Ship the smallest useful message first, then use the returned record in logs and workflows.

Step 3

Scale on the same integration

Add domain setup, routing, and delivery tooling later without rewriting your send path.