Twitch destination

The Twitch destination uses the Helix API to run Twitch actions from event rules and Control board buttons. It uses the Twitch account selected on the destination as the sending account. Register and sign in to accounts under Connections > Accounts.

Set up

1. Add and sign in to the Twitch accounts you need. A chat action uses a signed-in account (for example a bot) as the sender and any registered account as its target channel. The target does not need a sign-in: add it as a Read-only account with its channel login, or give a sign-in account a channel login. Multiple target channels can be configured independently.
2. In each account’s Sign-in settings, enable the required Destination action permissions, then sign in again to grant them.
3. Add a Twitch destination, choose its sending account, and test the connection.
4. Add an action to a rule or Control board button and choose the Twitch destination and action.

Actions

Action	Required permission(s)	Notes
Send chat message	user:write:chat	Select the target channel, then enter a message. The signed-in sender must be allowed to chat there.
Create prediction	channel:manage:predictions	The destination account must be the selected broadcaster. Provide a title, 2–10 outcomes, and a 30–1800 second window.
End prediction	channel:read:predictions, channel:manage:predictions	Locks, resolves, or cancels the active prediction for the selected broadcaster.
Send Helix API request	Depends on the operation	Runs a configured request against the Helix API using the destination account.

Chat and prediction actions select one broadcaster; add multiple actions to send to multiple channels. Messages, prediction titles, outcomes, and winning outcomes support event templates, such as ``.

Channel management actions

These actions show a form for their options. Choose the Channel to act on (any registered Twitch account, including read-only ones); the destination’s sending account must be that channel’s broadcaster, or a moderator where noted. User fields take a Twitch login, so templates such as `` work; Stream Pulse looks up the user ID. Enable the listed permission in the sending account’s Destination action permissions and sign in again.

Category	Actions	Sender	Permission(s)
Ads	Start commercial, snooze next ad	Broadcaster	channel:edit:commercial, channel:manage:ads
Clips	Create clip	Any	clips:edit
Chat	Announcement, shoutout, update chat settings, update your chat color	Moderator (color: any)	moderator:manage:announcements, moderator:manage:shoutouts, moderator:manage:chat_settings, user:manage:chat_color
Moderation	Ban or time out, unban, warn, delete messages, block term, Shield Mode	Moderator	moderator:manage:banned_users, moderator:manage:warnings, moderator:manage:chat_messages, moderator:manage:blocked_terms, moderator:manage:shield_mode
Moderation	Add or remove moderators and VIPs	Broadcaster	channel:manage:moderators, channel:manage:vips
Polls	Create poll, end poll (the active poll when no ID is given)	Broadcaster	channel:manage:polls
Raids	Start raid, cancel raid	Broadcaster	channel:manage:raids
Guest Star	Create or end session, send or remove an invite (Twitch beta)	Broadcaster	channel:manage:guest_star

Update chat settings only changes the settings you set to Turn on or Turn off. Delete chat messages clears the whole chat when the message ID is empty; use `` to delete the triggering message.

The action picker is backed by the Twitch API operation catalog. Operations marked not implemented are listed with their descriptions and official documentation links, but are disabled until Stream Pulse has a safe, operation-specific implementation. The catalog is based on the Twitch API reference.

Send Helix API request is the advanced escape hatch for other Helix operations. Set the HTTP method, a path relative to /helix (for example /channels), query parameters and request body as JSON, and the exact OAuth scopes required by the endpoint. The destination account must have those scopes; add them under its Additional OAuth scopes sign-in settings and sign in again. Requests are restricted to Twitch’s Helix API host and base path. Successful response bodies are available in the event run’s response details.

Skip this action when the broadcaster is offline checks Twitch before sending or changing a prediction. If the channel is offline, the action is recorded as skipped and later actions in the rule continue. Otherwise Twitch API errors are shown in Activity; requests are not automatically retried.

Prediction actions operate on the selected broadcaster’s active prediction. Create the prediction from a match-start event, then resolve or cancel it from a later event. The configured winning outcome must match one of the active prediction’s outcome titles.