Integration - SMTP
Type identifier:
integration:smtpCategory: Integration Operations
Description
The Integration - SMTP node sends emails through an SMTP server. It supports various email formats including plain text, HTML, and rich content with automatic text fallback. The node can handle attachments and supports common email features like CC, BCC, and reply threading.
Input Handles
Handle | Type | Description |
|---|---|---|
| control | Starts the send operation. |
|
| (Dynamic) SMTP server hostname. |
|
| (Dynamic) SMTP server port. |
|
| (Dynamic) Use TLS/SSL connection. |
|
| (Dynamic) SMTP authentication username. |
| secret | (Dynamic) SMTP authentication password. |
|
| (Dynamic) Sender email address. |
| email array | (Dynamic) Recipient email addresses. |
| email array | (Dynamic) CC recipients. |
| email array | (Dynamic) BCC recipients. |
| (Dynamic) Reply-to address. | |
|
| (Dynamic) Message-ID being replied to. |
|
| (Dynamic) Email subject line. |
| content or | (Dynamic) Email body content. |
| array | (Dynamic) File attachments. |
Note: Dynamic input handles appear based on configuration.
The password input always accepts a wrapped secret, such as the value output of Secret - Get. Do not unwrap the password into plain text. With v2 execution, connect trigger, password, and every configured dynamic input. Reading a data output alone does not send an email.
Output Handles
Handle | Type | Description |
|---|---|---|
| control | SMTP accepted the message. |
| error control | Sending or preparation failed; v2 exposes the error codes below. |
|
| The generated Message-ID. |
| email array | Recipients accepted by the SMTP server. |
| email array | Recipients rejected by the SMTP server. |
| email array or null | Recipients pending delivery, when reported by the server. |
|
| The SMTP server response, when available. |
Recipient results can contain address strings or named email objects. V2 publishes data outputs only after confirmed SMTP success; unavailable optional results are null. SMTP acceptance does not guarantee delivery to the recipient's inbox.
The authentication password is never included in these outputs. A wrapped password alone does not make SMTP metadata sensitive; sensitivity from other email inputs is preserved. If the server echoes the password into its result, the node follows error without publishing that result, even though the accepted send remains charged.
Configuration Options
Server Settings
Option | Type | Default | Description |
|---|---|---|---|
Host |
|
| SMTP server hostname. |
Port |
|
| SMTP server port (typically 465 for SSL, 587 for TLS). |
Secure |
|
| Use secure TLS/SSL connection. |
User |
| - | SMTP authentication username. |
Password | dynamic (secret) | - | SMTP authentication password. |
Email Settings
Option | Type | Description |
|---|---|---|
From | email or dynamic | Sender address (string or {name, address} object). |
To | email array or dynamic | Primary recipients. |
CC | email array or dynamic | Carbon copy recipients (optional). |
BCC | email array or dynamic | Blind carbon copy recipients (optional). |
Reply-To | email or dynamic | Reply-to address (optional). |
In-Reply-To |
| Message-ID for reply threading (optional). |
Subject |
| Email subject line. |
Body Content
The body can be one of three types:
Type | Description |
|---|---|
content | Rich content that auto-generates both HTML and plain text. |
text | Plain text only. |
html | HTML with automatic plain text fallback. |
Attachments
Files can be attached via the dynamic attachments input. Each file may contain at most 25 MiB (26,214,400 bytes).
V2 accepts stored files from the current Space, including files belonging to the current flow execution. Files from another Space or another flow execution are rejected. Raw, unsaved file payloads are not supported by this node in v2.
Behaviour
- Validates all required fields are provided
- Resolves dynamic values for server settings and email fields
- Connects to SMTP server with configured credentials
Constructs email message with:
- Sender and recipient addresses
- Subject and body content
- Attachments (if any)
- Threading headers (if replying)
- Sends the email via SMTP
- Logs success or failure
V2 errors
Connect error to a Control - Switch node in Error mode to branch on these codes:
Code | Meaning |
|---|---|
| A configured input is invalid, an attachment exceeds the limit, or the password is not a wrapped secret. |
| An attachment could not be read or rich-content file URLs could not be prepared. |
| The server could not be reached, authentication or sending failed, or the password secret was unavailable. |
| Sending timed out. Delivery is uncertain, and SMTP credits are charged. |
| SMTP credits could not be reserved, charged, or released. |
Execution and billing
V2 reserves SMTP credits before sending and charges after SMTP accepts the message. An explicit send failure releases the reservation without an SMTP charge.
A send timeout is treated as sent for billing, but follows error with smtp_timeout, not success. No SMTP data outputs are published for a timeout. The send timeout is 15 seconds.
The node does not automatically retry. Retrying after a timeout may send a duplicate email. If charging fails after acceptance or timeout, billing_failed does not mean the message was unsent; do not assume it is safe to resend.
Legacy v1 execution retains its existing charge-before-send behavior. These SMTP charges are separate from other flow execution charges.
Email Address Format
Email addresses can be specified as:
- Simple string:
"user@example.com" - Object with name:
{ name: "John Doe", address: "john@example.com" }
Content Types
When using content body type:
- Rich content is converted to both HTML and plain text
Examples
Send Simple Notification
Configuration:
- Host: smtp.example.com
- Port: 465
- Secure: true
- From: notifications@example.com
- To: (dynamic from trigger)
- Subject: "Your order has shipped"
- Body (text): Order details
Send HTML Email
Configuration:
- Body (html): HTML template with styling
- Attachments: Invoice PDF
Send with Content
Configuration:
Body (content): Rich text content from editor
- Automatically generates HTML and text versions
- Handles embedded images