OBS flow configuration
Connect OBS first. The plugin's page provides connection controls and scene buttons; event-driven automation is configured in the flow editor.
Scenes, sources, and filters
- Add an event trigger, such as Scene Changed, to a flow.
- Add an action such as Set Scene, Source Visibility, or Filter Enabled.
- Set the scene, source, or filter names exactly as they appear in OBS. A source visibility action needs the scene containing that source.
- Connect the trigger's flow output to the action's Execute input. Use Success and Error to decide what should run afterward.
- Save the flow and run it.
Where an action exposes both an input and a property for a name, a connected, non-empty input overrides the property. Avoid having a scene-change flow keep switching between scenes in response to its own changes.
Streaming, recording, and audio
Use Stream or Record to control the corresponding OBS operation. Choose the intended operation in the node's properties before enabling the flow. Their state-change triggers let another part of the flow react to OBS's reported state.
Input Mute controls a named audio input; Input Mute Changed reacts when that input changes. Trigger Hotkey invokes an OBS hotkey by its internal name, not its keyboard shortcut.
Errors
OBS actions continue through Done even if the request fails. Route Success through an If before steps that depend on the change, and inspect Error when false. A connected socket does not guarantee that a scene, source, filter, or hotkey name is valid.
