YouTube 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 YouTube channel to the app — as its description puts it, "Configure YouTube integration to receive chat messages and manage broadcasts." It exists in two variants: the channel itself, and a separate account the bot answers from.

How to set it up

1. Open Connections → Channels and open the YouTube page. Its header reads YouTube Channel (Reads events, broadcast).
2. Connection Status shows where you stand: Disconnected while no channel is connected, Connected as {username} once it is in place, yellow Sign in again when YouTube stopped accepting your sign-in, and red Google rejected the app keys in the rare case described below. The hint beside it names what is being asked for: "Requires authorization to check active broadcasts and send messages to YouTube chat."
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 the Google account that owns the channel and agree to the permissions. Leave every checkbox ticked. Google lists its permissions one by one and lets you untick them, and unticking one is the single most common reason YouTube ends up connected and silent: without the permission to see your broadcasts the app never learns that you are live, and a chat it cannot find is a chat it cannot read. Since 0.9.2 the app refuses such a sign-in and says so on that page; before it, the connection simply went green and nothing arrived. On success the browser page says Authorization successful! — "Account {username} has been successfully connected to YouTube", and below, "You can close this window. It will close automatically in a few seconds." Meanwhile the module page says "Finish signing in in the browser window — this page will update on its own.", after two minutes "Still waiting for the browser…", and after fifteen minutes it gives up with "Sign-in did not finish. The browser window was closed or the request was declined — press the button to try again."
5. The module page reports YouTube configuration successfully saved! and closes itself a moment later. Account Name (login) now shows the connected channel; the field is read-only.
6. Chat arrives together with a broadcast: the module reads the live chat of a broadcast that is running. With nothing live there is nothing to read. A public broadcast is picked up within a minute; an unlisted one can take up to half an hour, because it is not shown on the channel page and the app has to ask Google about it — rarely, to stay inside a request limit shared by everyone using strAImer. Pressing Authorize via Browser finds it at once. Whether the chat of a running stream has actually started shows on the YouTube badge under Connections → Channels, not on this page: the guide "Signing in to platforms", section "YouTube: chat arrives with the broadcast", says what each badge means.
7. If the sign-in stops working later, the badge turns yellow, Sign in again, and the channel name stays on the page. Press Authorize via Browser again: the same button renews it. Disconnected never means an expired sign-in, only that no channel is connected at all.
8. The arrow at the top left, Back, leaves the page.

The bot account

The same page under Connections → Bots is headed YouTube Bot Account (Sends replies to chat), and it works differently from the channel page above: one button, not two.

1. Press Connect the bot. A window opens inside the app: "sign in to the bot's Google account, then pick the YouTube channel it writes as. One account can hold several channels, and the app cannot tell which one you mean."
2. Sign in as the account the bot should answer from — not the channel's own account.
3. Pick the channel on the page that follows. That choice is what viewers will see as the author of the bot's messages.

Once it is connected the button changes to Sign in again or change the channel and the line under it explains why the sign-in exists at all: "The bot writes the way a browser does, so its replies and moderation do not spend the shared YouTube request limit." Press the same button to move the bot to another channel of the same account.

Make the bot a moderator of your channel. Without it YouTube refuses bans, time-outs and message deletion, no matter what the app does — moderation is a right the platform grants, not a setting here.

If the saved sign-in stops working, the page says so: "The saved sign-in stopped working, so the bot is not writing. Press the button to sign in again." Sign-ins do expire — this is the normal way to renew one.

If your own sign-in stops working, the stream is still read. The status reads Sign in again, and the page explains what stops: "YouTube no longer accepts your sign-in. The app still finds your public streams and reads their chat, but until you sign in again it cannot send messages as you or find streams that are visible only by link, and it can moderate the chat only through the bot account." This works only when the app has already identified your channel. If it has not, the page says it cannot find your stream, and signing in again before you go live is the only way.

Signing the bot in is not an optimisation — without it the app stays silent on YouTube. This is the part worth reading twice. Timers, command replies and the AI agent are automatic messages, and an automatic message with no bot sign-in behind it is not sent at all: the reason goes to the log console and nowhere else. Your own messages, typed by hand into the chat tile, are the exception — those go out whether or not a bot is set up, as long as a broadcast is live.

When the sign-in exists but stops working, the message is not dropped. It goes out through the official interface under your own channel's name, so viewers see it from you rather than from the bot. It is a deliberate stopgap: silence would mean timers, command replies and the agent all going quiet. The app writes a warning to the log every time, so a bot suddenly writing under your name is a sign its sign-in needs renewing.

Both of those need a broadcast that is actually live. With nothing streaming there is no chat to write into, and the message is refused for that reason instead.

If the page says "Google rejected the app keys"

This red badge is a different thing from an expired sign-in: Google no longer accepts the keys the app itself signs in with, and signing in again does not help. The page explains it with a code: "Google no longer accepts the keys strAImer signs in with (code: {code}). Signing in again will not help until strAImer is updated: update it and sign in again. If it is already up to date, write to us in Help & Feedback → Contact." So: update the app, then press Authorize via Browser; if the app is already on the latest version, write through Help & Feedback → Contact and quote the code.

Until then a public stream is still found and its chat is still read, as long as the app already knows your channel. Sending messages as you, streams visible only by link, and moderation other than through the bot do not work.

Super Chats, stickers and memberships

They arrive only during a live broadcast, from the chat the module is reading.

• Super Chats and Super Stickers come in as donations, in the currency the viewer paid in, and are converted into your base currency like any other donation. In the lists that choose which donations count, such as Count donations from on a fundraising goal, they are the source YouTube Super Chat: if a goal ignores Super Chats, check that this source is ticked there.
• If the app cannot recognise the currency written on a Super Chat, the amount arrives with an unknown currency, the log console says "Superchat currency not recognised", and a fundraising goal cannot convert it, so it does not move the goal.
• Memberships, including gifted ones, come in as subscriptions, not as donations, so they do not move a money goal.

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 channel, sign in with the account that owns it.
• The page shows no per-feature permission list — YouTube hands over its set at sign-in and the page reports only whether the account is connected.
• App keys that Google rejected cannot be replaced on this page: there are no fields for them.
• There are no Google Client ID and Google Client Secret fields — as the module puts it, "authorization goes through the strAImer app itself, no keys needed".
• The page has no Save button: everything is stored at the end of the browser sign-in.
• A broadcast cannot be picked here, and nothing on the page starts one. The page has no field for a broadcast address or a video link.
• The page neither disconnects the account nor deletes the connection, and it does not turn the module off.
• The channel and the bot account are set up separately: one sign-in does not fill in the other, and they use different windows — the channel signs in through the browser, the bot inside the app.
• The bot's channel cannot be typed in. It is picked from the list the sign-in window shows, and only channels of the account you signed in with are on it.
• Nothing on the page warns that automatic messages are being refused. The channel badge stays green: it reports the channel connection, not the bot's. Only the log console says why YouTube went quiet.