n8n Send Email Node: SMTP & Gmail Setup Guide (2026)

The n8n Send Email node (n8n-nodes-base.emailsend) is a built-in n8n workflow automation node that sends email through any SMTP server. You configure it by adding SMTP credentials (host, port, username, password), then setting the From, To, Subject, and Body fields. It works with Gmail, Outlook, SendGrid, custom domains, and any SMTP-compatible provider.

This guide covers everything from initial SMTP credential setup to advanced features like Send and Wait approval workflows, binary attachments, and fixes for the three most common errors that trip up n8n users.

The Send Email node works the same way in n8n 1.x and 2.x, so every setup step and error fix below applies to both versions.

Written by Ryan Nichols, Founder and CTO at Rain Automation. I build and maintain n8n workflows in production for SMBs across Georgia and nationally, and I've configured the Send Email node across dozens of client deployments.

Quick Reference: Send Email Node Parameters

Every Send Email node configuration starts with an SMTP credential and four required fields: From Email, To Email, Subject, and Email Format. The tables below cover every parameter the node exposes, pulled from the current n8n Send Email node documentation.

Credential

Field	Required	Notes
SMTP account	Yes	Host, port, user, password, secure flag. Gmail requires a 16-character App Password, not your account password.

Main parameters

Field	Type	Required	Notes
Operation	Options	Yes	Send or Send and Wait for Response. The latter pauses workflow execution until the recipient submits a response.
From Email	Email	Yes	Supports the Name <[email protected]> format.
To Email	Email	Yes	Comma-separated list for multiple recipients. Supports Name + email format. Same format applies to CC and BCC.
Subject	String	Yes	Plain text. Use n8n expressions for dynamic subjects.
Email Format	Options	No	Text, HTML, or Both. Available only when Operation is Send.

Options (additional fields)

Field	Type	Notes
Append n8n Attribution	Boolean	Appends "This email was sent automatically with n8n" to the message. Turn off for production.
Attachments	String	Comma-separated binary property names. Reference embedded images with <img src="cid:image_1">.
CC Email	Email	Same Name + email format as To Email.
BCC Email	Email	Same Name + email format as To Email.
Reply To	Email	Routes replies to a different address than From.
Ignore SSL Issues	Boolean	Skip TLS/SSL certificate validation. Avoid in production unless you control the SMTP server.

Send and Wait for Response: response types

• Approval: Recipient clicks an Approve or Decline button inside the email. Configurable button labels and style.
• Free Text: Recipient submits a single-field form response.
• Custom Form: Build a multi-field form with the n8n Form trigger's elements.

All three response types support Limit Wait Time (interval or wall time) and Append n8n Attribution.

Known limitation

The Send Email (SMTP) node does not set In-Reply-To or References headers, so each email is treated as a new conversation rather than continuing a thread. Use the Gmail node's Reply to a message operation when threading matters.

We recommend n8n for most small business automation. Affiliate link: we earn a small commission at no cost to you.

n8n Send Email Node vs Gmail Node vs Outlook Node

The n8n Send Email node uses SMTP and works with any email provider (Gmail, Outlook, custom domains, SendGrid). The Gmail node uses Google's API (Gmail/Workspace only) and the Microsoft Outlook node uses Microsoft Graph API (Outlook/M365 only); both require provider-specific OAuth2 setup. Use Send Email for provider flexibility and approval workflows; use Gmail or Outlook for provider-specific features like threading, labels, and inbox triggers.

This is the single most common question new n8n users ask about email. All three nodes can send email, but they work in fundamentally different ways. One uses SMTP. The other two use provider-specific REST APIs. Choosing the wrong one leads to hours of frustrating troubleshooting, so let's clear this up. If you want a focused answer on the Send Email vs Gmail decision specifically, n8n Send Email vs Gmail Node: Which to Use for Your Workflow breaks it down step by step.

The table below compares the three n8n email nodes across protocol, authentication, provider compatibility, and key features.

