Outputs & Actions
Email Output Nodes Reference
Technical reference for `emailOutput`, `gmailSend`, and `outlookSend`, including attachment handling and auto-zip behavior.
Updated 2 min read
Overview
These nodes send workflow outputs by email:
emailOutput: generic workflow email routegmailSend: send through a connected Gmail accountoutlookSend: send through a connected Outlook account
Configuration / Settings
| Setting | Type | Required | Details |
|---|---|---|---|
to | email/string template | Yes | Supports variable expressions. |
subject | string template | No | Defaults to Workflow Output. |
body | string template | No | Plain message body. |
fileName | string template | No | Base attachment name. |
connectionId | string | Required for Gmail/Outlook | OAuth-backed senders need an account connection. |
Inputs Expected
- All covered nodes expect file blobs as attachments.
- Nested loop arrays are flattened before attachments are built.
Variables Exported / Outputs
Output shape: original Blob[]
Important metadata:
emailSentmessageIdattachmentCountwasZippedproviderfor Gmail or Outlook nodes
Common Use Cases
- Email a final PDF package to a customer after templating.
- Send a ZIP archive when a workflow generated many files.
- Route the same processed file to both download and Gmail branches.
Edge Cases
emailOutputauto-zips when there are more than 10 attachments.- Gmail and Outlook nodes zip any multi-file attachment set by default.
- If there are no files, the node throws instead of sending a body-only message.