YouTube destination
Runs YouTube live chat and broadcast actions from rules and Control board buttons with the YouTube Data API. Requires StreamPulse Pro, including connection tests and actions. Google tokens stay on the managed gateway; no user developer credentials are required.
Set up
- Add a YouTube account and sign in as described in YouTube source, with Allow actions ticked. If you ticked it after signing in, sign in again.
- Add a YouTube destination, choose that account as the sending account, and test the connection.
- Add an action to a rule or Control board button, choose the YouTube destination, an action and, where asked, the Channel.
The channel can be your own or any other YouTube account, including read-only accounts. Actions that use live chat need the channel to be live.
Actions
| Action | Sender | Fields |
|---|---|---|
| Send chat message | Any account | Channel, message (up to 200 characters) |
| Delete chat message | Channel owner or moderator | Message ID, usually `` |
| Ban or time out user | Channel owner or moderator | Channel, user channel ID (``), timeout |
| Add moderator | Channel owner | Channel, user channel ID |
| Update stream title | Channel owner | New title for the sending account’s current live broadcast |
A moderator account can moderate another channel’s chat: sign it in, then pick the channel (for example a read-only account) on the action. Fields support templates. Errors from YouTube, such as missing permissions or quota, appear in Events > Activity.
Each action uses API quota from the operator’s shared Google project (about 50 units for most writes, plus about 100 units to find another channel’s live stream at most once a minute). See API quota.