Triggers
Triggers are event listeners that allow Talos to start or resume a workflow based on an external event. Instead of running a process on a fixed schedule or manually, you can configure Talos to "wait" for a specific condition to be met, such as a file being created or an email arriving.
How Triggers are Used
Triggers are used in two primary scenarios within Talos:
1. To Start a Workflow (Jobs)
You can configure a Job to start an entire automation automatically whenever a trigger is activated. This is the standard way to create "event-driven" automations that react to the outside world.
2. To Resume a Workflow (Wait for Trigger)
Within a workflow, you can use the Wait for Trigger action. This pauses the execution of the workflow at that specific step. The workflow will only resume and move to the next action once the trigger event occurs.
Common Properties
When you configure a trigger, you will typically define these basic properties:
| Property | Description |
|---|---|
| Name | A friendly name to identify the trigger in your project. |
| Description | A brief explanation of what this trigger is monitoring. |
| Timeout | The maximum time (in milliseconds) the trigger will wait. If the event doesn't happen within this time, the trigger will automatically activate anyway. Set to -1 to wait indefinitely. |
Core Concepts
- Active Monitoring: Once started, Talos monitors the resource (file, keyboard, or email) in the background.
- Activation: This is the moment the event happens. When a trigger is activated, it stops monitoring and signals Talos to either start the Job or resume the paused Action.