Use workflows to automate behavior that does not begin with a button press, or to add advanced logic when a direct button action is not enough. This reference explains how to choose a node, what appears on its card, what each visible connection provides, and where the node is useful.
Understand the node card#
Nodes appear in the editor under Connection, Workflow, Internal, Position, API, and Utility. Search by the name shown in this reference, then add the node to the canvas.
The left side of a node receives values or events. The right side provides values or emits events. Event connections represent something that happened, such as a button press or a timer finishing. Value connections carry state, such as a label, number, or true-or-false condition.
Many nodes show configuration directly on their card. When a matching value input is connected, the connected value can replace the value entered on the card. Dynamic nodes add connections after you choose an action, feedback, variable, endpoint, case, or named input.
Choose a category#
- Connection nodes: read connection variables and feedback, or run connection actions.
- Workflow nodes: create, read, write, and route workflow values.
- Internal nodes: use actions and feedback provided by Buttons.
- Position nodes: react to NFC reads from assigned surfaces.
- API nodes: exchange data with OSC, HTTP, TCP, UDP, and WebSocket systems.
- Utility nodes: transform values, control events, schedule work, and inspect state.
Experimental nodes#
TCP Server, TCP Client, UDP Receiver, UDP Sender, WebSocket Client, and WebSocket Server are hidden unless experimental workflow nodes are enabled. Treat their configuration and support status as subject to change.
