Twitch Integration

Comes with strAImer: this module is installed together with the app, so there is nothing to download. It is listed under Module Catalog → Built-in.

What this page is

The page connects a Twitch account to the app — as its description puts it, "Configure Twitch integration to receive chat messages, rewards, and manage your channel." It exists in two variants: the streamer's own channel, and a separate account the bot writes from.

Count Bits as donations sits on the channel tab. Cheers also arrive as a donation, so Bits move fundraising goals, auction bids and stream totals — at the rate from Settings → Currency Rates. Turn it off to keep Bits apart from money; the Bits counter stays either way. It is what makes a cheer move a fundraising goal or place an auction bid at all; with it off, Bits stay a counter of their own. Out of the box a bit is worth one US cent, which is what Twitch pays for one, converted into your base currency; a rate of your own in Settings → Currency Rates replaces that default.

Flipping the switch restarts the Twitch connection: the chat and the event stream reconnect, which takes a few seconds, and chat messages or events from those seconds can be missed. Set it before you go live rather than in the middle of a stream.

How to set it up

1. Open Connections → Channels and open the Twitch page. Its header reads Streamer Account (Reads events, EventSub).
2. Connection Status shows one of five wordings. The hint beside it names what is being asked for: "Requires maximum permissions (read chat, manage stream, polls, predictions, and channel points)."
3. Press Authorize via Browser. The page has one button and no field for a token: sign-in opens in your usual browser and finishes there.
4. The browser goes straight to Twitch's own confirmation page, with the code already filled in. Sign in to Twitch there if it asks, confirm the code and allow the permissions. The result is reported by Twitch itself, not by a strAImer page, so there is no page saying "Authorization successful!" at the end. You can close the browser tab afterwards.
5. While you are in the browser, the module page says "Finish signing in in the browser window — this page will update on its own." After two minutes it changes to "Still waiting for the browser. Finish signing in there — this page will update on its own. Nothing is lost if it takes a while." Do not press the button again while that sign-in is open: a new press starts a fresh sign-in and the one in the browser no longer counts. After thirty minutes the page gives up: "Sign-in did not finish. The browser window was closed or the request was declined — press the button to try again." Declining on Twitch looks the same from here: the page waits until that limit.
6. When the sign-in lands, the module page reports Twitch configuration successfully saved! and closes itself a moment later. Account Name (login) now shows the connected login; the field is read-only.
7. Granted permissions appears: "Which features work with the current token". Every feature is ticked or crossed, twelve lines on the channel tab: Read and send chat messages, New follower events, Paid subscription events, Bits events, Channel points rewards, Hype Train events, Channel goal events, Polls, Predictions, Change stream title and category, Create clips, Moderation: ban and delete messages.
8. If anything is crossed, a warning shows: "Some permissions are missing — related features will not work. Re-authorize to grant them." The Re-authorize button beside it starts the same browser sign-in, and that is what adds the missing rights.
9. The arrow at the top left, Back, leaves the page.

What the five status wordings mean

• Connected as {username} — green. The account is saved and neither Twitch nor the module has refused it. That is what it certifies: the sign-in is good. It is not a live test of whether events are flowing this second.
• Connecting... — yellow, with the account name still shown. The module is bringing the connection up: right after the app starts, and whenever either half of it, the chat or the event stream, has dropped. Both come back by themselves, so this one usually turns green within seconds.
• Sign in again to reconnect — yellow. The account is still here and its name is still shown below, because you need to know which account to repair, but Twitch has refused the saved access and will not renew it in the background. Nothing arrives from the channel until you sign in again, and signing in again is the only repair; there is no button that refreshes it from the outside.
• Connection error — red. The account is fine and the connection is not: the event stream dropped, or the module could not finish setting it up. The module retries by itself, so this one often clears without you touching anything.
• Disconnected — red, and the only one of the five that hides the Account Name (login) row, because there is no account saved on this page yet. That is what a fresh install shows.

The badge is live: it changes while the page is open, so there is no need to leave and come back to see a new wording.

The bot account

The same page under Connections → Bots is headed Bot Account (Sends replies to chat), and its hint is shorter: "Requires permissions to read and send messages in chat." The sign-in is the same one button, Authorize via Browser: sign in there under the account the bot should write from, not your own. Its Granted permissions list is one line long, Read and send chat messages, because the bot only writes to chat. Bans and message deletion go through the streamer account, which is why Moderation: ban and delete messages sits on the channel tab.

The two accounts are judged separately, and the bot never says Connection error. A bot sign-in Twitch has refused does not drag the streamer's own connection into Sign in again to reconnect with it.

If the browser reports an error

Instead of the Twitch page the browser may show Authorization Error with "Failed to exchange authorization code for tokens: {error}". That means the sign-in could not even start, most often because Twitch could not be reached. The account stays as it was; press Authorize via Browser again.

What it cannot do

• There is nowhere to paste a token, an access key or a refresh key. Authorize via Browser is the only way in, and it is also how an expired sign-in is renewed.
• Account Name (login) cannot be typed into. To connect a different account, sign in as that account.
• Permissions cannot be picked one by one. The tick list only reports what the current sign-in carries; Re-authorize hands over the whole set again.
• There are no Client ID and Client Secret fields, and none are needed: the sign-in goes through the strAImer app itself.
• The page has no Save button: everything is stored at the end of the browser sign-in. The Count Bits as donations switch is saved the moment you flip it.
• The page neither disconnects the account nor deletes the connection, and it does not turn the module off.
• The streamer account and the bot account are set up separately: one sign-in does not fill in the other.