Event Emulator
Open System > Event Emulator to send a synthetic event into GRiMbot's EventSub notification handler.
Supported events
| Event | Test fields |
|---|---|
| New follower | None |
| New subscriber | Sub tier |
| Resub / sub streak share | Sub tier, cumulative months, streak months, message |
| Gift subs | Gift count, sub tier |
| Bits cheer | Bits, message |
| Incoming Raid | Raid viewers |
| Watch streak share | Watch streak, points awarded, optional message |
First Chat Message and Channel point redemption events are not available. Send a real Chat Message or make a real Twitch redemption to test those paths.
Actor and permissions
Every synthetic event uses the Twitch identity from the current bot or broadcaster chat token. The token must be present, valid, and resolvable to a Twitch user. If GRiMbot cannot resolve it, Fire event remains unavailable.
The emulator requires a GRiMbOS administrator session. It does not ask Twitch to deliver the event and does not need the event's live EventSub scope to build the synthetic notification.
Fire a test
- Choose Event.
- Fill in the event fields.
- Stop if the channel is live and the resulting output should not reach viewers.
- Click Fire event.
- Read the result message.
- Check the expected Event Alert, Actions, media, chat output, TTS, statistics, and streak behavior.
The request is committed to the database after the EventSub handler completes. Configured downstream work may continue in the background.
Live output warning: A synthetic event can show in OBS, play clips, speak TTS, post a Chat Message, update statistics, and run streak rules. Use it before the Stream Session unless that output is intentional.
What this test proves
Event Emulator checks GRiMbot's handling after an EventSub-shaped notification reaches the application. It can expose errors in event parsing, persistence, Event Alerts, Actions, and connected output systems.
It does not contact Twitch EventSub. It does not prove that Twitch accepted the subscription, granted the required scope, can reach the selected transport, or will deliver a real event.
Use a real Twitch event to verify Twitch delivery. Check System > System Status and System > Connection Status first.
Failure handling
Click Refresh after changing the bot or broadcaster authorization. If the actor remains unavailable, re-authorize the applicable account in System > System Status.
Invalid numeric text, an unsupported event, or a failed handler returns an error and does not report success. Correct the field and fire the event again. If the event succeeds but one output is missing, test that output separately. For card and Action testing with sample variables, see Event Alerts.