RODbot Documentation
How RODbot connects, what it does, and how operators control channel automation.
RODbot is a YouTube live stream assistant for channel owners and managers. It monitors authorized live chat, runs configured commands, posts approved bot responses, and gives operators dashboard visibility into channel health, auth state, and runtime status.
Getting Started
- Request access if the app is still in limited beta for your channel.
- Sign in with Google using the Google account that owns or manages your YouTube channel.
- Connect Channel to grant YouTube access for the specific channel RODbot should manage.
- Configure commands in the dashboard, including command aliases and enabled/disabled state.
- Monitor runtime health from Dashboard, Logs, and Help so auth, quota, and live chat issues are clear.
Main Features
| Feature | What it does | Operator control |
|---|---|---|
| Commands and aliases | Responds to configured chat commands and common aliases during live streams. | Dashboard Commands page |
| Live chat connection | Finds active live chat and keeps the bot connected while stream automation is enabled. | Dashboard runtime controls |
| Channel profile settings | Stores channel-specific links, handles, fishing targets, catches, and response metadata. | Dashboard profile and command settings |
| Acknowledgements | Can thank eligible subscribers or support events when enabled for the channel. | Dashboard chat controls |
| Logs and diagnostics | Shows recent channel runtime events so operators can understand what the bot did and why. | Logs page |
Google and YouTube Access
RODbot uses incremental authorization. Identity sign-in identifies the Google operator first. YouTube authorization happens separately when connecting or reconnecting a channel.
The YouTube scope is used to read channel, subscriber, live stream and chat resources, post configured bot replies, and delete a selected broadcast after explicit operator confirmation. Broadcast deletion affects YouTube and is separate from disconnecting RODbot or deleting app data. The identity scopes are used to bind the signed-in operator and keep channel sessions associated with the correct owner.
For the exact OAuth scope mapping, retention model, and deletion controls, see the Privacy Policy.
Disconnecting and Deletion
Use Disconnect Channel to revoke Google access for the selected channel. Admin-side deletion is available for account removal requests and app-side data purge workflows. Disconnecting or deleting RODbot data does not delete the underlying YouTube channel.
Remove Bot preserves authorization and settings; daily authorization checks continue while detached. If Google is temporarily unavailable, checks retry hourly. At the 28-day API-data deadline, cached YouTube details and runtime state are cleared and the bot pauses until authorization is verified. Independent configuration and catches remain available after recovery. Disconnect and confirmed revocation instead start full channel cleanup. Admin shows incomplete cleanup, scheduled-check failures and requests needing attention after one hour.
Support
For account, access, deletion, or channel setup help, contact wannaseemyrod@gmail.com. Target response time is within 7 calendar days.