Savant lets you deliver workflow results directly through email using the Email and Multi-Email connectors. Both connectors allow you to configure recipients, message content, and attachments so that workflow results reach the right people in a format that is useful to them.
The two connectors are designed for different delivery requirements. Use the Email connector when you need to deliver a single workflow output. Use the Multi-Email connector when you need to combine multiple workflow outputs into a single email or need additional control over recipients and attachments.
The choice between the two connectors depends primarily on how many outputs you need to deliver and how much control you need over the email configuration.
Email connector
Use the Email connector when your workflow produces a single output that you want to deliver through email.
For example, a workflow might generate a daily report and send it to a predefined group of recipients. The workflow output can be included as an attachment, and recipients can be configured either as a fixed list or dynamically from workflow data.
Workflow output ──> Email ──> Recipients
The Email connector is the right choice when a single workflow output is all you need to deliver.
Multi-Email connector
Use the Multi-Email connector when your workflow needs to deliver multiple outputs through a single email.
You can connect multiple workflow outputs to the connector and configure each output independently as an attachment. Multi-Email also provides additional recipient options, such as CC and BCC, giving you greater control over how the email is delivered.
Output 1 ─────────┐
Output 2 ───────────> Multi-Email ──> Recipients
Output 3 ─────────┘
Multi-Email is useful when multiple outputs are related and should be delivered together rather than through separate emails.
How are they different?
The fundamental difference is how much control you need over the outputs being delivered.
| Multi-Email | |
Best for | Sending a single workflow output | Sending multiple workflow outputs in one email |
Recipients | Specific list or dynamic list based on a field | Specific list or dynamic list based on a field |
CC / BCC | — | ✓ |
Attachments | Single workflow output | Multiple workflow outputs |
Attachment configuration | Single output | Configure each output independently |
Dynamic attachment names | ✓ | ✓ |
Empty-output behavior | Depends on the recipient configuration | Depends on the recipient configuration |
Configure the Email connector
Use the Email connector when you want to send a workflow output through email.
Add an Email connector to the workflow.
Connect the workflow output to the Email connector.
Select the Email node to open its configuration.
Under Email To, select how you want to specify the recipients:
Specific list of recipients: Enter the email addresses directly when the same recipients should receive the email every time the workflow runs. For example, A daily invoice workflow always sends its output to: [email protected] and [email protected]
In this case, there is no reason to store recipient information in the workflow data. Configure the addresses directly in the connector.
Dynamic list based on a field: Select Dynamic list based on a field when the recipient needs to come from the workflow data. For example, an input could contain:
Acme Corp: [email protected]
Globex: [email protected]
Instead of configuring a fixed recipient, select the field containing the email address. Savant uses the value from that field when processing the workflow. This is particularly useful for:
Customer-specific notifications.
Record-level notifications.
Workflows where recipient information already exists in the input.
Reusable workflows that should not require recipient addresses to be hard-coded.
Note: The selected field should contain valid email addresses. If the field is empty or contains invalid values, the email may not be delivered as expected.
In Sender Name, enter the name you want recipients to see as the sender.
In Reply To, enter the email address that should receive replies, if different from the sending address.
In Subject, enter the subject of the email.
In Message, enter the content you want to include in the email. Use the message editor to format the email as needed. You can add text formatting, lists, links, and tables.
To include the workflow output as an attachment, enable Include Data as Attachment. This is useful when the workflow produces something that recipients need to download, review, or process separately. For example, an invoice report or a CSV containing processed records.
Under Attachment Type, select the format in which the workflow output should be delivered. For example, a tabular workflow result might be delivered as a text-based file.
The Attachment Name determines the file name the recipient sees:
Enter manually: Enter a fixed file name when the attachment should use the same name for every workflow run. For example: daily_invoices.csv
Dynamic based on a field: Select a workflow column/field when the attachment name should be generated from workflow data. If recipients need to distinguish attachments from different workflow runs without opening them, consider using a dynamic attachment name.
Under What would you like to do when the output is empty?, select how Savant should handle an empty result:
When you select Specific list of recipients under Email To, Savant provides three options for handling an empty output:
Same Message: Choose Same Message when the normal email message should still be sent even if the output is empty. This is useful when the email serves as confirmation that the workflow ran. For example: The daily invoice workflow completed. No invoices were generated.
Different Message: Choose Different Message when an empty result needs its own message. This is useful when an empty result needs to be explicitly communicated to the recipient. For example: No invoices were available for processing today. This avoids sending the same message that would normally accompany a successful output.
No Email: Choose No Email when there is no reason to contact the recipient if the workflow produces no output. This is particularly useful for alert-style workflows.
For example: If exceptions exist → Send email with exception report; If no exceptions exist → Do not send email. This prevents recipients from receiving unnecessary "empty" emails.
When you select Dynamic list based on a field under Email To, Savant provides two options:
Pass Job: Select this when an empty result is an expected and valid outcome. For example, a daily exception report may legitimately contain no exceptions. In that case, an empty result does not mean the workflow failed.
Fail Job: Choose Fail Job when the workflow is expected to produce output and an empty result indicates a problem. For example, if an invoice-processing workflow is expected to generate an output every time, an empty result may indicate that the workflow did not process the expected data.
Under Sort, configure the sort order for the output, if required. Select + to add additional sort conditions.
Review the configuration and select Apply.
Configure the Multi-Email connector
Use Multi-Email when a single email needs to contain multiple workflow outputs or when you need additional control over recipients and attachments.
Add a Multi-Email connector to the workflow.
Connect all workflow outputs that you want to deliver to the Multi-Email connector.
Select the Multi-Email node to open its configuration.
Under Email To, configure the primary recipients:
Enter a fixed list of recipients when the same recipients should receive the email every time.
Enable Dynamic based on field when the recipient should be determined from workflow data.
The addition of CC and BCC makes Multi-Email useful for workflows where an email needs a primary recipient plus additional stakeholder.
In Sender Name, enter the name you want recipients to see as the sender.
In Reply To, enter the address that should receive replies, if required.
In Subject, enter the subject of the email.
In Message, enter the content of the email.
The Attachments section displays the outputs connected to the Multi-Email connector. Each output can be configured independently. For example:
A CSV may contain the processed transaction data.
A PDF may contain a human-readable report.
Another workflow output may contain supporting information.
This allows a single email to contain several different workflow outputs. Multi-Email lets you decide which outputs should be attached and how each attachment should be represented, rather than treating all workflow output as a single attachment.
For each output:
Select the output in the Attachments list.
Enable Include Data as Attachment.
Select the Attachment Type.
Configure the File Name. For each attachment, you can:
Use a fixed name when the attachment represents the same type of report every time.
Use a dynamic name when the attachment needs to reflect information from the workflow. Dynamic names are particularly helpful when a recipient receives these emails regularly and needs to distinguish files without opening each attachment.
Configure sorting, if required.
You can repeat this process for each output that should be included.
Under What would you like to do when the output is empty?, select how Savant should handle an empty result.
When you select Dynamic list based on a field under Email To, Savant provides two options:
Pass Job: Allows the workflow to complete successfully when the dynamic recipient list does not produce a valid recipient.
Fail Job: Causes the workflow to fail when the dynamic recipient list does not produce a valid recipient.
When you select Specific list of recipients under Email To, Savant provides three options for handling an empty output:
Same Message: Sends the configured email message even when the output is empty.
Different Message: Sends a different message when the output is empty.
No Email: Does not send an email when the output is empty.
Click Apply.
Note: If a required configuration is missing, Savant displays a validation error message.
Summary
The distinction between the two connectors is primarily about how much control you need over email delivery.
Email is the simpler option for delivering a workflow output.
Multi-Email is designed for more advanced delivery scenarios where multiple outputs, attachments, or recipient configurations need to be managed together.
One output, simple delivery → Email
Multiple outputs or advanced email delivery → Multi-Email