Overview

Use the Email node to send emails to specified addresses;

Properties Tab

Basic Settings

All fields can be either literal values or expressions encapsulated within ${} syntax, for example ${in.MyValue}.

Field	Description	Example Value
Name	Name given to the Email Node. This will be displayed on the actionflow canvas.	MyEmailer
From	The email address the email will be sent from. This should match the email address specified as the login email in your Outbound Emailer, see: Repository → Full Repository → Email Accounts → Outbound Emailer → Login. Login shows the email being used to send emails from PhixFlow.	notifications@phixflow.com
To	The email address(es) the email will be sent to. Multiple addresses must be comma separated, if an expression evaluates to a list of email addresses then this will be converted automatically to the correct format.	sale@phixflow.com
CC	The CC email addresses. Provided as a comma-separated list if multiple values are required. If an expression evaluates to a list then this will be converted automatically to the correct format. This is an optional field.	info@phixflow.com, marketing@phixflow.com
BCC	The BCC email addresses. Provided as a comma-separated list if multiple values are required. If an expression evaluates to a list then this will be converted automatically to the correct format. This is an optional field.	info@phixflow.com, marketing@phixflow.com
Reply To (PhixFlow version 11.3+)	Specify an email address that reply emails will be go to. After emails are sent, if the email is then replied to the email will be sent to the value this field evaluates to. This allows emails to be sent from one email address but have users replies sent to another specified email address.	responses@phixflow.com
Subject	The email's subject. This accepts JEP expressions in the format ${Connector.AttributeName}	// Send the message followed by a timestamp MyEmailer has run successsfully_ + ${now()}
Message	The content of the email. This can accept text direct as an input as well as JEP expressions.	// Sends the content of the attribute MyMessage from // the in pipe ${in.MyMessage}
is HTML	defines whether to treat the email as HTML or plain text. The default setting is plain text, indicated by the toggle being switched off. This accepts JEP expressions in the format ${Connector.AttributeName} Treat the Message as HTML. Treat the Message as plain text.

Attachments

Available in PhixFlow version 11.3+.

Field

Description

File Table

Select an existing File Table or create a new one.

Once a file table has been selected, a filter field displays where a filter can be set to find all applicable files from that file table and include them as attachments on the sent email.

Advanced

Field	Description
Prioritise Throughput Over Ordering	When enabled, records are processed in parallel to optimise performance. This means the order records are processed is nondeterministic. When disabled (default), records are processed in the order they are provided.

Verifying Emails

It is possible to check an email has successfully been sent using the Email tab at the top of the system console. System Console → Email Tab. See System Console

Built-in Error Handling

Basic validation is performed to ensure that email addresses are well-formed. If they are not this will cause the actionflow to fail immediately. At least one address must be resolved from amongst the to, cc and bcc.

Other errors, such as email addresses for accounts that don’t exist, won’t cause a failure of the actionflow but they will result in the email sending not succeeding.

Learn More

Email Node