Feature	Send Email Node (SMTP)	Gmail Node (API)	Microsoft Outlook Node (Graph API)
Protocol	SMTP (port 465 or 587)	Gmail REST API (OAuth2)	Microsoft Graph API (OAuth2)
Authentication	Email + password (or app password)	Google OAuth2 consent flow	Microsoft OAuth2 consent flow
Works with	Any email provider (Gmail, Outlook, Yahoo, custom domains, transactional services)	Gmail and Google Workspace only	Outlook.com and Microsoft 365 only
Threading	No (each email is standalone)	Yes (can reply within existing threads)	Yes (can reply within conversation threads)
Labels / Categories	No	Yes (read, apply, remove labels)	Yes (categories, flags, importance)
Read inbox	No	Yes (trigger on new emails, search, read)	Yes (trigger on new emails, search, read)
Send and Wait	Yes (approval workflows)	No	No
Attachments	Binary data via upstream node	Native file attachment	Native file attachment
Calendar access	No	No (use Google Calendar node)	Yes (events, meetings via same OAuth2)
Basic Auth deprecation	N/A (uses provider credentials)	N/A (OAuth2 only)	Basic Auth disabled by default Dec 2026, removed H2 2027; migrate to OAuth2
Best for	Custom domains, non-Google/non-Microsoft providers, approval workflows, multi-provider setups	Gmail-specific features (threading, labeling, inbox triggers)	Outlook/M365-specific features (threading, categories, calendar integration)
Rate limits	Depends on your SMTP provider	500 emails/day (free Gmail via Gmail API), 2,000/day (Workspace)	10,000 API requests/10 min (general throttle); Exchange Online caps email sending at ~30 messages/minute

The Provider-First Selection Framework

When clients ask us which n8n email node to use, we walk three gates in order. The first gate that returns "yes" decides the node.

Gate 1: Do you need to read or trigger off the inbox?
If the workflow needs to pick up new emails, search a thread, apply a label, or fire on category changes, you need API access. SMTP is one-way (send only), so the Send Email node is out at this gate. Use the Gmail node (Workspace) or the Microsoft Outlook node (M365).

Gate 2: Are you locked into one provider ecosystem?
If every recipient and every sender lives inside the same Workspace or M365 tenant, the provider-specific node gives you threading, signatures, and inbox semantics for free. Use Gmail or Outlook. If your senders or recipients span multiple providers (custom domain via Mailgun, agency clients on different stacks, transactional services), keep going.

Gate 3: Do you need approval workflows or per-send From-address control?
Only the Send Email node has Send and Wait for Response (human-in-the-loop approvals). And if you need to swap the From address per execution (one workflow, multiple sender personas), Send Email handles it natively while Gmail and Outlook require a credential per identity.

Default rule: if no gate matches, use the Send Email node. It is the most portable choice, the easiest to swap providers on, and the only node that survives a change in your email stack. Gmail and Outlook are bets on a specific provider; Send Email is a bet on the protocol.

The quick rule (TL;DR of the framework): Use the Send Email node when you need provider flexibility, multi-provider support, per-send From control, or Send and Wait approval workflows. Use the Gmail node when you need Gmail-specific features like threading, labels, or inbox triggers. Use the Microsoft Outlook node when you are in a Microsoft 365 environment and want OAuth2 authentication with access to calendar and mail categories.

I've configured all three for dozens of client automation workflows, and here's what I've found: most small business owners are better off starting with the Send Email node. It works with whatever email provider you already have. You're not locked into Google's or Microsoft's ecosystem, and if you ever switch providers, you just update one credential instead of rebuilding your entire workflow.

If you're building workflows that combine email sending with CRM integrations, the Send Email node's provider flexibility becomes especially valuable. And for teams already invested in n8n for other automations (like connecting your CRM to multiple tools), the Send Email node slots right into existing workflows without adding another OAuth dependency.

If you're evaluating n8n against other automation platforms, our n8n vs Make comparison breaks down how each platform handles email nodes, pricing, and self-hosting.

If you're still deciding between the Send Email node and the Gmail node, see a detailed breakdown of how the two nodes differ across authentication, threading, rate limits, and use case fit.

---

Need this running in your business? We build and maintain n8n workflows for SMBs. Get in touch.

---

Step 1: Create Your SMTP Credential in n8n

Before the Send Email node can do anything, you need an SMTP credential in n8n that stores your provider's host, port, username, and password. The exact settings differ by provider, but the process in n8n is the same: Credentials > New Credential > Send Email (SMTP).

The process varies depending on your email provider, so I'll walk through the three most common setups.

Gmail SMTP with App Password

Gmail doesn't allow regular password authentication for SMTP. You must use a Google App Password, which requires 2-Factor Authentication to be enabled on your Google account. Here's the exact sequence:

