Trigger nodes explained

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

Usage guidelines

  • A trigger is always the first step in the automation.
  • 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 automation.
  • The starting point of the automation is tracked by default (you can switch it off). When a customer starts an automation, this is marked on the list of activity on the client card.

Instant triggers


An instant trigger launches an automation 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 Profile Event (available soon)
  • Client Data Changed
  • Incoming Webhook (available soon)

Scheduled triggers


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

  • Audience
  • Incoming Webhook (available soon)

Client triggers


Client triggers launch automation when they detect occurrence of 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
  • Client Data Changed
  • Audience

Business profile triggers


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

  • Incoming Webhook (available soon)
  • Business Profile Event (available soon)

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