By default, streamion.bot posts in your chat under its standard streamion.bot chat identity. The Custom Bot Pro feature replaces this default identity with a Twitch account of your own: streamion.bot continues to apply the same bot logic, but messages appear under the connected account. The feature is typically used when chat messages should appear under a name controlled by the broadcaster, for example @yournamebot instead of @streamionbot.

The feature page lives at /pro/custom-bot. Only the workspace Owner has access. Connecting a Twitch account affects the entire workspace, and the OAuth flow needs the broadcaster's session to attribute the action correctly.

Prerequisites

Two requirements must be met:

• The pro.custom-bot entitlement on your workspace. If the entitlement is missing, the page displays a Pro required card with a link back to the Pro overview, and the Connect button is hidden.
• A separate Twitch account for the bot. Twitch does not allow the same account to act as both broadcaster and bot. The bot account must therefore be different from your broadcaster account. Any unused or newly created Twitch account is suitable; a common convention is to create an account named <channelname>bot for this purpose.

Connecting the bot account

1. In a separate browser session (or an incognito window) sign in to Twitch with the bot account. This step is the most common source of error: if your regular browser is signed in to Twitch as the broadcaster, the next step will use that account by default.
2. In streamion.bot, on /pro/custom-bot, click Connect Bot Account.
3. The Twitch authorization page opens. Choose the bot account, not the broadcaster. streamion.bot forces Twitch to show the account picker so that the choice has to be explicit.
4. Grant the requested scopes (individual permissions). These cover the chat read/send abilities streamion.bot needs, plus a small number of supporting scopes.
5. You are redirected back to /pro/custom-bot. The page now shows Connected as <bot_login>, along with the display name, the granted scopes, the connection time, and when the access token expires.

streamion.bot double-checks the connection on the server side. If Twitch returns the broadcaster account, or if any required scope is missing, the connection is not saved and the page shows an error banner indicating which check failed.

After connecting

• Chat messages posted by streamion.bot now appear under the bot account's name and avatar instead of streamion.bot.
• The action is recorded in the admin audit log as tenant.custom-bot.connected.
• All other functionality continues unchanged: built-in commands, custom commands, counters, timers, and event responses. Only the identity under which messages are posted changes.

Re-authorizing

Twitch access tokens are refreshed by streamion.bot automatically in the background. Automatic refresh fails in two cases:

• The bot account's password has been changed.
• The streamion.bot app has been revoked in the bot account's Twitch settings.

In either case, the page shows a red Bot connection needs re-authorization banner. Until the connection is restored, streamion.bot falls back to its default chat identity so that chat keeps working. Click Reconnect to repeat the OAuth flow with the bot account.

Disconnecting

Click Disconnect on the page and confirm. streamion.bot revokes the Twitch tokens, removes the stored connection, and writes an entry to the audit log. Chat posting reverts to the default chat identity on the next message.

When the Pro entitlement ends

The stored bot connection is not deleted; streamion.bot simply stops using it and falls back to its default chat identity. When the Pro entitlement is reactivated (through renewal or a new grant), the connection becomes active again automatically. You do not have to walk through the OAuth flow a second time.

Troubleshooting