Journeys are created by nodes, which are connecting points that define an intended direction. Node triggers interact with actions and conditions to create a customer’s journey.


When a customer is ejected from a journey, the customer has completed a session. However, customers can re-enter a journey or start another session generated by a trigger from a different journey.


Most nodes can be configured to create specific customer journeys. 


This document outlines supported triggers that can be added in a customer journey. Conditions can be used with actions and conditions.


The following triggers are supported in nodes:


*Node configuration is required—the node displays a warning icon until configuration is complete. 


All other nodes include default settings that can be used to begin a journey without specific configuration.


Note: Nodes that are configured incorrectly or not configured at all display a warning icon within the journey page. 




Triggers


Transaction

Node summary: A customer is placed in an associated journey after completing a transaction.


Node Menus

This node includes two menus: Select Location(s) and Select Market(s).


When node preferences are applied, no summary data displays in the node.


Select Location(s)

The node requires a location, which specifies that only customers from the selected location will be placed in the journey. By default, all locations are set for the location. 


An individual location can also be selected in the date drop-down menu. Only pre-created locations can be selected in the menu. Locations are most commonly created through transaction data and can be edited in the Assets section. 


Select Market(s)

A specific market can also be set for the node. A market is a grouping of stores, such as stores in the same city, state, or region. Only pre-created markets can be selected in the menu. Markets can be created as part of the onboarding process or at any time by submitting a support case.


Node Connection

Once the node is configured, the condition can be connected to another node to build a path along the journey. Connections are made by hovering the mouse pointer over the node, clicking the gray arrow, and dragging the arrow to the intended node.


Connections can be made with multiple nodes.


If the arrow is not retained on the node and displays a gray path, the selected condition is not supported for the intended node.


This node connection does not include configuration options.


Back to Section Menu



Added to Schedule

Node summary: A customer has made an appointment for your company’s service and has been added to the schedule.


Node Menus

This node includes two menus: Select Location(s) and Select Market(s).


When node preferences are applied, no summary data displays in the node.


Select Location(s)

The node requires a location, which specifies that only customers from the selected location will be placed in the journey. By default, all locations are set for the location. 


An individual location can also be selected in the date drop-down menu. Only pre-created locations can be selected in the menu. Locations are most commonly created through transaction data and can be edited in the Assets section. 


Select Market(s)

A specific market can also be set for the node. A market is a grouping of stores, such as stores in the same city, state, or region. Only pre-created markets can be selected in the menu. Markets can be created as part of the onboarding process or at any time by submitting a support case.


Node Connection

Once the node is configured, the condition can be connected to another node to build a path along the journey. Connections are made by hovering the mouse pointer over the node, clicking the gray arrow, and dragging the arrow to the intended node.


Connections can be made with multiple nodes.


If the arrow is not retained on the node and displays a gray path, the selected condition is not supported for the intended node.


This node connection does not include configuration options.


Back to Section Menu



Time Trigger*

Node summary: A customer from a selected segment is placed into the journey at an assigned date and time. 


Node Menus

This node includes three menus: Segment, Date, and Time.


Segment

The node requires a customer segment, which places the customer in the specific segment into the journey.


Only pre-created segments can be selected in the menu. Segments can be created in the Assets section.


Both static and dynamic segments can be used in this node:

  • Static segments place customers within an initial segment based on the set qualification when the customer entered the node. Customers can be added or removed manually.

  • Dynamic segments place customers within an initial segment but can be modified based on variable qualifications. Customers can be managed by node triggers, actions, and conditions.


Date

The date indicates the date and time the customer should be added to the journey. Only the current date or future dates are available as options. Prior dates cannot be selected.


Time

The start time defaults to 12:00 am. Another time can be selected in the drop-down menu, which supports hour values.


When node preferences are applied, the Date and time trigger summary displays in the node.


Node Connection

Once the node is configured, the condition can be connected to another node to build a path along the journey. Connections are made by hovering the mouse pointer over the node, clicking the gray arrow, and dragging the arrow to the intended node.


Connections can be made with multiple nodes.


If the arrow is not retained on the node and displays a gray path, the selected condition is not supported for the intended node.


This node connection does not include configuration options.


Watch a video about Segments


Back to Section Menu



Recurring Time Trigger*

Node summary: A customer from a selected segment continues along the journey at a specific time on a recurring schedule.


Node Menus

This node includes five menus: Segment, Start Date, Start Time, Timezone, and Recurrence.


Segment

The node requires a customer segment, which places the customer in the specific segment. 


Only pre-created segments can be selected in the menu. Segments can be created in the Assets section.


