> For the complete documentation index, see [llms.txt](https://stage-precision.gitbook.io/grid/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stage-precision.gitbook.io/grid/timeline/layer-types/trigger-layer/timed-trigger.md).
# Timed Trigger
Use Timed Triggers to generate Started, Ended, and Seek Workflow Events across a defined time range in a Timeline.
A **Timed Trigger** defines a time range instead of a single point.
Its Block therefore has both a start position and a **Length**.
***
## Events
A Timed Trigger provides three Workflow Events:
* **Started**
* **Ended**
* **Seek**
### Started
**Started** fires when the Timeline is playing and the Playhead passes normally over the beginning of the Timed Trigger.
Jumping or seeking across the start does not fire the Started Event.
### Ended
**Ended** fires when the Timeline is playing and the Playhead passes normally over the end of the Timed Trigger.
Jumping or seeking across the end does not fire the Ended Event.
### Seek
**Seek** fires when the Timeline jumps or seeks into the time range of the Timed Trigger.
It does not fire continuously while the Timeline plays normally through the Block.
The Event can fire repeatedly. For example, if Timeline navigation repeatedly jumps into the same Timed Trigger, the Seek Event is generated each time.
***
## Workflow
A Timed Trigger has its own **Workflow**, which defines what should happen when one of its Events is fired.
The Workflow can be edited in two different ways:
* directly in the **Inspector**
* visually in the **Node Editor**
Both interfaces edit the exact same underlying Workflow.
### Inspector Workflow
In the Inspector, the Workflow is represented as a vertical list of Actions connected to the Timed Trigger Events.
Actions can be added directly to **Started**, **Ended**, or **Seek**.
For example, dragging an OSC object from the **Project Tree** onto one of the Events automatically:
1. creates the corresponding Action in the Workflow
2. connects the Action to the selected Event
3. exposes optional Action parameters directly in the Inspector
### Node Editor
The same Workflow can also be opened in the **Node Editor**.
Instead of the vertical Action list, the Workflow is shown as a node graph.
Objects can be dragged directly from the **Project Tree** into the Workflow and their Actions can be connected manually to **Started**, **Ended**, or **Seek**.