1. Go to myaccount.google.com and sign in
2. Open Security and confirm 2-Step Verification is enabled (if not, set it up first)
3. Visit the App Passwords page and generate a new app password
4. Select Mail as the app and Other as the device (name it "n8n")
5. Copy the 16-character password Google generates
6. In n8n, go to Credentials > New Credential > Send Email (SMTP)
7. Enter these settings:
   • User: your full Gmail address ([email protected])
   • Password: the 16-character app password (not your regular Google password)
   • Host: smtp.gmail.com
   • Port: 465
   • SSL/TLS: Enabled

A common mistake (and the source of most "connection closed unexpectedly" errors) is entering your regular Gmail password instead of the app password. In my experience helping clients set up Gmail SMTP in n8n, using the regular Google password instead of an App Password is the single most common configuration error. The n8n Gmail SMTP documentation covers the correct setup process. If you would rather connect via Gmail's OAuth2 API instead of SMTP, the full credential setup walkthrough includes the Google Cloud Console steps and the fix for the 7-day token expiry that catches most self-hosted users.

Outlook and Microsoft 365: Use OAuth2, Not SMTP

Microsoft is phasing out Basic Auth SMTP for Exchange Online. Basic Auth SMTP will be disabled by default at the end of December 2026 (admins can temporarily re-enable it), with full removal planned for H2 2027 per Microsoft's updated timeline. New Outlook/M365 workflows in n8n should use the Microsoft Outlook OAuth2 node instead of SMTP.

Existing SMTP workflows still work today, but the clock is ticking. I'd recommend migrating to the Microsoft Outlook node with OAuth2 authentication now rather than scrambling in December. The migration is straightforward, and you avoid the risk of your automations breaking when Microsoft flips the default.

Legacy: Basic Auth SMTP Setup (On-Premises / Private Exchange Servers Only)

The instructions below apply only to organizations running private or on-premises Exchange servers that still support Basic Auth SMTP. These steps do not apply to Exchange Online (Microsoft 365 cloud) tenants, where Microsoft is retiring Basic Auth SMTP (disabled by default end of December 2026, full removal H2 2027).

For on-premises Exchange servers where your administrator has confirmed Basic Auth SMTP is still supported, the n8n credential settings are:

• User: your Outlook/Exchange email address
• Password: your account password (or app password if MFA is enabled)
• Host: your organization's Exchange SMTP hostname (e.g., mail.yourdomain.com)
• Port: 587
• SSL/TLS: Disabled (Exchange uses STARTTLS on port 587, not implicit SSL)
• Disable STARTTLS: No (leave STARTTLS enabled)

If you see error 535 5.7.139 on an on-premises server, your admin has not enabled Authenticated SMTP for the mailbox. According to Microsoft's SMTP Auth documentation, this policy can be configured per-mailbox by an Exchange administrator.

Custom SMTP Provider Setup

For transactional email services (SendGrid, Resend, Mailgun, Postmark) or self-hosted mail servers, the credential fields are the same. You just need the SMTP details from your provider:

• User: typically an API key or the full email address
• Password: API key or SMTP password
• Host: your provider's SMTP hostname (e.g., smtp.sendgrid.net, smtp.resend.com)
• Port: 465 (SSL/TLS) or 587 (STARTTLS)
• SSL/TLS: Match your port choice

If you plan to use Mailgun specifically, and your goal is firing CRM lead notifications the moment a form submits, see how to wire the Mailgun node into an n8n lead notification workflow for the exact credential fields and trigger setup.

If you are comparing Gmail relay, Mailgun, SendGrid, and Postmark as providers for a production n8n deployment, see a full provider comparison for production n8n email setups that covers authentication methods, rate limits, and cost at each tier.

Port 465 vs Port 587: Which to Use

This confuses almost everyone. Here's the difference, drawn from the n8n credentials documentation:

• Port 465 uses implicit SSL/TLS. The connection is encrypted from the start. Set SSL/TLS to enabled in n8n.
• Port 587 uses STARTTLS. The connection starts unencrypted, then upgrades. Set SSL/TLS to disabled and keep Disable STARTTLS set to No.

When in doubt, try port 465 with SSL/TLS first. It's simpler and works with most providers.

Step 2: Configure the n8n Send Email Node

Once your SMTP credential is saved, add the Send Email node to any workflow canvas, select your credential, and fill in the From, To, Subject, and Body fields. The node supports both plain text and HTML email formats, plus optional CC, BCC, and Reply-To fields.

Here's a breakdown of every field and what to put in each one.

Required Fields

