Actions

Actions are the primary way WebTrigger controls your PC. A WebShell displays an action, the user presses it, and WebTrigger runs the configured behavior on the Windows computer.

Action Types

Application Actions

Launch desktop apps, tools, games, or files configured by the user.

Website Actions

Open a URL in the default browser or build a web launcher for common destinations.

System Actions

Use built-in media, desktop, window, volume, and power controls exposed by WebTrigger.

Script Actions

Run configured commands or scripts for power-user workflows and local automation.

HTTP Actions

Send HTTP requests to local tools, smart home devices, webhooks, or services.

Python Actions

Run Python-backed actions for custom logic when a simple command is not enough.

Action Execution Flow

Button Press

WebShell

WebTrigger API

Action Executes

Result Returned

Action API Endpoints

GET/api/actions

List user-created actions configured in the Windows app.

POST/api/actions/execute/{id}

Execute a configured action by ID.

const actions = await fetch('/api/actions').then(res => res.json());

await fetch(`/api/actions/execute/${encodeURIComponent(actions[0].id)}`, {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify({ confirmed: false })
});

Action Best Practices

Use confirmation prompts for actions that can close apps, run scripts, delete data, or power off the PC.
Use categories and tags so WebShells can group actions automatically.
Show cooldown, loading, success, and error states in your shell UI.
Keep buttons large enough for phone and tablet use.
Treat imported actions and scripts as trusted user content with real PC access.