Actions Blocks

Actions blocks are used to set up an action in a workflow. The system performs such actions at a particular period of time or at a particular stage of contact management.

There are 14 action blocks in the eSputnik system:

  • Email;
  • SMS;
  • Viber;
  • Web Push;
  • Mob Push;
  • Email to segment;
  • SMS to segment;
  • Viber to segment;
  • Web push to segment;
  • Mob push to segment;
  • Add to segment;
  • Remove from segment;
  • Check point;
  • Sprayer.

Email

The block sends one email to one contact.

Action blocks in the eSputnik workflow builder

The block has 5 parameters:

  • Message: required parameter. You can select the necessary message in two ways:
  1. Select from the drop-down menu (the easiest and most common way).
  2. Specify the message ID (select ${EmailMessageId} from the drop-down menu or click the gear icon and enter in both fields the name of the parameter that contains a message ID in your event, without ${}).

Action blocks in the eSputnik workflow builder

  • Сontact’s 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.
  • Contact ID: contact ID in the system. You can specify contact ID other than an email address. Click the gear icon and enter in both fields the name of the parameter containing the contact ID. For many system events, this parameter is called ContactId. Note that in these fields the parameter is entered without ${}.
  • 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 block Get contact 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 block Get contact isn’t used, the construction will be: $!data.get ('array').

  • Language parameter: 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.

Event parameter example:

Action blocks in the eSputnik workflow builder

Language ID can be entered as follows:

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

Action blocks in the eSputnik workflow builder

You can also enable Send only at specified hours to send messages only within a specified time gap.

Action blocks in the eSputnik workflow builder

By default, day hours from 8 a.m. to 8 p.m 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.

Action blocks in the eSputnik workflow builder

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

  1. 24/7 means the email can be sent at any time;
  2. clock mark means the email can be sent only at specified hours.

Action blocks in the eSputnik workflow builder

SMS

The block sends one SMS to one contact.

Action blocks in the eSputnik workflow builder

