Custom Bot Account

By default, AveloBot posts in your chat under its standard AveloBot chat identity. The Custom Bot Pro feature replaces this default identity with a Twitch account of your own: AveloBot 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 @avelobot.

The feature page is located at /pro/custom-bot. Only the workspace Owner has access. Connecting a Twitch account affects the entire workspace, and the OAuth flow requires 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 subsequent step will use that account by default.
2. In AveloBot, on /pro/custom-bot, click Connect Bot Account.
3. The Twitch authorization page opens. Select the bot account, not the broadcaster. AveloBot enforces Twitch's account picker so that an explicit selection is required.
4. Grant the requested scopes. These cover the chat read/send capabilities AveloBot needs, plus a small number of supporting scopes.
5. You are redirected back to /pro/custom-bot. The page now displays Connected as <bot_login>, along with the display name, the granted scopes, the connection time, and the token expiry.

AveloBot validates the connection server-side. If Twitch returns the broadcaster account, or if any required scope is missing, the connection is not saved and the page displays an error banner indicating which check failed.

After connecting

• Chat messages posted by AveloBot now appear under the bot account's name and avatar instead of AveloBot.
• 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 AveloBot automatically. Automatic refresh fails in two cases:

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

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

Disconnecting

Click Disconnect on the page and confirm. AveloBot 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; AveloBot simply ceases 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. A new OAuth round trip is not required.

Troubleshooting

Symptom	Likely cause	Fix
OAuth screen shows your broadcaster, not the bot.	You're signed into Twitch with the broadcaster in the same browser session.	Use an incognito window for the bot OAuth, or sign out of Twitch in the main window first.
"Bot account must differ from broadcaster" error.	You picked the broadcaster account on the Twitch screen.	Restart Connect with the correct account.
"Missing scopes" error.	You unticked a scope on the Twitch grant screen.	Reconnect and accept all requested scopes.
Bot connection in red ("needs reauthorization").	Refresh token rejected — usually a password change or app revocation on the bot account.	Click Reconnect.
Chat messages still come from AveloBot.	The Pro entitlement isn't active for your workspace, or the connection is in the "needs reauth" state.	Check /pro for entitlement status; check /pro/custom-bot for connection status.