Email Send (SMTP)
The Email Send (SMTP) node is a powerful, production-grade action designed for heavy-duty email automation. Unlike generic email nodes, this node is deeply optimized with intelligent Connection Pooling and Zero-Allocation streaming architectures, making it capable of blazing-fast bulk dispatching. It easily connects to any email provider (Amazon SES, SendGrid, Office365, Mailgun, cPanel) to automate everything from single notifications to massive mailing list campaigns with uncompromised memory efficiency.
What can you do with Email Send (SMTP)?
Universal SMTP Compatibility & TLS Security
Seamlessly integrates with practically every email server in existence. Fully supports explicit TLS over Port 465 and automatic STARTTLS negotiation over Port 587 or 25, ensuring enterprise-grade encryption during transit.
Extreme Performance Bulk Sender (Connection Pooling)
Automatically activates an intelligent Connection Pool when bulk sending is detected. Instead of constantly renegotiating expensive TLS handshakes for every email, it parallelizes dispatches across persistent concurrent sockets, multiplying throughput massively without blocking.
Zero-Allocation Attachment Streaming
Send massive documents, PDFs, or image attachments efficiently. Employs state-of-the-art streaming decoders to directly pipe Base64-encoded files over the network socket, preventing debilitating RAM spikes (OOM) commonly seen in inferior platforms.
Detailed Usage & Configuration
The Email Send (SMTP) node operates effectively for both single transactional alerts and extensive marketing loops.
1. Configuration Basics
First, create an SMTP Credential providing your Host, Port, Username, and Password. Be sure to enable "SSL/TLS on connection" if you are targeting Port 465. Next, provide a valid From Email (e.g., "Notifications <alert@domain.com>") and specify your recipients in the To field.
2. Text vs HTML Layouts
By toggling the Is HTML switch, you unlock the ability to construct rich, responsive visual templates. You can pipe in dynamic variables like {{ $json.userName }} straight into the layout to personalize each outgoing blast.
3. Sending Attachments
To attach files such as generated PDF invoices, map the Attachments Property field to the JSON property that holds the Base64 file data (e.g., invoiceData). The node's Smart Fallback even lets you pass a direct local file path (e.g. /tmp/report.pdf) into the property if running self-hosted. The system will automatically detect the file extension and format the correct MIME type before dispatch.