Trigger nodes explained

Triggers are building nodes that launch a workflow regardless of the type of the workflow (a customer workflow or non-customer scenario). The Triggers section contains two main types of triggers: scheduled and instant. Both types can be used in a customer workflow and business profile-oriented scenarios. Triggers can be also divided into customer-oriented and business-profile oriented.

Usage guidelines

  • A trigger is always the first step in the workflow.
  • You can use several triggers simultaneously (connect them to Merge paths node).
  • When you use several triggers at the time, they are linked with each other by OR dependency. It means only one activated trigger is enough to start the workflow.
  • The starting point of the workflow is tracked by default (you can switch it off). When a customer starts a workflow, this is marked on the list of activity on the customer’s profile.

Instant triggers


An instant trigger launches a workflow immediately after receiving information about the occurrence of an event in a touchpoint integrated with Synerise (a mobile app, website, point of sale, and so on). The group contains:

  • Client Event
  • Business Event
  • Data Changed

Scheduled triggers


Scheduled triggers launch a workflow on the chosen date and with the defined frequency. In specific cases, they can launch a workflow only once. These triggers can be used in customer workflows and business profile-oriented scenarios. The nodes of this category include:

  • Audience
  • Scheduled Run

Client triggers


Client triggers launch workflow when they detect occurrence of an event. As opposed to the Audience trigger node, client triggers work in the context of individual customers. The nodes of this category include:

  • Client Event
  • Data Changed
  • Audience

Business profile triggers


These triggers launch a workflow when an event occurrence free from customer context is detected. The nodes of this category include:

  • Business Event

Processing multiple triggers in a scenario


Remember that every scenario can contain more than one trigger, though, some of the elements can’t be joined. To prevent errors in the flow logic, we introduced a dynamic validation. If you add one type of the node, the next elements will be proposed in accordance with the logic of node combinations.

Contents


😕

We are sorry to hear that

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.

😉

Awesome!

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.