Triggers
Learn about triggers that initiate value streams.
Last updated
Was this helpful?
Learn about triggers that initiate value streams.
Triggers are the elements that initiate value streams. You can use them to start a new process instance or to resume an existing one that was previously paused.
A number of commerce events are provided out-of-the-box, these are the CE events. Additionally, you can configure custom events for your tenant, which are then available in the list. CE events can only be used as starting triggers, while custom events can serve as both starting and intermediate triggers.

Make scenarios can serve as triggers for value streams. Select an existing scenario from the dropdown, click Go to scenarios to open it in Make, or click Create new scenario to create one in Make and add it as a trigger.

When multiple scenarios have similar names in Make, use a consistent naming convention so you can identify the correct one without opening each scenario.
Use this as a baseline:
Include the value stream name first, so related scenarios are grouped together.
Include the step purpose, so the scenario role is clear.
Include the trigger or key event, so the invocation context is visible.
Keep names stable and avoid generic names like Send email or Validation.
If you import or copy value streams, duplicated scenario names can temporarily appear. You can identify the correct scenario by checking its folder in Make, where scenarios are grouped by the related value stream.
You can also use Timer Events as triggers. A timer event provides a flexible mechanism to schedule and control the execution of a value stream. It supports a wide range of trigger configurations to meet diverse timing and scheduling requirements. Similar to custom events, you can use timer events both as starting triggers to initialize a process, and as wake-up triggers to resume a process between steps, when the process is waiting for some events to happen.

Last updated
Was this helpful?
Was this helpful?