The block has 4 parameters:

  • Message: required parameter. The settings are the same as for the block Email.
  • Phone: 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}, ${PhoneNumber}, ${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.

Action blocks in the eSputnik workflow builder

  • Contact ID: contact ID in the system. You can specify contact ID other than a phone number. Click the gear icon and enter in both fields the name of the parameter containing the contact ID. For many system events, this parameter is called ContactId. Note that in these fields the parameter is entered without ${}.
  • 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 block Get contact 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 block Get contact isn’t used, the construction will be: $!data.get ('array').

You can also enable Send only at specified hours to send messages only within a specified time gap.

Viber

The block sends one Viber message to one contact.

Action blocks in the eSputnik workflow builder

The block has 5 parameters:

  • Message: required parameter. The settings are the same as for the block Email.
  • Phone: required parameter, a phone number of the contact or the event parameter containing it. The variable ${PhoneNumber} is specified by default. In your event, the variable may be called ${SMS}, ${PhoneNumber}, ${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: contact ID in the system. You can specify contact ID other than a phone number. Click the gear icon and enter in both fields the name of the parameter containing the contact ID. For many system events, this parameter is called ContactId. Note that in these fields the parameter is entered without ${}.

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 block Viber, and the Viber message won’t be sent to this contact.

Action blocks in the eSputnik workflow builder

Important!

The block Viber will be ignored for contacts without a phone number if it’s included in a workflow with multiple blocks.

  • Message time to live, sec: leave the default setting. After the specified time, the message will be deleted from the phone.
  • 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.

Sharing the JSON field with the block Get contact 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 block Get contact isn’t used, the construction will be: $!data.get ('array').

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\"}]}"

}

You can also enable Send only at specified hours to send messages only within a specified time gap.

Web Push

The block sends one web push notification to one contact.

Action blocks in the eSputnik workflow builder

The block has 7 parameters:

  • Message: required parameter. The settings are the same as for the block Email.
  • Token: token of the contact. The variable ${pushToken} is specified by default.
  • Phone: phone number of the contact. The variable ${PhoneNumber} is specified by default.
  • Сontact’s email: email address of the contact. The variable ${EmailAddress} is specified by default.
  • Active time: period of time during which a web push can be stored in the system if the contact isn’t currently available for delivery. The web push won’t be sent after its active time expires. Select the necessary active period from the drop-down menu.
  • Contact ID: contact ID in the system. The variable ${PushContactId} is specified by default.
  • 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.

Sharing the JSON field with the block Get contact 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 block Get contact isn’t used, the construction will be: $!data.get ('array').

You can also enable Send only at specified hours to send messages only within a specified time gap.

Important!

To send web pushes, the system needs a token of the contact. If the data in the contact card is combined (email address+phone number+ID+token), the token can be found by other parameters, not necessarily ${pushToken}. The system will search in turn if the contact with a specified email, phone number or ID has a token.

Mob Push

The block sends one mobile push notification to one contact.

Note. To send mobile pushes, you need to have an app which you need to connect to eSputnik.

Action blocks in the eSputnik workflow builder

The block has 5 parameters:

  • Message: required parameter. The settings are the same as for the block Email.
  • Token: mobile token of the contact. The variable ${pushToken} is specified by default.
  • Active time: period of time during which a mobile push can be stored in the system if the contact isn’t currently available for delivery. The web push won’t be sent after its active time expires. Select the necessary active period from the drop-down menu.
  • Contact ID: contact ID in the system. The variable ${ContactId} is specified by default.
  • 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.

Sharing the JSON field with the block Get contact 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 block Get contact isn’t used, the construction will be: $!data.get ('array').

You can also enable Send only at specified hours to send messages only within a specified time gap.

Important!

To send mobile pushes, the system needs a token of the contact. If the data in the contact card is combined (email address+phone number+ID+token), the token can be found by other parameters, not necessarily ${pushToken}. The system will search in turn if the contact with a specified email, phone number, or ID has a token.

Email to Segment

The block sends one email to a contact segment. It’s used in a workflow after contact import or to launch a series of emails.

Typically, one workflow includes either the block Email or the block Email to segment.

Action blocks in the eSputnik workflow builder

Important!

Do not use this block for triggered emails. If the event passes the email address of the contact, use the block Email.

The block Email to segment is only used for events that pass the segment ID, or for workflows that are launched for a selected segment.

Even if you set Regular in Trigger configuration and select a segment, you still need to use the block Email, because this trigger type doesn’t pass a segment group ID to the workflow. Instead, it launches the workflow separately for each segment contact and passes the email address and contact ID at each launch.

The block has 2 parameters:

  • Message: required parameter. The settings are the same as for the block Email.
  • Segment: required parameter. Select the segment from the drop-down menu or specify the segment ID (select ${GroupId} from the drop-down menu or click the gear icon and enter in both fields the name of the parameter that contains a segment ID in your event, without ${}.

You can also enable Send only at specified hours to send messages only within a specified time gap.

Important!

Each segment in the eSputnik system has its own ID. For example, if you send an event and with an ID value pass the GroupId parameter

{

"name":"GroupId", "value":167039898

}

167039898 will be substituted into the workflow instead of GroupId, and the workflow will be launched to this segment.

You need to know what the ID corresponds to so as to control the campaign, indicating what to send to which segment.

SMS to Segment

The block sends one SMS to a contact segment.

Typically, one workflow includes either the block SMS or the block SMS to segment.

Action blocks in the eSputnik workflow builder

Important!

Do not use this block for triggered messages. If the event passes the phone number of the contact, use the block SMS.

The block SMS to segment is only used for events that pass the segment ID, or for workflows that are launched for a selected segment (for example, dynamic).

Even if you set Regular in Trigger configuration and select a segment, you still need to use the block SMS, because this trigger type doesn’t pass a segment group ID to the workflow. Instead, it launches the workflow separately for each segment contact and passes the email address and contact ID at each launch.

The block has 2 parameters:

  • Message: required parameter. The settings are the same as for the block Email.
  • Segment: required parameter. Select the segment in the drop-down menu or specify the segment ID (select ${GroupId} from the drop-down menu or click the gear icon and enter in both fields the name of the parameter that contains a segment ID in your event, without ${}).

You can also enable Send only at specified hours to send messages only within a specified time gap.

Viber to Segment

The block sends one Viber message to a contact segment.

Typically, one workflow includes either the block Viber or the block Viber to segment.

Action blocks in the eSputnik workflow builder

Important!

Do not use this block for triggered messages. If the event passes the phone number of the contact, use the block Viber.

The block Viber to segment is only used for events that pass the segment ID, or for workflows that are launched for a selected segment (for example, dynamic).

Even if you set Regular in Trigger configuration and select a segment, you still need to use the block Viber, because this trigger type doesn’t pass a segment group ID to the workflow. Instead, it launches the workflow separately for each segment contact and passes the email address and contact ID at each launch.

The block has 2 parameters:

  • Message: required parameter. The settings are the same as for the block Email.
  • Segment: required parameter. Select the segment in the drop-down menu or specify the segment ID (select ${GroupId} from the drop-down menu or click the gear icon and enter in both fields the name of the parameter that contains a segment ID in your event, without ${}).

You can also enable Send only at specified hours to send messages only within a specified time gap.

Web Push to Segment

The block sends one web push to a contact segment.

Typically, one workflow includes either the block Web Push or the block Web Push to segment.

Action blocks in the eSputnik workflow builder

Important!

Do not use this block for triggered messages. If the event passes the token or contact ID, use the block Web Push.

The block Web Push to segment is only used for events that pass the segment ID, or for workflows that are launched for a selected segment (for example, dynamic).

Even if you set Regular in Trigger configuration and select a segment, you still need to use the block Web Push, because this trigger type doesn’t pass a segment group ID to the workflow. Instead, it launches the workflow separately for each segment contact and passes the email address and contact ID at each launch.

The block has 3 parameters:

  • Message: required parameter. The settings are the same as for the block Email.
  • Segment: required parameter. Select the segment in the drop-down menu or specify the segment ID (select ${GroupId} from the drop-down menu or click the gear icon and enter in both fields the name of the parameter that contains a segment ID in your event, without ${}).
  • Site: the website that collects tokens is specified by default. If you have several websites, choose one from the drop-down menu.

You can also enable Send only at specified hours to send messages only within a specified time gap.

Mob Push to Segment

The block sends one mobile push to a contact segment.

Typically, one workflow includes either the block Mob Push or the block Mob Push to segment.

Action blocks in the eSputnik workflow builder

Important!

Do not use this block for triggered messages. If the event passes the phone number of the contact, use the block Mob Push.

The block Mob Push to segment is only used for events that pass the segment ID, or for workflows that are launched for a selected segment (for example, dynamic).

Even if you set Regular in Trigger configuration and select a segment, you still need to use the block Mob Push, because this trigger type doesn’t pass a segment group ID to the workflow. Instead, it launches the workflow separately for each segment contact and passes the email address and contact ID at each launch.

The block has 2 parameters:

  • Message: required parameter. The settings are the same as for the block Email.
  • Segment: required parameter. Select the segment in the drop-down menu or specify the segment ID (select ${GroupId} from the drop-down menu or click the gear icon and enter in both fields the name of the parameter that contains a segment ID in your event, without ${}).

You can also enable Send only at specified hours to send messages only within a specified time gap.

Add to Segment

The block adds a contact to a list segment after they perform a specific action on the website or in the message.

Action blocks in the eSputnik workflow builder

The block has 4 parameters:

  • Segment: required parameter. Select the segment in the drop-down menu or specify the segment ID.
  • Contact’s email: email address of the contact.
  • Contact ID: contact ID in the system.
  • Phone: phone number of the contact.

By default, the contact is identified in the system by email address. The variable that contains a contact’s email address is already specified in the field. Change it only if you change the variable that passes it.

Important!

You can add a contact only to a list segment. You cannot add contacts to dynamic or combined segments.

Remove from Segment

The block removes a contact from a list segment. After removal, the contact remains in the system.

Action blocks in the eSputnik workflow builder

The block has 4 parameters:

  • Segment: required parameter. Select the segment in the drop-down menu or specify the segment ID.
  • Contact’s email: email address of the contact.
  • Contact ID: contact ID in the system.
  • Phone: phone number of the contact.

By default, the contact is identified in the system by email address. The variable that contains a contact’s email address is already specified in the field. Change it only if you change the variable that passes it.

Important!

You can remove a contact only from a list segment. You cannot remove contacts from dynamic or combined segments.

Check Point

The block does not perform any task except that it fixes in the log the passage of the checkpoint in the workflow. If you have a complex workflow with paths, add this block at any point in the workflow to see if it ran a particular path. Check point can also be used to bridge multiple paths. Not all blocks allow connection to several paths, and this block solves this issue.

Action blocks in the eSputnik workflow builder

The block has 1 parameter:

  • Name: specify the name of the check point.

In Automation > Event history, use Check point’s name to track whether the workflow has passed this point or not. This helps debug the workflow.

Sprayer

The block creates events for each contact of the selected segment.

As a rule, if the workflow is launched for a segment, you cannot add there blocks designed for contacts. Sprayer enables to do so.

It works as follows:

  • The workflow for a segment has been launched (the segment ID was passed in the event, or the segment is selected in the Sprayer settings).
  • The workflow reaches the block Sprayer.
  • A separate event for each contact is created (transition from segments to contacts).
  • This event launches a workflow for each contact.

The events created by the block contain an email address and contact ID. This makes it possible to launch a different workflow with these events and use contact blocks.

Action blocks in the eSputnik workflow builder

The block has 2 parameters:

  • Segment: required parameter. Select the segment in the drop-down menu or specify the segment ID (select ${GroupId} from the drop-down menu or click the gear icon and enter in both fields the name of the parameter that contains a segment ID in your event, without ${}).
  • Event: required parameter. Select the event you want to create. Events must be created beforehand in Automation > Event types.
Any Questions?
We’re always happy to help!
Request a Callback
Fill in the form, and our specialists will call you back as soon as possible.
Request a Callback
Chat Support
We’re waiting for your questions!
Send a Chat Message
Email
Contact the eSputnik support team
Send an Email