Workflow Programming

Workflow Programming

Grid Studio also provides Workflow Programming, a node-based system for building event-driven logic and system automation.

Workflows are used whenever the system needs to react to events, evaluate conditions, process structured data, and trigger actions across a project.

Objects used for workflow programming are created and organized in the Project Tree.

Unlike object-based data processing, workflows are not primarily designed for high-frequency real-time signal manipulation. Instead, they are used to coordinate logic, automation, and interaction between different systems.

Typical Workflow Logic

1

Event

A workflow begins with an event.

Events can originate from many different parts of the system, including user interaction, incoming protocols, internal object events, or external devices.

Typical examples include:

• Widget interactions such as buttons or sliders

• Areas in 3D space acting as trigger zones

• Incoming protocols such as OSC, UDP, or WebSockets

• Connected devices reporting status changes or feedback

• Timeline events

• Cue List triggers

• Calendar Scheduler events

• Macros

• State Machines

• Object, function, or parameter events

2

Logic Actions

The event is processed inside the workflow using node-based logic.

This logic can evaluate conditions, combine multiple inputs, branch behavior, and process structured data such as JSON, REST responses, or other complex datasets.

This makes workflows useful not only for automation, but also for interpreting and reacting to more complex information.

3

Device/Control Actions

Once the required logic has been evaluated, the workflow can trigger one or more actions.

These actions can control objects, change parameters, switch states, trigger other systems, send protocols, or interact with connected devices.

This allows Grid Studio not only to control external systems, but also to react to feedback and status changes coming from them.

4

System Reaction

The result of a workflow is a change in system behavior.

For example, a workflow may trigger a sequence of actions after a button press, react to a sensor event, process incoming protocol data, or coordinate multiple systems during runtime.