Send Mail — Reference

Compose an email and submit it through a configured server mailer.

Before you begin

• A Server Connect action and a dedicated test mail transport or capture service. Do not use production recipients for initial verification.

Send Mail

Compose an email and submit it through a configured server mailer.

Settings

Setting	Meaning
Mailer	The reusable Mailer definition that supplies SMTP/server transport settings.
Subject	The subject string. It is required; bind a deliberate value rather than a full untrusted message object.
Importance	The message priority hint: low, normal or high. It does not guarantee delivery order or inbox placement.
Attachment(s)	Server file paths or file records to attach. These are not the browser’s local file paths. Verify that the recipient is authorized to receive them.
Headers	Additional outgoing message headers. Keep their names/values controlled and avoid conflicting with the standard addressing or content headers.
Name (Sender)	The displayed sender name; the inspector labels it Name within the Sender group. It is not the action’s result name.
Email (Sender)	The From email address. Use an address allowed by the chosen mail service.
Reply To	The address to receive replies. For a contact form, a validated submitter address can be used here while From remains a service-authorized sender.
Recipient(s)	Simple exposes the primary recipient; Extended also reveals Cc and Bcc. This changes available controls, not an access policy.
To Name	Optional display name of the main recipient.
To Email	The main recipient address. Validate any recipient value derived from input.
Cc	Additional visible copy recipients.
Bcc	Additional blind-copy recipients. Do not expose this list through another output field.
Mail Body	Static uses Content; File reads a server-side template file. This selects the body source, not a database attachment.
File	The application-relative server template file used for a File body. Its expressions are evaluated in server scope. Node.js currently retains the earlier static value for the plain-text body variable, so verify File + Text carefully; File + HTML uses the loaded HTML body.
Content	The literal/template content for a Static body. Keep the format consistent with the selected Text or HTML mode.
Format	Text or HTML. HTML email support differs among recipients, so inspect a test rendering and any plain-text fallback.
Embed Images	For Node.js HTML, attempts to embed matching local JPG/PNG/GIF server paths as CID attachments. External URLs are not valid local filesystem paths for that embedding branch. The PHP HTML path delegates to PHPMailer and does not apply this switch equivalently.
Output	Includes the transport result when enabled. Node.js returns transport metadata; PHP normally returns send success or throws. Neither is proof that a recipient read the message or that it reached an inbox.

Verification example

Use a dedicated mail-capture/test transport with a known sender, one test recipient, a static text body and no attachments first. Inspect the subject, addresses and body. Then test an HTML body, a permitted test attachment and an intentional transport failure separately. No production recipient is needed to verify composition.

Transport and message limits

A successful transport submission is not guaranteed end-to-end delivery. Prefer explicit absolute production URLs in HTML templates instead of relying on rewriting from the incoming request host. Handle failures and retries deliberately so repeating a form request does not unintentionally send duplicate messages.

Place mail in the application flow

Validate and authorize the triggering operation, compose the intended message, and report the actual success/error state to the page. File upload, record creation and email delivery are separate operations.

Check your result

You can configure the transport or message fields and verify composition and failure handling with a test transport.