This action obviously sends an email of your design. It does have quite a few interesting options. The email can be configured to be sent to an email address you provide (multiple address can be separated by a comma) or the value of an attribute in the workflow. You can also add email addresses to CC and BCC fields. If you're using attributes to set any email address field, the attribute you provide must contain either a valid email address or the attribute must be of type Person or Group. See the Workflow Tips section of our Blasting Off With Workflows guide for a basic example of emailing a group using workflows.

If the Send To Email Addresses is a group or security role, you have the option of limiting the recipients of the email based on the group role attribute in the Send to Group Role field.

You also have the option of including up to three attachments. First, upload the file as a File type attribute, then select the workflow attribute that contains the file from the Attachment dropdown. The file size that can be sent is limited by both the sending and receiving email services, and is typically 10-25 MB.

The subject line, from address, and body of the email can contain Lava merge fields, so be creative. Also note that the email can be configured to be saved to the recipient's history.

In v14, we made have added new fields for From Name, this is displayed as the email sender's Name when the email is sentv14.1 If one is not provided and the From Email is derived from a Person then their fullname is used.

Writing the contents of a workflow email using Lava templates can be a little daunting. Also, many of these emails will be the same in similar workflow types. That's why you have an option to send an email using the contents of a system email. Just like the Send Email action, you can save the message to the recipient's history.

The system email shown on the list can be added from Admin Tools > Communications > System Communications.

This action is a bit different than most in that it is designed to continually check timeout parameters, therefore it never completes until a Unopened and/or No Action timeout occurs. Once the timeout occurs, it will complete and stop processing.

The first time it processes, it sends an email, and then creates two activity attributes. The first is a "DateTime Sent". It will set this to the time that the email was sent. It then checks this attribute in future processing to determine if it is the first process or not, and to evaluate timeout parameters.

The second activity attribute that is created is an "Email Status" attribute. This is used to store the last event status received by the Mandrill Webhooks.

During subsequent processing, this action will only check for timeouts.

If the "Unopened Timeout Activity" has an activity and "Unopened Timeout Length" has a value, it will check to see if status does not have "Opened" or "Clicked." If not, it will activate the "Unopened Timeout Activity" activity and then mark the action as complete.

If the "No Action Timeout Activity" has an activity and "No Action Timeout Length" has a value, it will check to see if status does not have "Clicked." If not, it will activate the "No Action Timeout Activity" activity and then mark the action as complete.

In addition to the action, the Mailgun.ashx and TwilioSendGrid.ashx webhooks have been updated to evaluate any events that occur for the email that was sent. When the webhook receives an event, it will attempt to find the corresponding workflow action and update the workflow action's "Email Status" activity attribute and then activate any configured activities.

When a Send event is received the attribute value will be updated to "Sent".

When an Opened event is received the attribute value will be updated to "Opened" (if not already "Opened" or "Clicked") and if an On Open Activity is configured, that activity will be activated.

When a Clicked event is received the attribute will be updated to "Clicked" and if an On Clicked Activity is configured, that activity will be activated

When a HardBounced, Rejected, SoftBounced, Spam, or Unsubscribe event is received the attribute will be updated to "Failed", and if an "On Failed Activity" value is set, that activity will be activated.

The above only applies if the workflow is still Active. Inactive workflows will not have events recorded.

The subject line, from address and body of the email can contain Lava merge fields, so be creative.

If you have a Firebase app for Rock, this action will let you send a notification to users. You can send it to either a person or a group.

This action creates an SMS Response message with the From and To number you specify.

For example, say you have a text-to-workflow set up to handle certain incoming keywords. With SMS Communication Process Response, if no keyword is found, the workflow injects the message into the person-to-person text system.

Additional Details

If the SMS system returns an error, the error message will be placed in the Error Attribute. Currently, the only error that would be returned is the standard 'Could not deliver' message. Consider checking to see if the value is non-blank, and if so, send it as a response to the user.

This action is very similar to the Send Email action but it sends a SMS text message instead. This action assumes there is a valid SMS text subscription available. See the Communicating with Rock manual for more details on SMS text message configuration.

You can also include an attachment. To include a dynamically generated attachment (for example, a contact card), use the Set Attribute From Lava workflow action.

Additional Details

Either the From field should be set with a SMS From Number or the corresponding From (From Attribute) of type DefinedValue should hold the selected SMS From Number. v12.5