Twitch Integration

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.

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 four 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. Sign in to Twitch in the browser and agree to the permissions. On success the browser page says Authorization successful! — "Account {username} has been successfully connected to strAImer", and below, "You can close this window. It will close automatically in a few seconds."
5. 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.
6. Granted permissions appears — "Which features work with the current token". Every feature is ticked or crossed: Read and send chat messages, Channel points rewards, Paid subscription events, Change stream title and category, Create clips, Polls, Predictions, Manage ads.
7. 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.
8. The arrow at the top left, Back, leaves the page.

What the four 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.
• 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 four 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 read when the page opens, so a wording that changed while you sat on the page appears after you leave with Back and open it again.

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 three lines long: Read and send chat messages, Moderation: ban and delete messages, Chat announcements.

The two accounts are judged separately, and the bot reports only three of the four wordings — it 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 success page Twitch may return Authorization Error — "Failed to exchange authorization code for tokens: {error}". 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 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.