Automation

Automation is where you own the cue logic. Scripts and cue lists sit on the same graph as Action Deck — they are not a parallel product.

What belongs here

  • Cue sequences and timed follows
  • Bridges between OSC / HTTP / MCP / CLI and Action Deck tiles
  • Show logic that should survive a surface swap (desk today, browser tomorrow)

Design stance

  • Scriptability over lock-in — write logic you can read and move.
  • Same graph — automation fires the same sinks and endpoints Control uses.
  • Fail loud — prefer clear skips and logs over silent no-ops when a target is offline.

Patterns that work

  1. Cartwall SFX → network audio device — cartwall pages fire into your chosen network sink (AES67, ST2110, Sonos, garden speaker, etc.; see Overview · No sound card — how do cartwall SFX reach a network audio device? and Getting Started · 04).
  2. OSC in → Action Deck out — external desk presses land on the same tiles operators see.
  3. HTTP cue — simple integrations and show callers without a full desk stack.
  4. Spatial follow-on — after cartwall SFX → network audio, move the bed from Control → Audio → Spatial Layouts (layouts): Add Speaker / Add Spatial Zone, zone DMX Position Control, runtime DmxSpatialBridge X/Y + SignalR (Getting Started · 05). No invented spatial OSC address — use DMX, script, or OSC → show commands.
  5. MCP / HTTP assistants — prefer tools that fire existing Action Deck / Automation cues (API / MCP overview; configure on-prem at AI → MCP / MCP Server first; Cloud MCP optional/advanced only).

Plugin Builder boundary

When a native endpoint is missing, open AI → Plugin Builder (/plugin-builder) and review the result here. That is a capability, not a separate SKU. Keep Automation readable: generated plugins should still look like owned show logic, not mystery meat. Guided: Getting Started · 06.