• From Email: The sender address. Must match (or be authorized by) your SMTP credential. Some providers reject emails if the From address doesn't match the authenticated user.
• To Email: The recipient. For multiple recipients, separate addresses with commas: [email protected], [email protected]. You can also use expressions to pull addresses dynamically from previous nodes in your workflow.
• Subject: The email subject line. Supports n8n expressions, so you can inject data from earlier nodes (e.g., New lead: {{ $json.name }}).

Email Body and Format

The node supports two formats:

• Text: Plain text email. Simple, reliable, works everywhere.
• HTML: Full HTML email with formatting, images, and links. Use this for branded notifications, reports, or customer-facing emails.

You can write HTML directly in the node or use an upstream Code node to build templates dynamically. For complex templates, I typically build the HTML in a Function node and pass it through as an expression.

Optional Fields

• CC: Carbon copy recipients (comma-separated)
• BCC: Blind carbon copy recipients
• Reply-To: Where replies should go (useful when sending from a no-reply address)
• Append n8n Attribution: Toggle off if you don't want "Sent with n8n" appended to your emails. For professional/client-facing emails, you'll want this off.

If you're automating email responses with AI, the HTML format combined with expression-based subject lines gives you full control over personalization.

Step 3: Add Attachments to the n8n Send Email Node

Attachments in n8n work through the binary data system, not file paths. Use an upstream node (Read/Write Files, HTTP Request, or Code node) to create binary data, then reference the binary property name in the Send Email node's Attachments field.

This trips up many users because it's different from how most email clients handle attachments.

Here's how it works:

1. Use an upstream node to create binary data. The most common options:

   • Read/Write Files from Disk node: reads a file from the server's filesystem
   • HTTP Request node: downloads a file from a URL
   • Spreadsheet File node: generates a CSV or Excel file from JSON data
   • Code node: creates binary data programmatically

2. The binary data flows through the workflow as a binary property (default name: data)

3. In the Send Email node's Attachments field, enter the binary property name (usually data)

A frequent mistake: users try to put a file path or URL in the Attachments field. That won't work. The field expects the name of a binary property that exists on the incoming item from the previous node.

For example, if you want to attach a PDF report to a weekly automated report email:

1. Use a Code node or HTTP Request to generate/fetch the PDF
2. The file becomes a binary property called data on the output item
3. In the Send Email node, set Attachments to data

To attach multiple files, you'll need multiple binary properties with different names (e.g., report, invoice), and list them comma-separated in the Attachments field.

Real-World Use Case: Quarterly Referral-Partner Outreach with the Send Email Node

At Rain Automation we run this exact pattern for our AgentOS clients. For Spenser Thomas, a Canton, GA real estate agent serving Cherokee County, we built an n8n workflow that pulls referral-partner contacts (probate attorneys, divorce attorneys, real-estate-adjacent professionals) from his agent-os database and sends a quarterly market-update email through the Send Email node. Across 1,138 outreach and referral sends to 1,076 unique recipients between March and May 2026, the workflow has held a 43.6% open rate among delivered emails, the right benchmark for relationship-driven B2B outreach in real estate.

This is a pattern we've also adapted for small business CRM setups, and it applies to most CRMs n8n supports.

The scenario: A real estate agent wants to stay top-of-mind with referral partners through scheduled, personalized market updates, without ever logging into an email tool to do it.

The three-node workflow:

1. Schedule Trigger (cron): fires the first Monday of each quarter at 7:00 AM ET
2. Postgres node (read): pulls referral-partner contacts tagged for the quarter from marketing_leads, joined to marketing_lists for segment selection. Outputs one item per recipient
3. Send Email node: sends via SMTP using Spenser's mail.spenserthomas.com relay credential, personalizing subject and HTML body with {{ $json.firstName }} plus a market-stats block computed upstream from the previous month's MLS data

Here is what the Send Email node configuration looks like for this workflow:

• From Email: [email protected] (rotates per segment: outreach@ for cold partners, partners@ for active sphere)
• To Email: {{ $json.email }}
• Subject: {{ $json.firstName }}, here's the {{ $json.market }} market in 60 seconds
• HTML Body:

<p>Hi {{ $json.firstName }},</p>
<p>Quick {{ $json.market }} numbers for {{ $json.month }}:</p>
<ul>
  <li>Median sale price: {{ $json.medianPrice }}</li>
  <li>Days on market: {{ $json.dom }}</li>
  <li>Active inventory: {{ $json.activeInventory }} homes</li>
