✉️
Use the Email node when a workflow needs to send messages or read mailbox content.
Common uses include:
- Sending notifications after a job finishes.
- Reading alert emails from an inbox.
- Delivering reports to a team.
- Checking a mailbox for new messages to drive workflow logic.
What the Email Node Does
The Email node supports two actions:
| Action | Meaning |
|---|---|
email:sendEmail | Send an outgoing message using the selected email connection |
email:getEmail | Read messages from a mailbox and return matching results |
Send Email
Use Send Email when the workflow should notify people.
Required fields
| Field | What it means | Example |
|---|---|---|
| Sender | Which saved outgoing email connection sends the message | Finance SMTP connection |
| To | Main recipients | ops-team@example.com |
| Subject | Email title | Daily report is ready |
| Body | Message content | The daily report completed successfully. |
Optional fields
| Field | What it means | Example |
|---|---|---|
| CC | Copied recipients | manager@example.com |
| BCC | Hidden recipients | audit@example.com |
| Attachment | One storage path or a list of storage paths to attach. Each path is expression-resolved and downloaded from artifact storage, then attached to the message | {{$('exportReport').artifact.storagePath}} |
| Priority | Delivery importance | Normal, high, low |
| Read receipt | Ask for a read confirmation when supported | Yes |
| Delivery receipt | Ask for a delivery confirmation when supported | Yes |
The attachment field accepts either a single storage-path string or a list of them. Each is resolved, downloaded via the artifact client, and added to the outgoing message as attachment metadata.
Example
You want to send a daily report email.
| Field | Value |
|---|---|
| Sender | Finance SMTP connection |
| To | finance-team@example.com |
| CC | finance-manager@example.com |
| Subject | Daily finance report is ready |
| Body | Hello team, the daily finance report has been generated. Please review it in the shared folder. |
What happens:
- The node resolves the saved sender connection.
- Automation Hub prepares the email content.
- It sends the message through the configured SMTP service.
- The step result shows success or failure.
Get Email
Use Get Email when the workflow should read mailbox content.
Required fields
| Field | What it means | Example |
|---|---|---|
| Mailbox connection | Saved incoming mailbox connection to read messages from | Monitoring mailbox |
| Folder | Mail folder to search | Inbox |
| Output | How much data to return | Complete email details |
Optional fields
| Field | What it means | Example |
|---|---|---|
| Return all | Return the default set of messages | Yes |
| Limit | Max messages to read when not returning all | 10 |
| Filter type | How the filter is interpreted: filterQuery (structured filter) or searchQuery (mailbox search string) | filterQuery |
| Filter | Rules to select emails, interpreted per filterType | Unread alerts from alerts@example.com |
| Fields | Selected fields for custom output | Subject, From, Received Time |
| Download attachments | optionDetails.attachmentDownload — when true, each message's attachments are uploaded to artifact storage and referenced in the output | Yes |
| Attachments prefix | Storage path prefix used when uploading downloaded attachments (attachmentsPrefix) | emails/alerts/ |
The limit, folder, fields, and filter values are expression-resolved before the mailbox is queried.
Example
You want to read unread alert emails.
| Field | Value |
|---|---|
| Mailbox connection | Monitoring mailbox |
| Folder | Inbox |
| Filter | Only unread emails from alerts@example.com |
| Limit | 25 |
| Output | Subject, sender, received time |
What happens:
- The node opens the saved mailbox connection.
- It checks the selected folder and applies the filter.
- It returns matching email details for later steps.
Output
Get Email returns a JSON list, one entry per matching message:
| Field | What it holds |
|---|---|
content | The message as JSON (headers, sender, subject, body, and the requested fields) |
binary | Artifact metadata for the message's downloaded attachments. Present only when Download attachments is enabled |
When attachment download is off, each entry contains just content; when it is on, entries also include binary pointing to the uploaded attachment(s) in artifact storage.
Runtime behavior
The Email node always resolves the saved email or mailbox connection from Global Configurator before it performs the action.
- Send Email uses the configured SMTP or default sender connection.
- Get Email uses the configured mailbox connection for reading messages.
Common problems
| Problem | What to check |
|---|---|
| Email did not send | Recipients, subject, sender connection, SMTP host/port |
| Authentication failed | Connection credentials, tenant, client ID, client secret |
| No emails returned | Folder name, filters, unread-only setting, mailbox permissions |
| HTML looks wrong | Message body content and email client HTML support |
| Step fails before sending | Required fields may be missing |
Best practices
- Use clear subject lines so recipients understand the email purpose.
- Keep recipients intentional: only use CC and BCC when needed.
- Save connection details in Global Configurator instead of embedding passwords in the node.
- Store repeated values in global variables to make workflows easier to update.
- Test automated emails with a small audience before sending broadly.
- Make failure emails descriptive: include job name, failed step, and next actions.