Start Date

The start date indicates the first date in the series of occurrences a customer should be added to the journey. The start date defaults to the current date. An alternative date can also be selected in the date drop-down menu. Prior dates cannot be selected. 


End Date

An end date can be added to the node. When enabled, the node will stop placing customers from the selected segment into the journey. By default, the date is 1 day later. A future date can also be selected in the date drop-down menu. Prior dates cannot be selected. 


Start Time

The start time indicates the time the customer should be added to the journey. By default, the start time is 12:00 am. An alternate start time can be selected in the drop-down menu, which supports hour values. The selected time also applies as the start time for all additionally scheduled occurrences.


# Occurrences

By default, the number of occurrences field is not enabled, meaning the node will run indefinitely within the schedule. However, a specific number of occurrences can be set for the node. When enabled, the default number is 10 total occurrences. The number of occurrences can be entered directly in the number field. The box also includes up and down arrows that can adjust the number appropriately. The number field does not have a maximum limit.


Timezone

The timezone indicates the timezone that manages the start date and time. Currently all nodes are managed with the America/Denver timezone. 


Recurrence

The recurrence option indicates the recurring time period for the node. By default, the recurrence is set to daily.


Alternate recurrence options can be selected in the drop-down menu. Options include weekly, monthly, quarterly, or annually. Depending on the selected recurrence option, recurrence options will vary.


Daily Recurrence

The Daily recurrence option defaults to run the node every day. An alternative number of days can be entered directly in the number field. The box also includes up and down arrows that can adjust the number appropriately. The maximum value allowed for day entries is 31.


The daily recurrence can also be set to two other options: run every week day or run every weekend day.


Weekly Recurrence

The Weekly recurrence option defaults to run the node every week. An alternative number of days can be entered directly in the number field. The box also includes up and down arrows that can adjust the number appropriately. The number field does not have a maximum limit.


By default, all days of the week are selected. Days of the week can be deselected if a day is not preferred. At least one day of the week must be selected for the node to create a recurrence.


Monthly Recurrence

The Monthly recurrence option defaults to run the first day of every month. An alternative number of days and months can be entered directly in the number field. The box also includes up and down arrows that can adjust the number appropriately. The maximum value allowed for day entries is 31 and month entries is 12.


The monthly recurrence can also be set to run the first specific day of the week of every month. When enabled, the default is the first Monday of every month. Alternative options can be selected in the drop-down menus: 

  • The first drop-down menu includes options for first, second, third, fourth, fifth, and last.

  • The second drop-down menu includes all days of the week.


An alternative number of months can be entered directly in the number field. The box also includes up and down arrows that can adjust the number appropriately. The maximum value allowed for month entries is 12.


Quarterly Recurrence

The Quarterly recurrence defaults to run the first day of the quarter. An alternative number of days can be entered directly in the number field. The box also includes up and down arrows that can adjust the number appropriately. The maximum value allowed for day entries is 31.


Annually Recurrence

The Annually recurrence option defaults to run every year on January 1. An alternative month option can be selected in the drop-down menu. Additionally, an alternative date can be entered directly in the number field. The box also includes up and down arrows that can adjust the number appropriately. The maximum value allowed for month entries is 31.


The annual recurrence can also be set to run the first specific day in the first specific day of the week in a specific month. When enabled, the default is the first Monday in January. Alternative options can be selected in the drop-down menus:

  • The first drop-down menu includes options for first, second, third, fourth, fifth, and last.

  • The second drop-down menu includes all days of the week.

  • The third drop-down menu includes all months of the year.


When node preferences are applied, no summary data displays in the node.


Node Connection

Once the node is configured, the condition can be connected to another node to build a path along the journey. Connections are made by hovering the mouse pointer over the node, clicking the gray arrow, and dragging the arrow to the intended node.


Connections can be made with multiple nodes.


If the arrow is not retained on the node and displays a gray path, the selected condition is not supported for the intended node.


This node connection does not include configuration options.


Back to Section Menu



Segment Trigger*

Node summary: A customer is selected to be added to an associated journey based on specific trigger. 


Node Menus

This node includes one menu: Segment.


When node preferences are applied, the segment name displays in the node.


Segment

The node requires a customer segment, which places the customer in the specific segment. 


Only pre-created static segments can be selected in the menu. Static segments place customers within an initial segment and does not support any additional events. Segments can be created in the Assets section.


Note: Consider creating a segment nomenclature to help define which are dynamic vs static segments.