</ul>
<p>If a {{ $json.market }} buyer or seller comes across your desk this quarter, I'd be glad to be your first call.</p>

The Send Email node is the right choice here because Spenser sends across multiple list segments per quarter (probate, divorce, sphere of influence), and each segment uses a different From address (spenser@, outreach@, partners@). Switching the From per execution is trivial with Send Email's From Email field; doing the same with the Gmail node would require multiple pre-authorized OAuth credentials and a credential-switching step in the workflow.

This is the same pattern described in our complete CRM and n8n integration guide. You can extend it with conditional logic (different stat blocks per ZIP code), delays (a one-week follow-up to non-openers), or lead scoring tied to engagement.

If your outreach pattern is "scheduled cron > database query > personalized email" at low enough volume to stay under your SMTP provider's rate limit, Send Email is the simpler choice over the Gmail or Outlook nodes. No OAuth, no provider lock-in, and you can swap SMTP relays without touching the workflow logic. If you're already using n8n for CRM integrations, adding a Send Email node to your existing workflows takes about five minutes.

Advanced: Send and Wait for Response (Approval Workflows)

The Send and Wait operation pauses a workflow until the email recipient responds with an approval, rejection, free text, or form submission. This turns the Send Email node into a human-in-the-loop checkpoint for production workflows.

Zero tutorial blog posts in the current search results cover this feature properly, so let's fix that.

What Send and Wait Does

Instead of firing an email and moving on, Send and Wait pauses the workflow execution until the recipient responds. This creates human-in-the-loop workflows where a person must approve, reject, or provide input before the automation continues.

According to the n8n Send Email node documentation, there are three response types:

Response Type: Approval

The email includes Approve and Reject buttons. Clicking either one resumes the workflow with the response value, so you can branch accordingly. Use this for:

• Manager approves a quote before it's sent to the client
• Finance approves a refund before it's processed
• Team lead approves a new hire's onboarding sequence

Response Type: Free Text

The email includes a text input field. The recipient types a response, and that text is passed back into the workflow. Use this for:

• Requesting additional context before processing a support ticket
• Collecting manager notes on a proposed action
• Gathering feedback before finalizing a report

Response Type: Custom Form

The email links to a form with fields you define (dropdowns, text areas, checkboxes). The form responses feed back into the workflow. This is the most flexible option for structured input.

Setting a Time Limit

You can set a Limit Wait Time to prevent workflows from hanging indefinitely. After the timeout, the workflow continues down a "no response" path. This is critical for production workflows because a forgotten approval email shouldn't block your automation forever.

The Gmail Button Stripping Gotcha

Here's something you won't find in the official docs: Gmail's email client sometimes strips the approval button links, making them unclickable. This is a known issue reported on the n8n community forum.

Workarounds:

• Send approval emails through a transactional provider (Postmark, Brevo, Resend) instead of Gmail SMTP
• Test with non-Gmail recipients (Outlook, Apple Mail work fine)
• Use the Free Text or Custom Form response type instead of Approve/Reject buttons

If you've been exploring automated approval workflows, Send and Wait turns the Send Email node into a genuine human-in-the-loop checkpoint.

What Is n8n-nodes-base.sendemail?

n8n-nodes-base.sendemail is the official package identifier for n8n's built-in Send Email node, confirmed in the n8n documentation and source code. You may also see it referenced as n8n-nodes-base.emailSend or n8n-nodes-base.emailsend in community posts and search results; these are common search variants, but the authoritative identifier in n8n source code and documentation is n8n-nodes-base.sendemail. If this string appears in an error log, a workflow JSON export, or the n8n node panel, it points to the SMTP-based email sending node covered in this tutorial. It is not a separate tool or plugin. It is the system name n8n assigns under the hood to the "Send Email" node you drag onto the workflow canvas. Recognizing this identifier is useful when debugging failed executions, because n8n error messages reference the package name (n8n-nodes-base.sendemail) rather than the display name you see in the UI.

Troubleshooting the n8n Send Email Node

The three most common n8n Send Email errors are ETIMEDOUT (blocked SMTP ports), 535 5.7.139 or 550 5.7.30 (Office 365 SMTP Auth disabled or Basic Auth retired), and "Connection closed unexpectedly" (wrong Gmail password or port/SSL mismatch). Each has a specific, fixable root cause.

