Actions2
- Email Actions
Overview
This node sends an email using the SMTP protocol with enhanced features such as List-Unsubscribe headers and custom email headers. It supports sending emails in plain text, HTML, or both formats, and allows specifying sender and recipient details, subject, CC, BCC, attachments, reply-to address, and unsubscribe options. It is useful for automating email notifications, newsletters, or transactional emails with advanced header controls.
Use Case Examples
- Sending a monthly newsletter with both HTML and plain text content to multiple recipients.
- Sending a transactional email with attachments and custom headers for tracking.
- Automating unsubscribe options in marketing emails using List-Unsubscribe headers.
Properties
| Name | Meaning |
|---|---|
| From Email | Email address of the sender, can include a name. |
| To Email | Email address of the recipient, can include a name. |
| Subject | Subject line of the email. |
| Email Format | Format of the email content: plain text, HTML, or both. |
| Email (HTML) | HTML version of the email content, shown if format is HTML or both. |
| Email (Text) | Plain text version of the email content, shown if format is text or both. |
| Options | Additional optional settings including CC, BCC, attachments, custom headers, reply-to address, and unsubscribe options. |
Output
JSON
success- Indicates if the email was sent successfully.messageId- The message ID returned by the SMTP server.headers- Custom headers included in the sent email.to- Recipient email address.subject- Subject line of the sent email.error- Error message if sending failed.
Dependencies
- SMTP server credentials (host, port, user, password)
Troubleshooting
- Common issues include incorrect SMTP credentials, invalid email addresses, or missing required fields like 'From Email', 'To Email', or 'Subject'.
- Error messages typically indicate the cause, such as authentication failure or network issues. Verify SMTP settings and email formats.
- Attachments must be correctly referenced by binary property names; otherwise, they will be skipped without failing the entire operation.