Message Blocks

Blocks send one message to one contact.

Contains eight block types:

Common Block Parameters

Each block contains the following parameters:

• Message: required parameter. 

To select a message:

1. Click the Select message button on the right side of the settings panel.

2. Select a message from the list (by default, the last created one is selected) or specify the dynamic variable ${emailMessageId} using the button next to the search bar.

To search the message in the list, use the search field by message name, subject, tag, or ID.

You can also sort messages by their update date

If a workflow is associated with a message, it appears in the list. To open a preview of the workflow, hover over its name and click the corresponding icon.

The following actions are available in the message selection window:

• Create a message copy

• Message preview

3. Click the Select button.

By clicking on the three-dot icon, after selecting the message in the block settings, you can:

• Preview the message

• Replace the message

• Edit the message in a new tab

• Copy the ID

If you delete the message, a corresponding tooltip will appear in the block settings.

In that case, you should select a new one by clicking the Replace message button.

• Phone (for SMS, Viber and Web Push blocks): required parameter, a phone number of the contact or event parameter containing it. The variable ${phoneNumber} is specified by default. In your event, the variable may be called ${SMS}, ${Phone}.

To check the exact title, go to Automation → Event history, and click the event that triggers the workflow.

A phone number is specified in digits, for example,12018627991, only for testing.

• Contact ID. You can specify system contact ID other than an email address. Enter in field the name of the parameter containing the contact ID. For many system events, this parameter is called ContactId.

• JSON: you can enter data in the JSON format or specify the event parameter that contains such data. Don't fill this field if you don’t pass in the event the parameter with the JSON line.

JSON example:

{ "name": "items", "value": "{\"array\":[{\"name\":\"Brenda Flatform Sport Sandals\",\"price\":\"100.00\",\"url\":\"https://site.com/catalog/steve-madden-brenda-flatform-sport-sandals?ID=8472233&CategoryID=56233&swatchColor=Natural\",\"imageUrl\":\"https://site.com/uploads/product/big/20161122/20161122_7zvb.jpg\"},{\"name\":\"Cloudsteppers Women's Brio Sol Flip-Flop Sandals\",\"price\":\"78.00\",\"url\":\"https://site.com/catalog/clarks-cloudsteppers-womens-brio-sol-flip-flop-sandals?ID=10566812&CategoryID=56233&swatchColor=Red%20Synthetic\",\"imageUrl\":\"https://site.com/uploads/product/big/23112013/2125.jpg\"}]}" }

Sharing the JSON field with the Get contact block requires access to data from this field through the intermediate jsonParam object, using the example of the array items, the field name of the first element will be available using this construction:

$!data.get('jsonParam').get('array').get(0).get('name')

If the Get contact block isn’t used, the construction will be:

$!data.get ('array')

• Send only in specified hours: You can enable this parameter to send messages only within a specified time gap.

By default, day hours from 08:00 to 20:00 are set as send hours. Such setting allows not to annoy recipients at an inappropriate time and schedule send at permitted hours. To change specified hours or change allowed hours for each day, go to your profile → Settings → Workflows.

See more detailed information >

The corresponding marks on the block show whether this parameter is enabled for a particular message:

1. Regular icon means the message can be sent at any time.
2. Clock mark icon means the message can be sent only at specified hours.

One from Many

The task of the block is to select from several messages with certain tags the one that is likely to have the best CTR and send it.

The block has such parameters:

• Send via — select a media channel (you can select any).
• Application — the name of a Mobile Push app or Telegram bot (there is no option to select an application if there is only one app or bot registered in the account — the corresponding parameter will be applied automatically).
• Include variants with tags – select the tags that messages should have. The number next to the tags indicates the number of messages with these tags.
• Exclude variants with tags – select the tags that messages should not have.
• Send only in specified hours.

To quickly view the corresponding messages, click the preview icon in the field with the number of selected options.

More on block usage >

Email

The block sends one email to one contact.

In addition to the common block parameters, the block has such parameters:

• Email: email address of the contact or the event parameter that contains an email address. The variable ${emailAddress} is specified by default. If in your event this parameter has a different title, enter it.
• Language: language ID or the event parameter containing it. It is needed to create multilingual messages. Leave the field blank if you don't use Multilanguage, or the language of the contacts is specified in their carts.
  Language parameter example:

Language parameter can be entered in the following formats:

• en, es, fr;
• EN, ES, FR;
• en-US, fr-CA, en-AR.

SMS

The block sends one SMS to one contact.

A phone number is specified in digits, for example,12018627991, only for testing.

Viber

The block sends one Viber message to one contact.

In addition to the common block parameters, the block has Message activity time (TTL) parameter. TTL it's a period after which the message will not be displayed if it has not been delivered by this time.

Viber messages are sent only to contacts with a phone number specified in the contact card. If the contact doesn’t have a phone number, the workflow will ignore the Viber block, and the Viber message won’t be sent to this contact.

Web Push

The block sends one Web Push to one contact. After subscribing, the system will search for the contact among existing ones. If it manages to identify the contact, a push token will be added to that contact's card. If not, a new contact will be automatically created with the token only.

In addition to the common block parameters, the block has such parameters:

• Token. The variable ${pushToken} is specified by default.
• Email. Email address of the contact or the event parameter that contains an email address. The variable ${emailAddress} is specified by default. If in your event this parameter has a different title, enter it.

Mobile Push

The block sends one mobile push notification to one contact.

In addition to the common block parameters, the block has such parameters:

• Token: mobile token of the contact. The variable ${mobPushToken} is specified by default.

• Application: an app identifier for accounts with more than one app. You can select the app to send notifications from the dropdown list or specify dynamic parameter ${appId}. The system extracts the app ID from the event that has triggered the workflow. When sending events through the SDK, this parameter is passed automatically.

App Inbox

The block sends one app inbox notification to one contact.

Telegram

The block sends one Telegram message to one contact.

In addition to the common block parameters, the block has such parameters:

• Token — Telegram token of the contact. The variable ${telegramBotToken} is specified by default.

• Telegram bot — a bot identifier for accounts with more than one bot. You can select the bot to send messages from the dropdown list or specify dynamic parameter ${appId}. The system extracts the bot ID from the event that has triggered the workflow.