SMTP Advanced

Send emails via SMTP with reply-to, forward and custom headers

Actions3

Reply To Email

AI-generated

Summary

Reply to an existing email with proper threading by specifying original message identifiers and sending formatted email content.

Inputs

  • fromEmail (required) — Email address of the sender.
  • toEmail (required) — Email address(es) of the recipient(s). Separate multiple addresses with commas.
  • subject (required) — Subject line of the reply email.
  • messageId (required) — Message-ID of the original email being replied to, used to maintain threading.
  • references — References header from the original email to include for threading context.
  • emailFormat — Format of the email body; options are text, HTML, or both. Defaults to text.
  • text — Plain text content of the reply; required if using text or both formats.
  • html — HTML content of the reply; required if using HTML or both formats.
  • options.replyTo — Email address to use for the Reply-To header.
  • options.cc — Carbon copy recipient(s); separate multiple addresses with commas.
  • options.bcc — Blind carbon copy recipient(s); separate multiple addresses with commas.
  • options.customHeaders — Custom email headers as name-value pairs to add to the outgoing email.
  • options.attachments — Comma-separated names of binary properties containing files to attach to the email.

Output shape

a list of JSON objects, each indicating success status, message ID of the sent reply, operation type, recipient email, and subject line, paired with the input item index.

Handles multiple input items; throws errors unless configured to continue on failure. Returns success and error details per item.

Examples

Example 1: Replying to an email with text content and maintaining proper email threading.

Set fromEmail, toEmail, subject, messageId, and optionally references. Provide plain text content in 'text'. Optionally add cc, bcc, replyTo, and attachments.

Links

Discussion