> 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/trigger.md).

# Trigger

Use Timeline Triggers to fire Workflow Events at specific points in time and connect them to Actions through the Inspector or Node Editor.

A **Trigger** represents a single point in time.

It provides one Workflow Event that is fired when the Timeline is actively playing and the Playhead passes over the Trigger position.

<figure><img src="https://1761958297-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDcGqBEYUYkl2mQzGbOue%2Fuploads%2F8RLKuq5OoPlJgluTSwBk%2FnRQclcpuGP.gif?alt=media&amp;token=ce0c6859-d774-4761-90af-5cbe20e73dc5" alt=""><figcaption></figcaption></figure>

Manually moving, seeking, or jumping the Playhead across the Trigger does **not** fire the Event.

***

## Events

### Trigger

The Event is fired when the Timeline is actively playing and the Playhead passes over the Trigger position.

Manually moving, seeking, or jumping the Playhead to or across the Trigger does **not** fire the Event.

***

## Workflow

A Timeline Trigger has its own **Workflow**, which defines what should happen when the Trigger Event is fired.

The Workflow can be created and edited in different ways:

* directly in the **Inspector**
* visually in the **Node Editor**
* automatically when an object from the **Project Tree** is dragged onto the Trigger Layer

### Creating a Trigger with a Preconfigured Workflow

A Trigger can also be created together with a matching Workflow Action in a single step.

Drag an object from the **Project Tree** directly onto the Trigger Layer.

For example, dragging an OSC object onto the Trigger Layer automatically:

1. creates a new Trigger at the drop position
2. creates the corresponding Action in the Trigger's Workflow
3. connects the Trigger Event to that Action

<figure><img src="https://1761958297-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDcGqBEYUYkl2mQzGbOue%2Fuploads%2FEgmNXRxwrzX6u1tkiDS2%2FPowerToys_uYurpYFRhI.gif?alt=media&amp;token=d92ce56a-fea8-4153-b85a-8210d52386a0" alt=""><figcaption></figcaption></figure>

This provides a fast way to create both the Trigger and its Workflow logic at the same time.

### Inspector Workflow

In the Inspector, the Workflow is represented as a vertical list of Actions connected to the Trigger Event.

<figure><img src="https://1761958297-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDcGqBEYUYkl2mQzGbOue%2Fuploads%2FiuDSZ6zLoWvGCPMgGvKB%2FPowerToys_GLMKYVEb4l.gif?alt=media&amp;token=46e523f0-b853-4171-b7b1-a78bc0a1b5f7" alt=""><figcaption></figcaption></figure>

For example, to send an OSC message when the Trigger fires, drag the OSC object from the **Project Tree** onto the Trigger Event in the Inspector.

Grid Studio automatically:

1. creates the corresponding Action in the Workflow
2. connects the Action to the Trigger 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.

<figure><img src="https://1761958297-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDcGqBEYUYkl2mQzGbOue%2Fuploads%2FEQLxEHGbIG8Vu9wbFHRi%2FGrid_Studio_G7DuoAmoQk.gif?alt=media&amp;token=350a8396-8950-4cda-bd11-8bcc5246a78f" alt=""><figcaption></figcaption></figure>

Objects such as an OSC object can be dragged directly from the Project Tree into the Workflow and connected manually to the Trigger Event.
