Ligantic
Knowledge Base
Tutorials
Updates
Search Articles
Login
Free Sign Up
Home
Get Started
Tutorials
How-to guides
Reference
Explanation
Spaces
Schemas
Flows
Experiences
Endpoints
SDK and CLI
Browse documentation
Home
Get Started
Spaces
Schemas
Flows
Experiences
Endpoints
SDK and CLI
Docs
/

Integration - SMTP

Type identifier: integration:smtp Category: 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

trigger

control

Starts the send operation.

host

string

(Dynamic) SMTP server hostname.

port

number

(Dynamic) SMTP server port.

secure

boolean

(Dynamic) Use TLS/SSL connection.

user

string

(Dynamic) SMTP authentication username.

password

secret

(Dynamic) SMTP authentication password.

from

string or email object

(Dynamic) Sender email address.

to

email array

(Dynamic) Recipient email addresses.

cc

email array

(Dynamic) CC recipients.

bcc

email array

(Dynamic) BCC recipients.

replyTo

email

(Dynamic) Reply-to address.

inReplyTo

string

(Dynamic) Message-ID being replied to.

subject

string

(Dynamic) Email subject line.

body.value

content or string

(Dynamic) Email body content.

attachments

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

success

control

SMTP accepted the message.

error

error control

Sending or preparation failed; v2 exposes the error codes below.

messageId

string

The generated Message-ID.

accepted

email array

Recipients accepted by the SMTP server.

rejected

email array

Recipients rejected by the SMTP server.

pending

email array or null

Recipients pending delivery, when reported by the server.

response

string or null

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

string or dynamic

"smtp.example.com"

SMTP server hostname.

Port

number or dynamic

465

SMTP server port (typically 465 for SSL, 587 for TLS).

Secure

boolean or dynamic

true

Use secure TLS/SSL connection.

User

string or dynamic

-

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

string or dynamic

Message-ID for reply threading (optional).

Subject

string or dynamic

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

  1. Validates all required fields are provided
  2. Resolves dynamic values for server settings and email fields
  3. Connects to SMTP server with configured credentials
  4. Constructs email message with:

    • Sender and recipient addresses
    • Subject and body content
    • Attachments (if any)
    • Threading headers (if replying)
  5. Sends the email via SMTP
  6. Logs success or failure

V2 errors

Connect error to a Control - Switch node in Error mode to branch on these codes:

Code

Meaning

invalid_input

A configured input is invalid, an attachment exceeds the limit, or the password is not a wrapped secret.

file_access_failed

An attachment could not be read or rich-content file URLs could not be prepared.

smtp_failed

The server could not be reached, authentication or sending failed, or the password secret was unavailable.

smtp_timeout

Sending timed out. Delivery is uncertain, and SMTP credits are charged.

billing_failed

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

Related pages

Object - Query
Queries the Records of a Schema that match a filter, with pagination and ordering. Returns the matching Records with their metadata, or, with a select/groupBy shape, rows of chosen fields, aggregates over relationships, and grouped counts and totals. Use this node to retrieve data for processing, display, or downstream operations.
Page not found. It may have moved or may not be published.
Browse documentation