Sobmit Docs

Email node

Email node card

The Email node sends a transactional email to one or more recipients. The message body is derived automatically from the incoming payload — a generated table becomes a formatted HTML table, a generated HTML page is sent as-is, and anything else becomes plain text — so an email often needs no body configuration at all.

Handles

HandlePurpose
PayloadThe body source (a table, report, string, …)
AttachmentsMedia to attach (generated audio/images, PDFs, …)
ResultA { to, subject, recipients } summary after sending

Configuration

  • Recipients — one or more email addresses (bare addresses, comma-separated lists and "Name <email>" are accepted).
  • Subject — the subject line. Supports {…} templates.
  • Body mode — how the body is derived:
    • auto — prefer the payload’s natural HTML form (a table or HTML page), otherwise plain text.
    • text — always plain text.
    • html — always HTML.
  • Custom HTML / Text — optional overrides for the body (win over the auto-derivation). Supports {…} templates.
  • Attach payload files — when on, also attach any media travelling on the payload line (not only what is wired into Attachments).

Attachments

Media wired into the Attachments handle is always attached. With Attach payload files enabled, media on the payload line is added too — so a text body and a generated audio or image can feed the same node without one overwriting the other. PDFs, images, video, audio and 3D models are all supported.

Example — email a generated report

A Deep Research node produces a cited report. An Email node sends it:

recipients: ops@example.com
subject: "Weekly competitive brief"
body mode: auto          (the report becomes the text body)

A Table Generation node upstream would instead arrive as a formatted HTML table in the email.

Notes

  • Sending is billed at a flat fee per recipient as an anti-spam protection fee — there is no per-token model cost.
  • The card shows the recipient count and, when wired, a paperclip badge for attachments.
  • Delivery is through Resend; a missing sender or invalid key fails the node with a clear message.

Related