> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/value-stream-modeller/value-stream-designer/process-components/triggers.md).
# Triggers
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.
## Events
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.
Event trigger configuration (select event type)
## Make scenarios as 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.
Scenario trigger configuration
### Scenario naming best practices
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`.
{% hint style="info" %}
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.
{% endhint %}
## Timer Events
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.
Timer event configuration for scheduling and wake-up triggers
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://developer.emporix.io/value-stream-modeller/value-stream-designer/process-components/triggers.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.