Este artigo está atualmente disponível em inglês e espanhol. Você pode usar esta documentação enquanto ela não estiver disponível em seu idioma.
Action-type nodes are used to execute specific operations within flows. The moment a user arrives at an action-type node, their activity begins.
How do the different action-type nodes work?
By default, the different action-type nodes fall into six categories, depending on the area where they are executed:
1. System
Nodes in the System category perform checks related to the Connectif platform.
1.1. "Wait" node
This node is used to activate a certain wait time between the nodes that precede and follow it. In the node interface, you can configure the parameters that determine the wait:
- A period of time. For example: 1 day and 15 hours.
- Until a specific date and time. For example: until July 23, 2023 at 2 p.m.
- Until the date of imported data. For example: Three days after the last purchase made.
The example shows a wait for a given interval of one hour.
1.2. “Plan” node
This node is used to program actions that you want to perform on a regular basis. In the node interface, you can configure the planning options:
- How often do you want it to repeat? To determine the periodicity. For example: weekly, every week, on Fridays.
- Select the time of day at which to launch the cycle. To set the time at which that action will be repeated.
- Select when to stop repeating. To determine the repetition limit for that action.
The example shows a weekly schedule, which will be repeated for five weeks on Thursdays at 10:30 AM CET and will not stop repeating.
1.3. “Start A/B/X test” node
This node is used to activate the start of an A/B/X test in a workflow. In the node interface you can configure the test parameters, which will help determine the winning branch.
Learn how the “Start A/B/X test” node works in this article.
1.4. “Evaluate A/B/X branch” node
This node is used to evaluate any action within an A/B/X test branch. In the node interface, you can configure the points added to the branch when it is executed.
Learn how the “Evaluate A/B/X branch” node works in this article.
1.5. “Split” node
This node is used to divide the workflow flow based on a probability that a contact will be directed by one branch or another. In the node interface, this probability is configured, automatically or manually.
Learn how the “Split” node works in this article.
2. Contact
The nodes in the Contacts category perform checks that involve contact activity or information.
2.1. “Set field” node
This node is used to establish contact fields and collect contact information. In the node interface, you can configure the different contact fields as well as assigning literal values.
The example shows a sum of points that can be used in Lead Scoring strategies. To do this, drag "Literal" to the "Points" field and modify it to add 10 points.
2.2. “Add to segment” node
This node is used to add the contacts that reach it to a static segment. In the node interface, you can configure the segment to which the contacts will be assigned.
In the example, users who arrive at that node are set to be added to the “Segment Example” segment.
2.3. “Remove from Segment” Node
This node is used to extract contacts from a static segment, working just like the “Add to Segment” node. This node does not delete contacts from the Connectif database. In the node interface, you can configure the segment from which the contacts will be deleted.
In the example, users who arrive at that node are set to be removed from the “Segment Example” segment.
3. Email
Nodes in the Email category are those that perform checks involving email content.
3.1. “Send email” node
This node is used to send an email to contacts that arrive at that part of the workflow. In the node interface, you can configure all aspects of the email to be sent and the receivers in steps:
- Email template settings (1). To select a previously-created email or set up a new one in the email editor.
-
Node configuration (2). To configure how it will be sent:
- Send to. To choose between Contacts, and send that email to users whose “Email status” is "Active", or Specific email, and manually indicate which email addresses will receive it.
- Selecting the type of email. To choose if the email will be Transactional and sent to all contacts, or Newsletter, and sent to users whose “Newsletter status” is "Subscribed".
- Parameters. To set the Email subject, the Source name, the Source email and the Reply email.
You can configure the Source name, the Source email and the Reply email so that they are always the same by default from "Integrations > Email > Default settings".
- Configuring fields and values (3). To assign or modify the values of the email variables.
- Google Analytics (4). To set the unique email parameters that will be followed in Google Analytics.
The example shows the configuration interface of the node (2).
4. SMS
Nodes in the SMS category perform checks involving SMS content.
4.1. “Send SMS” node
This node is used to send an SMS to contacts that arrive at that part of the workflow. In the node interface, all aspects of the message to be sent and its recipients are configured in steps.
Learn how the nodo “Send SMS” node works in this article.
5. Website
Web category nodes perform checks involving web content.
5.1. “Send web content” node
This node is used to display specific web content to contacts who arrive at that part of the workflow. In the node interface, configure what the content is and how it will be displayed.
Learn how the “On clicking web content” node works in this article.
5.2. “Display push” node
This node is used to display a specific push notification to contacts that arrive at that part of the workflow. In the node interface, all aspects of the notification to be displayed are configured in steps:
- Notification settings (1). To select a previously-created push notification or configure a new one in the web push notification editor. In this step, you can also set an expiration date for the notification.
- Configuring fields and values (2). To assign or modify the values of the email variables
The example shows the notification configuration interface (1).
6. Ecommerce
Ecommerce category nodes perform checks involving ecommerce information.
6.1. “Get Purchase Data” Node
This node is used to obtain data related to the contact’s previous purchases. In the node interface, you can configure the information to be extracted:
- Any purchase. To choose what aspect of the purchase you want to obtain, filtered by product or by purchase.
- Configure the conditions to obtain a specific series of purchases. To filter the conditions that must be met by the purchases from which the information will be obtained.
All conditions must be met to allow the contact to continue the flow.
In the example, the total sum of purchases made in the last week is obtained. The node will allow the contact to continue through the flow if the total price spent in that interval is greater than 200 euros.
6.2. “Get Products” Node
This node is used to collect products that are then shown to contacts in the different web contents. In the node interface, you can configure the different use cases from which the items will be obtained.
Learn how the “Get Products” node works in this article.
6.3. “Get Last Cart” node
This node is used to collect the data referring to the last cart for each contact. In the node interface, you can configure the properties of the cart and how the products will be obtained:
- Select the cart status. To choose active, abandoned or purchased carts, or any cart (the default option).
- Configure the order in which the products in the cart will be obtained.. To select the order in which the products will be obtained, generally ascending or descending by price, priority or valuation, while the quantity can only be ascending.
In the example, the last abandoned cart is selected and the products are ordered by ascending price.
6.4. “Assign voucher” node
This node is used to obtain a voucher and send it automatically to a contact. In the node interface, the voucher database from which these codes will be obtained is configured in steps.
- Set (1). To select the main database from which the vouchers will be obtained.
- Configure (2). (Optional). To select an alternative database from which to continue obtaining the vouchers, in case the codes in the main list have just been assigned.
The example shows the interface of the set step (1), in which the base “Bulk Vouchers” is selected as the main one.
Congratulations!
You’ve reached the end of the tutorial.
Do you have questions?
Don’t forget, our Connectif specialists are here to help you. To contact them, just open a Support ticket by clicking the blue “Help” button on your dashboard.
Keep learning!
To make the most of your Connectif account, we recommend reading these articles next:
- Condition-type nodes, to filter the requirements the contacts must meet to continue through the flow.
- Trigger-type nodes, to be used in real time when the contacts perform an activity.
- Limitations in nodes, to configure the conditions under which the nodes will not be triggered.
- Directory of workflow templates, to locate the templates available to use in your strategies.