First-party benchmark from our send logs (Rain Automation, March to May 2026): Across 12 outreach campaigns we route through this Send Email pattern for AgentOS tenants (1,974 sends to 1,287 unique recipients), we see a 43.6% open rate among delivered emails. That is the realistic benchmark for SMTP-based B2B outreach when deliverability is configured correctly (SPF, DKIM, DMARC properly aligned). If your Send Email setup is consistently under 20%, the issue is almost always one of: a non-aligned From domain, a missing DKIM signature, or an SMTP relay that strips authentication headers. The single most common terminal failure we see in our logs is the relay rejecting a malformed recipient address ("to parameter is not a valid address"); validating the to field with a regex check in a Code node before the Send Email node fires catches it before it costs you a send credit.

After helping dozens of users debug their email workflows (and running into every one of these myself), here are the errors you're most likely to encounter. If your workflow stopped sending and none of these match, a complete walkthrough of what breaks the Send Email node and how to fix it covers five failure patterns in detail.

Error: ETIMEDOUT (Connection Timed Out)

What happens: The Send Email node hangs for 30-60 seconds and then fails with ETIMEDOUT or Connection timed out.

Root cause: Your hosting provider blocks outbound SMTP ports (25, 465, 587) to prevent spam. This is extremely common on cloud platforms including DigitalOcean, AWS EC2, Hetzner, and Oracle Cloud.

Solutions:

