Overview
This node sends an email message using the SMTP protocol. It is designed to send emails from a specified sender to one or multiple recipients, supporting plain text, HTML, or both formats in the email body. This node is useful for automating email notifications, alerts, newsletters, or any scenario where programmatic email sending is required.
Practical examples include:
- Sending confirmation emails after form submissions.
- Dispatching automated reports or alerts.
- Sending marketing emails with rich HTML content.
Properties
| Name | Meaning |
|---|---|
| User | The user name value mapped from the configured API credential used for authentication with the SMTP server. |
| From Email | The sender's email address. You can specify just the email or include a display name, e.g., Nathan Doe <nate@n8n.io>. |
| To Email | The recipient's email address. Similar to "From Email", it supports specifying a display name alongside the email. |
| Subject | The subject line of the email message. |
| Email Format | The format of the email content. Options are: Text (plain text), HTML (HTML formatted), or Both (send both plain text and HTML versions). |
| Text | The plain text version of the email body. Required if the format includes Text or Both. |
| HTML | The HTML version of the email body. Required if the format includes HTML or Both. |
| Options | A collection of additional optional settings: |
| - Append n8n Attribution | Whether to append the phrase “This email was sent automatically with n8n” at the end of the email. |
| - Attachments | Names of binary properties containing data to attach to the email. Multiple names can be comma-separated. Useful for attaching files or embedding images referenced in the email body. |
| - CC Email | Email address(es) to send carbon copy (CC) recipients. |
| - BCC Email | Email address(es) to send blind carbon copy (BCC) recipients. |
| - Ignore SSL Issues | Whether to allow connections even if SSL certificate validation fails (useful for self-signed certificates). |
| - Reply To | Email address to use as the reply-to address for responses. |
Output
The node outputs JSON data representing the result of the email sending operation. Typically, this includes status information such as success confirmation or error details. If attachments are included, they are referenced via their binary property names but the node itself does not output binary data.
Dependencies
- Requires an SMTP server configuration accessible via credentials that provide authentication (e.g., username and password).
- Needs proper network access to the SMTP server.
- Optional: If SSL certificate validation is disabled, the node will connect even with invalid or self-signed certificates.
- No other external services are directly required.
Troubleshooting
Common issues:
- Authentication failures due to incorrect user credentials.
- Connection errors if the SMTP server is unreachable or blocked by firewall.
- SSL errors if the server uses a self-signed or invalid certificate and "Ignore SSL Issues" is not enabled.
- Invalid email addresses causing rejection by the SMTP server.
- Missing required fields like "From Email", "To Email", or message body depending on the selected format.
Error messages and resolutions:
- Authentication failed: Verify the username and password/API key in the credentials.
- Connection timed out: Check network connectivity and SMTP server address/port.
- SSL certificate error: Enable "Ignore SSL Issues" only if you trust the server; otherwise, fix the certificate.
- Invalid recipient address: Ensure all email addresses are correctly formatted.
- Missing message body: Provide either plain text or HTML content according to the selected email format.
Links and References
- SMTP Protocol Overview
- Email Format Standards (MIME)
- n8n Documentation on Email Nodes (for general email sending concepts)