Sending a Message with Workflows

Overview

The Send Message action will sends a message to the workflow enrollment contact or an otherwise designated contact

This is a Sakari Workflows feature and is currently in Beta.

To request access to the beta, please complete this survey.

Setup

To configuring the action, set the contact that the message should be sent to and choose an outbound group.

Send From

  • Group Name

    • Dropdown menu of existing groups
  • Custom
    • ?

Send To

Define the contact that the message will send to

  • Contact
    • Enrollment Contact
    • Output Contact
  • Internal currently disabled
    • Select an internal user to send the message to using the phone number configured in user profile
  • Custom
    • Enter a custom phone number to send the message
      • E.164 format

Message

  • Utilizes Sakari Message creation interface
    • Upload media (MMS)
    • Insert link
    • Use AI assistant
    • Insert attribute (as token)
      • Enrollment Contact Property
      • Workflow Property
      • Output Property

Note:

This action results in 2 branches.  Contacts that are successfully sent a message will proceed through the sent branch, whereas any errors will results in the failure branch

Screenshot 2024-07-10 at 20.59.38.png

 

 

Output Properties

Output properties [add article link] are properties that an action or trigger generates that can be used by other triggers and actions downstream in your workflow. 

This action generates the following property option(s): 

  • Valid
  • Requested
  • Estimated Price
  • Group
  • Message
  • Contact

 

Examples

Example 1

In this example, a message will be sent to the enrolled contact from a phone number configured in My First Group.  Additionally, the First Name contact attribute is used as a token for the enrolled contact

Screenshot 2024-07-10 at 21.03.18.png

 

Example 2

In this example, a message will be sent to a custom phone number as a notification that an enrolled contact has clicked a link.

Screenshot 2024-07-10 at 21.05.36.png

 

FAQ