Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Overview

Use the  Send Email action 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}.

FieldDescriptionExample Value
NameName given to the Email Action Node. This will be displayed on the actionflow canvas.MyEmailer
FromThe email address the email will be sent from. This should match the email address specified as the login email in your Outbound Emailer, see Email Account.notifications@phixflow.com
ToThe 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
CCthe 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.
BCCthe 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.
Subjectthe email's subject.

// Send the message followed by a timestamp

MyEmailer has run successsfully_ + ${now()}

Messagethe content of the email. This can accept text direct as an input as well as 

// 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.

 Treat the Message as HTML.

 Treat the Message as plain text.


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

  1. Understanding Actionflows
  2. Creating Actionflows
  3. Wiring Actionflows

For links to all pages in this topic, see Understanding Actionflows


Terminology changes in progress

As part of the redesign of PhixFlow, we are changing the following terms:

dashboard → screen   
stream → table
stream attributes → attributes
stream item → record
stream set → recordset
stream view → view
stream item action → record-action 
stream action → table-action
driver class → database driver

  • No labels