Do · Actions · supported
Advanced: run command text
Run command text on one platform. With no event platform (such as a SheevPad press), automatically choose an available connection: Twitch, YouTube live chat, then Kick. Explicit targets must be available. Prefer friendly bot actions when possible.
action.run_command · 2.8.0
Requirements and availability
An existing supported command and an available Twitch, YouTube live-chat, Kick, or X connection; TikTok is excluded; X supports local command effects with responses suppressed.
Picker contexts: automation, timer, command, pad.
Behavior
Resolve command text; blank does nothing. Dispatch a registered command first, then full command routing for custom/Marketplace commands. Preserve explicit targets and real event platforms; no event platform (including a default SheevPad press) or auto chooses the first available Twitch, YouTube live chat, Kick, then X connection (X executes local commands with responses suppressed). Unavailable targets fail before command dispatch. Replies and scheduled Marketplace continuations retain that one target. Uses broadcaster automation authority, bypassing public-command enabled/platform checks where supported. This is not a shell or arbitrary script action.
Configure in the app
Open: Do → Advanced Actions (commands only) → Add action
Steps
- Choose action category Chat Bot Commands, select Advanced: run command text, and click Add action.
- Expand the action card. Configure the Fields below; check Editor defaults for your context and any operation-dependent fields.
- Choose resource values from real app pickers. Set output Platform separately from the trigger Where setting when the action offers it.
- Use Move action up / Move action down to position this action, then save the containing command, automation, timer or SheevPad button.
Limitations
- Arbitrary command text does not have one safe TikTok response contract; use the corresponding friendly action instead.
- Picker availability does not supply missing event variables. Check prerequisites and originating provider.
- An action return value is not automatically a sequence variable. Only documented producers create template outputs.
Fields
| Field | Input / options | Defaults / limits | Availability |
|---|---|---|---|
Command textcommand | text | Editor defaults: {"automation":null,"timer":null,"command":null,"pad":null} Example hint: !quote or !sr {message} | Supports variables |
Platformplatform | select
| Editor defaults: {"automation":"event","timer":"all","command":"event","pad":"all"} | Literal value / selected resource |
Contract details
- Declared Contexts
[ "timer", "automation" ]- Picker Contexts
[ "automation", "timer", "command", "pad" ]- Hidden From Picker
- false
- Required Variables
[]- Failure Behavior
- See the behavior for local skips/errors and context entries for sequence continuation.
- Outputs
[]
Examples
Illustrative configuration; replace fixture resources in the editor. This is not an import file.
{
"command": "!quote",
"platform": "auto"
}Related entries
Source and verification
Source-reviewed for 2.8.0. Connected-service validation remains subject to release UAT.
- src/features/automations.js — ACTION_REGISTRY.run_command
- public/index.html — getBuilderActionEntries / createDefaultAction
Exact build metadata and source revision: version overview and downloads.