Skip to content
Workflow Automation IntegrationHTTP Node & Port 587 SMTP

Enterprise transactional email for n8n automated workflows

Trigger transactional emails from any n8n workflow with zero fragile OAuth tokens. Built-in webhook feedback loops, recipient allowlists, and 6,000 free monthly sends.

3,000 emails/month freeZero credit card requiredSub-20ms edge latency
< 2 mins
Setup Time
Copy-paste HTTP node
Scale plans
Uptime SLA
Per the Terms; not offered on Free, Starter or Pro
6,000 / mo
Free Monthly Sends
Forever free tier
Developer Ergonomics

Drop into your application in under 60 seconds

Native typed interfaces with zero unnecessary dependencies. Built for standard fetch and modern edge runtimes.

$n8n: Import from Clipboard -> HTTP Request
n8n-http-node.json
json
JSON
{
  "nodes": [
    {
      "parameters": {
        "method": "POST",
        "url": "https://api.sadasend.com/emails",
        "authentication": "genericCredentialType",
        "genericAuthType": "httpHeaderAuth",
        "sendHeaders": true,
        "headerParameters": {
          "parameters": [
            { "name": "Authorization", "value": "=Bearer {{ $env.SADASEND_API_KEY }}" }
          ]
        },
        "sendBody": true,
        "specifyBody": "json",
        "jsonBody": "={\n  \"from\": \"notifications@yourdomain.com\",\n  \"to\": \"{{ $json.customerEmail }}\",\n  \"subject\": \"Order Confirmed #{{ $json.orderId }}\",\n  \"html\": \"<p>Hi {{ $json.name }}, your order has shipped!</p>\"\n}"
      },
      "name": "Send SadaSend Email",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 4.2
    }
  ]
}

Copy-pasteable n8n HTTP Request node configuration. Trigger high-deliverability emails from any webhook, database change, or cron schedule.

Core Infrastructure

Engineered for high deliverability and zero incident risk

Every layer from edge connection pooling to per-key rate limits is designed to keep critical transactional dispatches fast, reliable, and contained.

Zero Fragile OAuth Expirations

Eliminates broken automation pipelines caused by expiring Gmail or Microsoft refresh tokens with static scoped API keys.

Native Port 587 ESMTP Relay

Drop smtp.sadasend.com directly into n8n Send Email nodes if you prefer native SMTP over HTTP REST calls.

Bi-Directional Webhooks

Stream delivery, open, click, and bounce events directly back into n8n Webhook nodes to update CRM systems automatically.

Per-Workflow Recipient Allowlists

Restrict automated test runs in staging to company email addresses to guarantee test data never reaches real customers.

Instant Error Handling & Retries

Clear JSON error responses with standard HTTP status codes let n8n error workflows handle rate limits and issues gracefully.

RFC 8058 1-Click Headers

Automatic List-Unsubscribe headers ensure automated notifications comply with 2026 Gmail and Yahoo inbox sender policies.

Architectural Comparison

SadaSend vs Gmail OAuth / Generic Mail Nodes

Why production n8n workflows switch from personal Gmail connections to SadaSend.

Feature & CapabilitySadaSendGmail OAuth / Generic Mail Nodes
Token Expiration VulnerabilityNever expires (Static API key)Expires every 7-90 days
Custom Domain DKIM & SPF AlignmentSent via @gmail.com alias
Staging Recipient Allowlists
Bi-Directional Webhook Event IngestionManual polling required
ESMTP Port 587 Relay Support
Free Tier With Custom Domain6,000 sends foreverPersonal inbox limit only
Forever Free Tier
Transparent Economics

Start with 3,000 emails every month at zero cost

No artificial paywalls on security. Unlike legacy providers that reserve recipient allowlists or dedicated IP pools for high enterprise tiers, every SadaSend account receives full safety controls from day one.

3,000 dispatches monthly forever with zero credit card
All safety gates, allowlists, and velocity limits included
Scale seamlessly: Starter ($12/mo for 10k), Pro ($19/mo for 50k), Scale ($79/mo for 250k)
Free Developer Plan
$0 / mo

No credit card required

Create Free AccountCompare all paid plan tiers
Frequently Asked Questions

Everything you need to know about n8n email

Clear, transparent answers on deliverability, API authentication, and rate limits.

You can either use the n8n HTTP Request node pointing to POST https://api.sadasend.com/emails with your API key header, or configure the n8n Send Email node with host smtp.sadasend.com and port 587.
Technical Deep Dives

Related developer guides and architectural tutorials

Explore step-by-step production implementation blueprints, benchmarks, and protocols.

Documentation

SMTP relay & framework integrations

Connect existing applications, WordPress, Supabase, Laravel, Django, and Nodemailer to SadaSend via standard SMTP relay with zero code changes.

Read guide
Documentation

REST API Reference & Endpoints

Complete REST API reference for sending emails, managing API keys, tracking delivery events, and configuring recipient allowlists with low latency.

Read guide
Documentation

API Error Codes & Troubleshooting

HTTP status codes, machine-readable error reasons, and step-by-step remediation guides for API key rate limits, circuit breakers, and bounce handling.

Read guide
Deep Dive4 min read

How to Send Transactional Email with n8n and SadaSend: The Complete Guide (Zero SMTP Limits)

Automate transactional email in n8n without SMTP timeouts, OAuth expirations, or account bans. Complete HTTP Request node setup, copy-pasteable workflow JSON, and webhook handling with SadaSend.

Read tutorial
Deep Dive4 min read

Building a transactional email queue on Bun and BullMQ without losing messages

The worst bug an email service can have is not a crash. It is accepting a message, returning 202, and never sending it.

Read tutorial
Deep Dive4 min read

Nodemailer in production: what breaks, and what to do about it

Nodemailer is excellent at composing and transmitting a message. Almost every production incident I have seen with it is about the code around it, not the library.

Read tutorial
Deep Dive3 min read

Why your transactional email goes to spam

People assume transactional mail is exempt from filtering because it was requested. Mailbox providers do not know that, and mostly do not care.

Read tutorial
Deep Dive4 min read

SPF, DKIM and DMARC: what each one actually does

Three records, endlessly confused with each other. Here is the mental model that makes them stop being confusing, and the two mistakes that cause most failures.

Read tutorial