Blocks description (Actions group)

Actions Group consists of following blocks:

Email

The block sends 1 letter to the 1 recipient.



The block includes 5 parameters:

  • Message - choose from the list the created letter in eSputnik
  • Email contact - specify the email address of the contact or parameter from the event that contains the email address.
  • Contact - instead of email, you can specify the contact id in the system. Usually not used
  • JSON - here you can insert data for substitution into a letter in JSON format. Or, specify a parameter from the event that contains such data. Do not enter anything in this field, unless you pass a parameter with a string in the JSON format in the event.
  • Message language - the language identifier or parameter from the event containing is inserted into the field. It is used for multilanguage in the trigger messages. Do not enter anything if you do not use multilanguage.

It is mandatory Message parameter. The remaining parameters are filled depending on the tasks.

The message is selected in the Message parameter and will be sent. Accordingly, you must first create a letter that will be sent, and then select it.


SMS

The task of the block is to send an SMS message to the user. The block is used for sending single messages and works similarly to the Email block, but instead sends an SMS.



This block includes 4 parameters:

  • Message - select from the list an SMS message that was previously created in the system.
  • Contact phone number is the recipient's phone number or the parameter from the event that contains it.
  • Contact - you can use the contact id instead of the phone number. To do this, click the gear and enter the name of the parameter containing the contact id in both fields. For many system events, this parameter is called ContactId. Note that the parameter is written without ${} in these fields.
  • JSON - this can insert data for substitution into a message in JSON format. Or, specify a parameter from the event that contains such data. Do not enter anything in this field unless you pass a parameter with a string in the JSON format in the event.

Push

The block sends a Push notification to the user. In order for the user to receive Push, he must first sign up for push notifications.

The block works similarly to the Email block, but it sends a Push notification instead of the letter.



The block includes 6 parameters:

  • Message - select from the list a pre-generated push message
  • Token - subscriber token
  • SMS - subscriber's phone number
  • Email - subscriber's email address
  • Push Activity Time - the time during which the system will attempt to deliver a push message to the subscriber
  • Contact - contact id in the system
  • JSON - this can insert data for substitution into a message in JSON format. Or, specify a parameter from the event that contains such data. Do not enter anything in this field unless you pass a parameter with a string in the JSON format in the event.

Important! Push messages are sent using a token (Token), so the system has to "know" the subscriber token. But if the token is attached to the contact in the system, then the system can find the token via other contact channels (Email, SMS, id). In this field, you can fill in those fields to search for the token that you have. You can fill in several fields. The system will search by this parameters one by one.

Email to group

Sends a letter to a group of contacts that is a mass mailing. In this block, not a single recipient is selected, but a group.

 Important! The block is not suitable for triggers. If the email address of the contact is sent to the event, then you should use the usual Email block.
The Email group is used only if the group id is passed to the event or specific groups are selected in the scenario itself.

 Important! If you use the condition to run the Regular scenario in which the group is selected, you still need to use the single Email block. The point is that this trigger condition does not pass the group id to the scenario. Instead, it runs the scenario separately for each member of the group and sends an email and a contact id each time it starts.

 Important! Usually, the scenario uses either only messaging group blocks or only single message blocks.



The block includes 2 mandatory parameters:

  • Message - select the message you want to send to the group
  • Group - select the group you want to send the message to. You can choose from the drop-down list or register the group id (click on the gear and assign the group id). If the field is left blank, the GroupId parameter will be used by default.

SMS to group

The task of the block is to send an SMS message to a certain group of contacts.

 Important! The block is not suitable for triggers. If a contact's phone number or contact id is sent to the event, then a single SMS block should be used.
An SMS group is used only if an id is passed to the event or specific groups are selected in the scenario itself.

  Important! If you use the condition of running the Regular scenario in which the group is selected, you still need to use a single SMS block. The point is that this trigger condition does not pass the group id to the scenario. Instead, it runs the scenario separately for each member of the group and sends an email and a contact id each time it starts.

 Important! Usually, the script uses only either messaging group blocks or single message blocks.




The block includes 2 mandatory parameters:

  • Message - select the message you want to send to the group
  • Group - select the group you want to send the message to. You can choose from the drop-down list or register the group id (click on the gear and assign the group id). If the field is left blank, the GroupId parameter will be used by default.

Add to group

The task of this block is to add the user to a certain static group (list).


The block includes 3 parameters:

  • Group - select from the list the group to which you want to add a contact
  • Contact Email
  • Contact ID

The Contact Email and Contact ID parameters are used to select the contact's identification method. By default, the contact is identified by email. This field already contains the name of the variable that contains the subscriber's email. You change it only if you create your own variable, which contains the person's email.

 Important! You can add a user only to a static group (list). You cannot add a user to a dynamic or compound group.

Remove from the group

The task of the block is to delete the user from a certain static group (list). The contact will remain in the system.

It works in the same way as the Add to group block, only it does not add a contact, but removes it from the group.



The block includes 3 parameters:

  • Group - select the group from the list from which to delete the contact
  • Contact Email
  • Contact ID

The Contact Email and Contact ID parameters are used to select the contact's identification method. By default, the contact is identified by email. In this field, by default, the name of the variable that contains the person's email is already registered. You change it only if you create your own variable that contains the person's email.

 Important! You can remove a user only from a static group (list). You can not remove a user from a dynamic or compound group.

Checkpoint

The block does not perform any actions, except that it places a record of itself triggering in the log of the scenario operation. If you have a complex scenario with ramifications, then you can put this block anywhere and then in the log look whether the scenario has passed on a certain path.



The block has just one parameter:

  • Name - It is mandatory. The name of the verification point. It helps to understand what point of verification is meant and analyze the information collected.

Sprayer

The block creates events for each participant of the selected group.
The fact is that in one scenario you can not use group and single blocks at the same time. If the scenario is for a group, we can not use blocks in this scenario that are intended for single contacts. The sprayer block gives this opportunity. The events created by the block contain the email address and contact id. This allows you to run these events in a different scenarios and use the blocks for sending single messages.



The principle of operation is as follows:

  • the scenario for groups has started (the group id was assigned in the event or the group was selected in the settings of the sprayer)
  • the scenario reaches the sprayer block
  • a separate event is created for each contact (switching from groups to single contacts)
  • And now this event will launch a scenario for a single contact.

The block includes 2 parameters:

  • Group - choose the group from the list for which you want to create single events. You can choose from the drop-down list or register the group id (to do this click on the gear and prescribe the id of the group). If the field is not filled, the GroupId parameter is used by default
  • Event - select the type of event that you want to create. The type of the event must first be created in the Triggers - Event types

Previous topics

Part 1. Blocks Description (General Group)

Part 3. Blocks description (Conditions group)