Creating automations from stream events

Automations let an event trigger an action while you are live — for example, showing a message when a game event arrives or sending a notification when a milestone is reached.

The basic flow

1. Publish an event from Stream Deck, Streamer.bot, the Local Agent or your own integration.
2. Match its type in Integrations → Automations.
3. Add the action and any cooldown you need.
4. Test the rule with a harmless sample event before using it on air.

Use a stable event type such as game.kill, game.round_win, game.objective or game.custom. Put changing details — player, score or message — in the event context rather than creating a new rule for every variation.

Keep automations audience-safe

Add a cooldown to noisy events and keep messages short enough for the overlay. Never place API tokens in an event's message or context. If an action calls an external service, give it only the permissions it needs and rotate the token if it is ever exposed.

If an event is visible in the event log but the automation does not run, check the event type spelling, workspace, enabled state and cooldown window.