Streaming Hub 0.1

Twitch

Use Twitch EventSub, chat and channel operations in automations.

Alpha

Verified withStreaming Hub: 0.1.3.0Plugins: Twitch 1.1.0

Capabilities

Receive supported stream, subscription, raid, moderation, reward, poll and prediction events.
Use supported chat and Twitch API actions.
Expose normalized event fields to automation steps.

Integration signals can start automations. Integration actions are added as steps.

Requirements

A Twitch account with access to the target channel.
Authorization scopes required by the selected signals and actions.
A working network connection to Twitch services.

Connect

Open Services → Twitch, or double-click Twitch in the bottom status bar.
Select Configure Signals, Actions and Scopes. Enable only the signals and actions you intend to use, then select Apply. This determines which OAuth scopes Streaming Hub requests.

Twitch Signals, Actions and Scopes window with signal checkboxes and a summary of required OAuth scopes — Choose the capabilities you need before authorization. The scope summary at the bottom updates when you apply the selection.

Choose the Chat Account role. Use Broadcaster to send chat messages as the channel account, or Bot to use a separately connected bot account.
Select Connect Broadcaster. Streaming Hub opens Twitch in your default browser; sign in and approve the requested scopes.
Return to Streaming Hub after the completion page appears. If you selected Bot for chat, select Connect Bot and sign in to the separate account.
Select Save, then test a Twitch signal or Send Message action and inspect Logs.

Twitch project settings showing account roles, connection buttons and diagnostics — The settings page shows the connected accounts and diagnostics. In this example the account is connected, but a missing-scope warning remains for one EventSub subscription.

The Streaming Hub server handles only the Broadcaster authorization-code and token-refresh exchanges. Helix API calls, EventSub, chat and token validation connect directly from the desktop application to Twitch.

Verify the connection

The Twitch service indicator shows connected and the log reports successful EventSub subscription creation for enabled event types. A connected account can still show a missing-scope warning; enable the required capability and reconnect to grant its scope.

Limitations

Twitch permissions are scope-specific. An account can connect successfully while an action or subscription remains unavailable because its required scope was not granted.

Troubleshooting

Check the service status and filter the Log panel by the integration source. Reopen the integration settings to check connection details, enabled options and required external-service permissions.