The node also requires one of three options:

  • Add all contacts on this segment now and that are added in the future (default option)

  • Add all from this segment now—customers can be added to the segment but are only placed in the journey after the journey is published

  • Add only contacts that enter this segment in the future—after a journey is published, customers added to the segment are automatically placed in the journey


Node Connection

Once the node is configured, the condition can be connected to another node to build a path along the journey. Connections are made by hovering the mouse pointer over the node, clicking the gray arrow, and dragging the arrow to the intended node.


Connections can be made with multiple nodes.


If the arrow is not retained on the node and displays a gray path, the selected condition is not supported for the intended node.


This node connection does not include configuration options.


Watch a video about Segments


Back to Section Menu



Web Form

Node summary: A customer receives and completes a web form using a pre-created template.


Node Menus

This node includes one menu: Web Form.


When node preferences are applied, the selected web form name displays in the node.


Web Form

The node requires a web form be created on an outside web page and connected to the account. The web form can be selected from the configured web forms in the assets panel. Once a customer fills out the form on the specified URL, they will enter the journey through this node.


Only pre-created web forms can be selected in the menu. Web forms can be created and edited in the Assets section.


Web Form Templates

Pre-created, published web forms can be selected in the menu. Web Forms can be created and edited in the Assets section.


Node Connection

Once the node is configured, the condition can be connected to another node to build a path along the journey. Connections are made by hovering the mouse pointer over the node, clicking the gray arrow, and dragging the arrow to the intended node.

Connections can be made with multiple nodes.

If the arrow is not retained on the node and displays a gray path, the selected condition is not supported for the intended node.

This node connection does not include configuration options.


Back to Section Menu



Abandoned Cart

Node summary: A customer is placed in an associated journey after a cart is created on your storefront, and it has been two hours since the cart was started and it hasn't been finalized. 


Node Menus

This node includes two menus: Select Location(s) and Select Market(s).


When node preferences are applied, no summary data displays in the node.


Select Location(s)

The node accepts a location if applicable to your account, which specifies that only customers from the selected location will be placed in the journey. By default, all locations are set for the location. 


An individual location can also be selected in the date drop-down menu. Only pre-created locations can be selected in the menu. Locations are most commonly created through transaction data and can be edited in the Assets section. 


Select Market(s)

A specific market can also be set for the node. A market is a grouping of stores, such as stores in the same city, state, or region. Only pre-created markets can be selected in the menu. Markets can be created as part of the onboarding process or at any time by submitting a support case.


Node Connection

Once the node is configured, the condition can be connected to another node to build a path along the journey. Connections are made by hovering the mouse pointer over the node, clicking the gray arrow, and dragging the arrow to the intended node.


Connections can be made with multiple nodes.


If the arrow is not retained on the node and displays a gray path, the selected condition is not supported for the intended node.


This node connection does not include configuration options.


Watch the following video to see an example using this trigger:




Back to Section Menu


Shopify Fulfillment

Node summary: A customer is placed in an associated journey after completing a step in your Shopify store order fulfillment process.


Node Menus

This node includes two menus: Select Location(s) and Select Market(s).


When node preferences are applied, no summary data displays in the node.


Select Location(s)

The node accepts a location if applicable to your account, which specifies that only customers from the selected location will be placed in the journey. By default, all locations are set for the location. 


An individual location can also be selected in the date drop-down menu. Only pre-created locations can be selected in the menu. Locations are most commonly created through transaction data and can be edited in the Assets section. 


Select Market(s)

A specific market can also be set for the node. A market is a grouping of stores, such as stores in the same city, state, or region. Only pre-created markets can be selected in the menu. Markets can be created as part of the onboarding process or at any time by submitting a support case.


Node Connection

Once the node is configured, the condition can be connected to another node to build a path along the journey. Connections are made by hovering the mouse pointer over the node, clicking the gray arrow, and dragging the arrow to the intended node.


Connections can be made with multiple nodes.


If the arrow is not retained on the node and displays a gray path, the selected condition is not supported for the intended node.


This node connection includes configuration options relating aShopify order:

  • Label Printed
  • Label Purchased
  • Ready for Pickup
  • Confirmed
  • In Transit
  • Out for Delivery
  • Delivered
  • Failure


Watch a video on Shopify Automation

Back to Section Menu


From Zapier

Node summary: A customer is sent to the Journey from Zapier (Zapier Integration must be configured).


**Only use a single "From Zapier" trigger per journey or else each customer will be added to the journey once for each "From Zapier" that appears in the Journey**


Node Menus

This node includes no menu configurations.



Node Connection

This node does not include connection options.


Watch a video about Zapier


Back to Section Menu