Signals

When to use a signal

Create a signal when an automation must react to a manual command, time condition, data threshold, or event supplied by an integration.

How it works

A signal defines its source and matching settings. When a matching event is received, Streaming Hub creates an execution context and attempts to start the associated automation.

Runtime policies such as cooldown and concurrency are evaluated before the sequence runs.

Signal sources

• Manual test or trigger.
• Interval timer or scheduled moment.
• Threshold over a runtime value.
• Event supplied by a plugin, such as Twitch, OBS, YouTube, DonationAlerts or Stream Deck.

Signal data

A signal may add structured fields to the execution context. Steps can read these fields by path. Available fields depend on the signal type and the received event.

Test data

Use signal test data to verify a sequence without waiting for an external event. Test data should match the shape expected from the real signal.

Limitations

Signal availability and fields depend on installed plugin versions. Public Alpha versions may change field names or validation behavior.