# Connection workflow nodes

> Read variables and feedback from a connection or run one of its actions from inside a workflow.

Use these nodes to read state from a connection or send a command through one. Choose a node Connection Variable : read a variable supplied by a connection Connection Action : run one action supplied by a connection Connection Feedback : read a true-or-false condition supplied by a connection Connection Variable Read a variable supplied by a connection. What you see in the editor Choose Connection , then choose Variable . The node shows the latest value beside its Value output. Connections Kind Label What it provides Output Value The current value of the selected connection variable. Example Select a connection variable that reports a device name, then connect Value to Display while building and testing the workflow. Connection Action Run one action supplied by a connection. What you see in the editor Choose Connection and Action . The action’s own options then appear on the node. Three triggers can all be enabled at once, independently: connecting an event to Event always runs the action when that event fires; Execute on startup additionally runs it once when the workflow starts; Execute on change additionally runs it whenever a connected option value changes. Use startup execution only when repeating the action after a restart is acceptable. Connections Kind Label What it provides Input event Event Runs the selected action. Input Execute on startup A true or false value that overrides the switch on the card. Input Execute on change A true or false value that overrides the switch on the card. Input Connection A connection to use instead of the one picked on the card, for example from a Connection-type variable. Input Action An action to run instead of the one picked on the card. Inputs One per action option A value for that option, overriding what's set on the card. Action option inputs Every option the selected action has gets its own input handle, labelled with the option's name, so the list changes with the connection and the action. An ATEM ME: Set Program input action, for example, has M/E and Input ; a Fairlight audio action has Input , Source , and Mix option . Plain text notes in an action's options have no handle. The same rules apply to every option: Leave a handle unconnected and the node uses the value set on the card. Connect a value and the field on the card is replaced by the live value coming in. That value wins over anything set on the card. The value has to be one the option accepts, such as a valid input number or one of the choices in a dropdown. If it isn't, the node shows an error for that option instead of running the action. With Execute on change on, a new value on any connected option runs the action again. To see which values an option expects, set it on the card first and look at what the dropdown or field offers. If the action fails, the node reports it through its own error state, the same border indicator described in Read what a node's border is telling you , not through a separate output event. Example Connect a Button event to Event and select a non-production device action to run when the button is pressed. Connection Feedback Read a true-or-false condition supplied by a connection. What you see in the editor Choose Connection and Feedback . The feedback’s options appear after you make the selection. The node shows the current result beside State while the workflow is running. Connections Kind Label What it provides Output State The current feedback result, as true or false. State is the only output, and it's always true or false. A connection can also offer feedbacks that report something else, such as a value, an image, or a gauge level, and these still appear in the Feedback list. The workflow node only passes on the true-or-false part, so with a feedback that reports only a value, State stays false. To use a value in a workflow, read it with a Connection Variable node instead, if the connection provides it as a variable. Example Select a feedback that reports whether an input is on Program, then connect State to Logic Operation or Display .