Signals

A signal defines the event that can start an automation. Core listens for enabled project signals even when the Editor is closed.

Configure a signal

Select its type and inspect its declared settings and event fields. Core signals include timers, scheduled moments, thresholds, Windows session events and global keyboard shortcuts. Integration plugins provide their own signals. Use Test to start a controlled test of the selected signal; a manual test is separate from the signal type.

Filters narrow which events qualify. Signal test data creates a controlled test event; it does not create a real donation, redeem a reward or change an external service.

Test and enable

Use Test a signal to inspect representative data. Save the automation definition first, then enable live handling when it behaves correctly. Automation and folder concurrency can still queue, delay or reject a qualifying event.

Use the installed Encyclopedia for exact field names and contracts.