1. Contact your host and request outbound SMTP port unblocking. Some providers (DigitalOcean) allow this after account verification.
2. Use a transactional email relay that works over HTTPS instead of SMTP (e.g., Resend with the HTTP Request node, or SendGrid's Web API).
3. Use port 587 with STARTTLS if only port 25 and 465 are blocked (sometimes 587 is allowed).
4. Check with telnet from your server: telnet smtp.gmail.com 465. If it hangs, the port is blocked.

Error: 535 5.7.139 or 550 5.7.30 Authentication Failure (Office 365)

What happens: n8n connects to smtp.office365.com but authentication fails with error code 535 5.7.139 or 550 5.7.30.

Root cause: Microsoft is retiring Basic Auth SMTP for Exchange Online. Basic Auth will be disabled by default at the end of December 2026, with full removal in H2 2027. If you're seeing 550 5.7.30 Basic authentication is not supported for Client Submission, your tenant may have already disabled Basic Auth. The older 535 5.7.139 error indicates SMTP Auth was disabled by policy for a specific mailbox. Both errors point to the same resolution: migrate to OAuth2.

Solution:

Migrate to the Microsoft Outlook OAuth2 node in n8n. Even if Basic Auth still works on your tenant today, it will stop working by H2 2027. This is a frequently reported issue in the n8n community, and the only resolution is OAuth2. If you're running an on-premises Exchange server (not Exchange Online), an Exchange administrator may still be able to enable Authenticated SMTP per-mailbox per Microsoft's SMTP Auth documentation.

Error: Connection Closed Unexpectedly (Gmail)

What happens: n8n reports Connection closed unexpectedly or Socket closed when trying to send through Gmail.

Root cause: Almost always one of two things:

1. You're using your regular Gmail password instead of a Google App Password
2. You're using port 587 with SSL/TLS enabled (wrong combination)

Solution:

1. Generate a Google App Password and use that in your credential
2. Use port 465 with SSL/TLS enabled, OR port 587 with SSL/TLS disabled (STARTTLS)
3. Verify 2-Step Verification is active on your Google account

Email Deliverability Tips

Even after your emails send successfully, they might land in spam. A few things that help:

• Set up SPF, DKIM, and DMARC records for your sending domain. Without these, receiving servers have no way to verify your emails are legitimate.
• Don't bulk send through a personal Gmail or Outlook account. These providers have strict daily sending limits (Reddit users report issues after just 10 emails/day). Use a transactional provider for volume.
• Match your From address to the domain in your SPF record. Mismatches are the top cause of spam classification.
• Include an unsubscribe link in marketing emails. It's legally required in most jurisdictions and improves deliverability.

If you're building email marketing automation for your small business, getting deliverability right from the start saves you from rebuilding sender reputation later.

For cases where n8n reports a successful send but the email never appears in the inbox or spam folder, the issue is usually a DNS authentication gap. Rain Automation's delivery fix guide walks through all six root causes in order, from SPF failures to relay-level silencing.

Working n8n Email Examples by Industry

The Send Email node is the same across every business. What changes is the workflow around it. Three service businesses that run this node in production. The Send Email node is identical across all of them. The workflow logic around it is not.

Cleaning Company: Automatic Estimate Follow-Up

A cleaning business we work with was losing estimates to slow follow-up. A potential customer would fill out the website form, and someone on the team would get around to emailing them back whenever they noticed. Sometimes that was 4 hours later. Sometimes it was the next day. Sometimes it didn't happen at all.

The n8n workflow we built triggers a Send Email node the moment a new estimate request lands. Within 4 minutes, the customer gets a personalized confirmation with the estimate turnaround time and a direct line to the office. If they don't reply within 48 hours, a follow-up email goes out automatically.

The result: response time dropped from "whenever someone remembers" to under 5 minutes. The owner stopped losing estimates to competitors who simply replied faster.

We built and maintain this workflow. If that is the follow-up gap your business has, reach out at rainautomation.com/contact.

Real Estate Team: Listing Alert Emails to Matched Buyers

A real estate team we work with needed listing alerts that actually matched what each buyer was looking for. Before automation, agents would scan new listings manually and forward them to buyers when they had time. Buyers were finding properties on Zillow before their own agent sent anything.

The n8n workflow pulls from their MLS feed on a schedule, matches each new listing against saved buyer preferences (price range, location, bedrooms, property type), and fires a Send Email node with a formatted property summary. Buyers get alerts within an hour of a listing hitting the market. No manual work from the agent.

The team stopped losing buyer engagement to Zillow's speed. Agents spend their time on showings and negotiations instead of copying listing links into emails.

The workflow runs in production. Contact us at rainautomation.com/contact if your team is still doing this manually.

Window Installation Contractor: Contract Delivery Confirmation

A window installation company we work with was spending 20 to 30 minutes per job on a task that should take zero: sending customers an email confirming their signed contract was received and their job was scheduled.

The n8n workflow monitors their document system. When a signed agreement arrives, a Send Email node fires automatically. The customer gets a confirmation with their job details and next steps. The office team doesn't touch it.

Over 15 to 20 jobs per month, that's 6 to 10 hours of admin work that just disappeared. More importantly, customers stopped calling to ask "did you get my contract?" because the confirmation arrived before they thought to ask.

Spending 20+ minutes per job on contract confirmations? We built the fix. rainautomation.com/contact.

Frequently Asked Questions

These are the most common questions about the n8n Send Email node, each answered so you can jump directly to what you need. If you're troubleshooting a specific error, the Troubleshooting section above has step-by-step fixes.

How Do I Fix "Please Contact Your Admin. n8n Is Not Set Up to Send Email Right Now"?

This error appears when n8n's instance-level SMTP configuration is missing. It is separate from the Send Email node's per-workflow credentials. To fix it, add SMTP environment variables to your n8n Docker Compose file or .env: N8N_EMAIL_MODE=smtp, N8N_SMTP_HOST=smtp.gmail.com (or your provider), N8N_SMTP_PORT=465, [email protected], N8N_SMTP_PASS=your-app-password, and N8N_SMTP_SSL=true. After saving, run docker compose down && docker compose up -d to rebuild the container. A simple container restart may not apply the changes; running docker compose down && docker compose up -d is the most reliable method to ensure n8n reads the updated environment variables. This configuration controls n8n's system emails (password resets, user invitations), not the Send Email node in your workflows.

How Do I Send Email to Multiple Recipients in n8n?

In the Send Email node's To Email field, list addresses separated by commas: [email protected], [email protected], [email protected]. The same comma-separated format works for CC and BCC fields. You can also use n8n expressions to build the recipient list dynamically from upstream data, for example {{ $json.recipients.join(', ') }} when pulling from a database or spreadsheet node. Each address receives its own copy of the email. There is no built-in limit on the number of comma-separated recipients, but your SMTP provider's per-message limit applies (Gmail caps at 100 recipients per message). Check your provider's documentation for their specific per-message recipient cap.

What Is the n8n Send Email Node?

The n8n Send Email node is a built-in workflow automation node that sends email through any SMTP server. You configure it with four credential fields (host, port, username, password) and four message fields (From, To, Subject, Body). It works with Gmail, Outlook, SendGrid, Mailgun, custom domains, and any other SMTP-compatible provider. Unlike the Gmail node or Microsoft Outlook node, the Send Email node is provider-agnostic and does not require OAuth2 setup. It also supports a Send and Wait operation for human-in-the-loop approval workflows, which the provider-specific nodes do not offer.

How Do I Send an Email Using n8n?

Add the Send Email node to your workflow, create an SMTP credential with your provider's settings (host, port, username, password), and configure the To, From, Subject, and Body fields. The node sends through your existing SMTP server and works with Gmail, Outlook, or any custom domain.

n8n Send Email Node vs Gmail Node: When Should You Use Each?

Use the Send Email node for provider flexibility, non-Google providers, per-send From control, or Send and Wait approvals. Use the Gmail node when you need Gmail API features like threading, labels, or inbox triggers. Send Email uses SMTP (any provider); Gmail uses the REST API (Google OAuth2 only).

How Do I Set Up SMTP Credentials in n8n?

Go to Credentials, create a "Send Email (SMTP)" credential, and enter your provider's SMTP host, port, username, and password. For Gmail: host smtp.gmail.com, port 465, SSL/TLS enabled, 16-character App Password. For Outlook/M365, skip SMTP and use the Microsoft Outlook OAuth2 node instead.

How Do I Send HTML Email via n8n?

Set the Email Format field to "HTML" (or "Both" for a plain-text fallback). Write HTML directly in the body field or inject it via expressions like {{ $json.htmlContent }} from an upstream Code node. The node renders standard HTML including tables, lists, images, and inline CSS.

How Do I Send Attachments with the n8n Send Email Node?

Use an upstream node (Read/Write Files, HTTP Request, or Code node) to load the file as binary data. Put the binary property name (default: data) in the Attachments field. You cannot use file paths or URLs directly. For multiple files, use separate property names listed comma-separated.

Why Is My n8n SMTP Node Timing Out?

SMTP timeouts (ETIMEDOUT) usually mean your hosting provider blocks outbound ports 465 and 587 to prevent spam. Test with telnet smtp.gmail.com 465 from your server. If it hangs, contact your host to unblock SMTP ports, or switch to a transactional relay service like SendGrid or Resend that uses HTTPS APIs instead.

Can n8n Automate Emails?

Yes. n8n can fully automate email sending, reading, and processing. Use standard triggers (webhooks, schedules, CRM events) to fire workflows that send personalized emails through the Send Email node. Common automations include welcome emails, follow-up sequences, report delivery, and approval workflows.

Can the n8n Send Email Node Thread Replies?

No. The Send Email (SMTP) node does not set In-Reply-To or References headers, so each email starts a new conversation. If you need to reply within an existing thread, use the Gmail node's "Reply to a message" operation or the Microsoft Outlook node's reply operation.

Next Steps

You now have everything you need to configure the n8n Send Email node, from basic SMTP credentials to advanced approval workflows. The node's provider flexibility makes it a solid foundation for almost any email automation.

If you're building email into a larger automation stack, our n8n CRM integration tutorial covers how to connect your email workflows to HubSpot, Pipedrive, and other CRMs. And for a broader comparison of automation platforms, check out our n8n vs Make breakdown.

If the email addresses and lead details your workflow needs live in a database, our n8n PostgreSQL integration guide covers connecting n8n to Postgres, plus the upsert and empty-result handling that keeps scheduled sends from going out twice or not at all.

If you're connecting n8n email workflows to a broader CRM stack, our n8n CRM integration hub covers the full picture: HubSpot, Pipedrive, Salesforce, and custom CRM setups.

If you want to go beyond individual nodes and build workflows that make decisions on their own, see our complete guide to AI agents for business automation.

For workflows that go beyond what off-the-shelf tools can handle, our custom development services page covers what a purpose-built automation platform looks like, and when it makes sense to invest in one.

If you're running a real estate business, Agent OS includes built-in automation and CRM tools purpose-built for agents, with no custom workflow configuration required.

Ready to try n8n? Sign up for a free account and build your first email workflow. n8n's free tier includes enough executions to test everything covered in this guide.

Related Reads

More on n8n and business automation:

• n8n vs Make for Small Business Automation — A side-by-side comparison for service businesses choosing between the two most popular self-hosted automation platforms.
• n8n Send Email Node Not Working: Common Errors and Fixes — If your Send Email node is failing silently, throwing SMTP errors, or emails aren't arriving, start here.
• AI Agents for Business Automation: The Complete Guide — What AI agents actually do inside a business, where they work, and where they don't.
• n8n PostgreSQL Integration: Connecting Your Database to Automated Workflows: Connect n8n to Postgres, choose between the Postgres and Postgres Trigger nodes, and stop duplicate rows on repeat runs.

This guide is for informational purposes. Email deliverability, provider policies, and n8n features may change. Always check the official n8n documentation for the latest specifications.