Overview Image Modified
Use the | Insert excerpt |
|---|
| _action_email |
|---|
| _action_email |
|---|
| nopanel | true |
|---|
|
node to send emails to specified addresses;| Insert excerpt |
|---|
| _property_tabs |
|---|
| _property_tabs |
|---|
| name | basic-h |
|---|
| nopanel | true |
|---|
|
Basic SettingsAll 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 Email Account. | 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 | | 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} | Insert excerpt |
|---|
| _toggle_on |
|---|
| _toggle_on |
|---|
| nopanel | true |
|---|
|
Treat the Message as HTML.| Insert excerpt |
|---|
| _toggle_off |
|---|
| _toggle_off |
|---|
| nopanel | true |
|---|
|
Treat the Message as plain text. |
|
Verifying EmailsIt 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 AttachmentsCurrently unsupported in Actionflows. To send an email with an attachment see Sending Emails. Built-in Error HandlingBasic 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. Advanced| Field | Description |
|---|
Prioritise Throughput Over Ordering | | Insert excerpt |
|---|
| Actionflow Properties |
|---|
| Actionflow Properties |
|---|
| name | PrioritiseThroughputOverOrdering |
|---|
| nopanel | true |
|---|
|
|
|