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 workspace-oriented scenarios. Triggers can be also divided into customer-oriented and workspace-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
ORdependency. 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 profile starts a workflow, this is marked on the list of activity on their profile’s card.
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:
- Profile 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 workspace-oriented scenarios. The nodes of this category include:
- Audience
- Scheduled Run
Profile triggers
Profile triggers launch workflow when they detect occurrence of an event. As opposed to the Audience trigger node, profile triggers work in the context of individual customers. The nodes of this category include:
- Profile Event
- Data Changed
- Audience
Workspace 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.
