Getting Started

WebTrigger starts with the Windows app. Create the actions and live values you want on your PC, open Quick Connect, then scan in from a phone, tablet, laptop, or browser on the same network.

When you are ready to customize the interface, use a WebShell: a browser-based control layout that decides how your actions, dashboards, and live data appear.

How WebTrigger Works

Think of WebTrigger as the local bridge between your PC and the screens you already own.

Windows PC
WebTrigger
Actions + LDS + Launch Folders
WebShell
Phone / Tablet / Browser

First Setup Workflow

  1. Install WebTrigger on the Windows PC you want to control.
  2. Set your PIN during first launch.
  3. Create a few actions, such as apps, hotkeys, websites, scripts, or system controls.
  4. Open Quick Connect and scan the QR code from another device on your network.
  5. Use a bundled WebShell first, then customize or build your own when you are ready.

Core Concepts

Actions

Actions do things: launch applications, open websites, run scripts, send hotkeys, make HTTP requests, and trigger system controls.

Learn More About Actions

Launch Folders

Launch Folders discover items automatically from configured folders, such as games, applications, utilities, or tools.

Learn More About Launch Folders

First WebShell Build

  1. Start from a bundled WebShell or create a new HTML/CSS/JS folder.
  2. Use WebTrigger APIs to list actions, Live Data Sources, and Launch Folders.
  3. Render the controls and data in the layout you want.
  4. Handle loading, success, error, confirmation, and cooldown states.
  5. Open the WebShell from your phone, tablet, or browser to test it.

Recommended Starting Point

GET /api/theme-context/export is the easiest way for a WebShell to discover actions, Live Data Sources, launch folders, and available APIs.

const context = await fetch('/api/theme-context/export').then(res => res.json());

console.log(context.actions);
console.log(context.liveDataSources);
console.log(context.launchFolders);

Start here when building a new shell, especially if you are using an AI coding assistant to generate the first version.