Create Twitch Prediction

Requirements and availability

Twitch Affiliate/Partner broadcaster, channel:manage:predictions permission (updated sign-in service plus reconnect), no unresolved prediction.

Picker contexts: automation, timer, command, pad.

Behavior

Resolve the question and each ordered outcome once through the shared variable/RNG engine in Twitch context; validate the final nonempty question (45 characters), 2–10 distinct outcomes (25 characters each) and whole entry window 30–1800 seconds. Create one Channel Points prediction on the connected Twitch broadcaster. Timers execute this action only on their Twitch firing. Never replace an active prediction or retry a creation automatically. In the main window pin area select Prediction to lock entries, choose and explicitly confirm a winner, or cancel/refund. Settlement rechecks the exact current prediction; unresolved cards remain available after entries close.

Configure in the app

Open: Do → Advanced Actions (commands only) → Add action

Steps

1. Choose action category Stream Platform Commands, select Create Twitch Prediction, and click Add action.
2. Expand the action card. Configure the Fields below; check Editor defaults for your context and any operation-dependent fields.
3. Use the Question, Choices/Outcomes and Timing groups. Fill Question and the initial numbered Yes/No rows. Use Add option and the adjacent Remove option button to adjust the list within its displayed limits. Click Variables (the curly-brace button at narrow widths) beside a field to open its chooser; other choosers close, selecting a variable inserts into that field and closes the chooser, and Escape closes it without insertion. For a named RNG list use {list:your-list-name}. Read the resolved-text limits beside the groups, set duration in Timing, and expand Permissions and variable help only when needed. This action always targets the connected Twitch broadcaster; timers run it only on Twitch. No creation happens merely by saving.
4. Choose resource values from real app pickers. Set output Platform separately from the trigger Where setting when the action offers it.
5. Use Move action up / Move action down to position this action, then save the containing command, automation, timer or SheevPad button.

Limitations

• Prediction creation always targets the connected Twitch broadcaster; other platforms are unsupported and non-Twitch timer firings skip it.
• 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

Contract details

Declared Contexts

[
  "timer",
  "automation",
  "command",
  "pad"
]

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.

{
  "title": "Will we win?",
  "options": [
    "Yes",
    "No"
  ],
  "duration": 60
}

Related entries

• Automation
• Timer
• Custom command
• SheevPad action button

Source and verification

Source-reviewed for 2.8.0. Connected-service validation remains subject to release UAT.

• src/features/automations.js — ACTION_REGISTRY.create_twitch_prediction
• public/index.html — getBuilderActionEntries / createDefaultAction

Exact build metadata and source revision: version overview and downloads.