Action Nodes

Action type nodes execute specific operations within the workflows. If the trigger nodes wait for contacts to do something and condition nodes ask questions about it, action nodes activate the moment contacts get to them.

actions-min.png

 

Within the action type nodes, we can see 6 different categories:

System

system.png

 

Wait

It's used to activate a waiting time between the previous and next nodes. For example, we use a "wait" node between "get products" and "send email" nodes. That way, the email will be send in the time interval that we want. There are also options to make it happen at a specific date and time, and even from imported data of previous nodes. In the following example, we'll set up the node to wait 15 minutes. 

wait-min.png

 

Schedule

It's used to program actions that we want to happen on a regular basis. For example, if we have a strategy related to sending a newsletter to our contacts every week, we can use this node to make it happen easily. In that case, we just have to change the content of the newsletter. In the following example, we'll set the node up to activate every Friday at 12:00 pm.

schedule-min.png

 

Start A/B/X Test

It's used to start an A/B/X test. This node, as well as the process it involves, is documented in it's own article. 

Evaluate A/B/X Branch

It's used to evaluate any action within one of the branches from the A/B/X test. This node, as well as the process it involves, is documented in it's own article.

Contact

contact2.png

 

Set attribute

It's used to set attributes in the contact fields. It's mainly used to channel the information from forms that were featured in previous nodes (not the email account, since that gets stored automatically). In this example, we'll use a classic lead scoring strategy to add points to the contacts profile's based on their actions. For that, we'll drag a "literal" to the "points" field and we'll make it so 10 points are added.

setatri-min.png

 

Add to segment

It's used to add contacts to a particular segment after certain events in the workflow. Works only with static segments, since dynamic ones are managed by Connectif's system. There are no setting options in this node aside from choosing the segment itself. 

addtosegment-min.png

 

Remove from segment

It's used to delete people from a segment. Aside from that, works exactly the same as the previous node. 

removefrom-min.png

 

Email

email23.png

 

Send email

It's used to send emails to the contacts. There are a few steps in this process. First, you have to choose or create the email in question. After that, there are two other steps. The first one has to do with a single screen, and the other has to do with the mappings. Since we've already talked about the later, we'll focus on the former: the configuration screen. 

 

We'll focus on the types of email first, which can be "transactional" and "newsletter". We have to make sure to know about the difference between both, because if we don't, we might select newsletter when the contacts we want to reach are not subscribe to that. If that happens, they won't recibe the email. Another key section is "parameters". Aside from the subject, which is unique to every email, you can edit the other fields to have a default every time you do this process. You can do that going to "Integrations > Email > Default Settings". 

sendemail23-min.png

 

SMS

sendsms.png

 

Send SMS

It works similarly to the "send email" node. Since we already have an article that details the settings for this node, we'll use this space to explain the SMS editor. As you can see below, it's similar to the email editor. We can add variables to the messages, and below the text box we have a counter that keeps track of the characters that we've use and have left. In the case that we use more characters than allowed per message, the system will send two SMS. 

sendsms2-min.png

 

Web

web23-min.png

 

Send Web Content

it's used to send web content to your contacts. Within every type of web content, you can see examples of how to use them in workflows, as well as their respective possibilities. These are the types of web content:

  • "Popup".
  • "Full Screen".
  • "Slide In".
  • "Floating Bar".
  • "Inline".

Display message (deprecated)

It's used to display modal windows. It's been deprecated in favor of the web contents, which allow more options and are more intuitive. 

Show push notification

It's used to activate the push notification that you select in the first step of the settings. There is only other step aside from select/create, and it's the mappings. Nonetheless, the first step has the option to choose an expiration date for the push notifications. it can be a particular date or a time interval. We'll use the latter option so that the push is deactivated after three days. 

mypushn-min.png

 

Show banner (deprecated)

Similar to the "display message" node, this node has been deprecated in favor of "send web content". To be specific, the "Inline" web content.

E-commerce

ecomer.png

 

Get purchase information

It's used to collect data related to purchases that a contact has done previously. It allows you to have different types of information, like total purchases or number of products bought, etc. All the conditions that you add have to be true for a contact to continue. In this example, we'll get the total amount of purchases during the last week. We'll let the contact continue through the workflow if they spent more than 200 euros during the week. 

getpurcha-min.png

 

Get products

This node is one of the most useful in all of Connectif. If you master it, that means that you have a certain understanding of the whole platform. It's used to gather products that will latter be shown to the contacts in web contents. It's a very effective way to show products to your contacts.

 

For this example, we'll take a case of use "best sellers", from the general section. This case takes the website as reference, not the contacts. In the settings, we can make it so that the node gets the 10 best selling products from last month. In this example, we won't add conditions, but in case that there are some, remember that all of them have to be true for a contact to go through.

getpru-min.png

 

Get last cart

It's used to gather data about the last cart of every contact. It could be any type of cart: active, abandoned, purchased, etc. Once we choose one type, we can select the orden in which we will get the products, either ascending or descending and depending on the price or priority. The quantity can only be in ascending order. In this example, we'll take the last abandoned cart and we'll sort the products by ascending price.

getlastcar-min.png

Was this article helpful?
0 out of 0 found this helpful