The Email connector lets a workflow send its output by email. Connect one output to send a single attachment, or connect several outputs to combine them into one email — each one configured independently. Recipients can be a fixed list, or built dynamically from a field in the data.
Combining multiple outputs into one email
The Email connector can do more than send a single attachment. Connect more than one workflow output to the same Email connector, and each connected output appears as its own entry under Attachments - configured independently, with its own attachment type, file name, and sort order.
This is useful whenever related results should reach a recipient together, rather than as several separate emails. For example, a month-end close workflow might produce a summary report, a detailed backup file, and a list of exceptions - all from the same run. Instead of three separate emails, connect all three outputs to one Email connector and deliver them together as a single message with three attachments.
Each attachment keeps its own settings, so the outputs don’t need to match each other:
One can be a PDF summary, another an Excel file, another a text file - each uses whichever Attachment Type fits it.
Each can have its own File Name, fixed or generated dynamically from the data.
An Excel attachment can have its own Tab Name, and can be formatted against an uploaded template independently of any other attachment in the same email.
Each attachment can be sorted independently under Sort.
Because a single email can now carry more than one result, CC and BCC are useful here too — add stakeholders who only need to see part of the combined output, without making them a primary recipient.
Why you need the Email connector
A workflow’s output often needs to reach someone who doesn’t use Savant — a manager, a vendor, or another team. The Email connector delivers that output by email, so the result doesn’t depend on someone logging into Savant, exporting a file, and sending it manually after every run.
When to use it
A report needs to go to the same group of people every time the workflow runs.
A workflow should only send an email when there’s an exception or an issue to flag, and stay quiet otherwise.
Each record in the output needs to go to a different recipient — for example, a separate email per vendor or customer, based on a field in the data.
Several related outputs need to reach the same recipient together, as one email — see “Combining multiple outputs into one email” above.
The result needs to reach someone outside Savant who only needs the output, not access to the workflow itself.
Why it’s useful
Recipients don’t need a Savant account — only an email address.
The workflow handles delivery, so no one has to manually export and send the result after each run.
Recipients can be a fixed list or generated from the data, so the same workflow can notify one person or many without changing its setup.
The empty-output options mean an email only goes out when there’s something to report, if that’s how the workflow should behave.
Attachments can be delivered as Excel, PDF, or a text file, including an Excel file formatted against a template.
Configure the Email connector
Add the Email connector. Add an Email connector to the workflow.
Connect the outputs. Connect one or more workflow outputs to the Email connector. Connect a single output to send one attachment, or connect multiple outputs to combine them into one email.
Open the configuration. Select the Email node.
Set the recipients. Under Email To, choose:
Specific list of recipients — enter the email addresses directly, when the same people should receive the email every time the workflow runs. For example, a daily invoice workflow that always goes to [email protected] and [email protected].
Dynamic based on field — select a field from the workflow data instead, so each record’s recipient comes from that field. The field must contain valid email addresses, or delivery may not work as expected.
Add CC and BCC, if needed. Add any additional recipients who should receive a copy — particularly useful when combining multiple outputs into one email for different stakeholders.
Set the sender details. Enter a Sender Name and, if replies should go to a different address, a Reply To address.
Write the email. Enter the Subject and the Message. The message editor supports text formatting, lists, links, and tables.
Configure each attachment. Every output connected to the Email connector is listed separately under Attachments — if you connected more than one, each gets its own entry to configure independently:
Enable Include Data as Attachment.
Set the Attachment Type — Text File, Excel, or PDF.
Set the File Name — a fixed name, or Dynamic based on field to generate it from the workflow data.
For Excel, set the Tab Name — fixed or dynamic.
For Excel or PDF, enable Format file from template to upload an .xlsx template (up to 25MB) the output should follow.
Set Sort, if the attachment’s data needs a specific order.
Set the empty-output behavior. Under What would you like to do when the output is empty?, choose how Savant should handle a run where the connected output has no data:
With a specific recipient list:
Same Message — sends the same email and message every time, even when there’s no data. Use this when the email itself confirms the workflow ran, regardless of the result.
Different Message — sends a separate message when the output is empty, so the recipient gets an explicit note instead of the usual content.
No Email — skips sending an email entirely when the output is empty. Use this for alert-style workflows where an empty result just means there’s nothing to report.
With a dynamic recipient field:
Pass Job — lets the workflow complete normally when a record produces no output or no valid recipient. Use this when an empty result for a given record is expected, not an error.
Fail Job — stops the workflow and marks it failed when a record produces no output or no valid recipient. Use this when the workflow should always produce output, so an empty result signals a problem.
Apply. Review the configuration and select Apply.
Troubleshooting
1. No email was sent.
If Email To is set to Dynamic based on field, check that the field contains a valid email address for every record. An empty or invalid value, combined with Fail Job, stops the workflow instead of sending an email.
If the output was empty, check the empty-output setting — No Email and Fail Job are both expected to skip sending, so confirm that’s what you intended for this workflow.
Check the recipient’s spam or junk folder before assuming delivery failed.
2. The email was sent, but an expected attachment is missing.
Confirm Include Data as Attachment is enabled for that output under Attachments.
If the output was empty and the empty-output setting is Same Message or Different Message, the email still goes out, but without data to attach.
3. One attachment in a multi-output email is missing or misconfigured, but the others are fine.
Each attachment is configured independently — check that specific output’s entry under Attachments rather than assuming a shared setting is at fault.
4. The attachment opened in the wrong format, or wasn’t formatted as expected.
Check that Attachment Type matches what the recipient expects — Text File, Excel, or PDF.
For a formatted Excel or PDF output, confirm Format file from template is enabled and that the uploaded .xlsx template is still valid.
5. The same recipient received duplicate or unexpected emails.
With Dynamic based on field, confirm the selected field doesn’t repeat the same address across multiple records — each matching record generates its own email.
6. Savant shows a validation error and won’t apply the configuration.
A required field is missing. Review Email To, Subject, and each enabled attachment’s required fields (Attachment Type, File Name, and Tab Name for Excel) before applying again.
Summary
The Email connector sends a workflow’s output by email- as a single attachment, or as multiple outputs combined into one message, each configured independently. Recipients can be a fixed list or one built from the data, and the connector can be set to send only when there’s actually something to report. Use it whenever a workflow’s result needs to reach someone by email.