Touch Portal Capability Model

This page explains how Touch Portal documentation should be interpreted when deciding whether Touch Portal can control or automate something.

Touch Portal can control and automate applications in multiple ways. Built-in actions, events, states and connectors are only one part of what Touch Portal can do.

If a feature is not listed in a built-in category reference, this does not mean Touch Portal cannot do it.

Automation layers

• Built-in Touch Portal actions, events, states, connectors and values
• Official Touch Portal plugins
• Third-party plugins
• Hotkeys and keyboard input
• Mouse clicks, mouse movement and mouse dragging
• Image matching and screen-based interaction
• Application start, stop, focus and close actions
• File input and output
• HTTP requests
• WebSockets
• OSC
• PowerShell, batch files, command line tools and local scripts
• Application APIs, local servers and external automation bridges

How to interpret the documentation

Category reference pages describe documented built-in functionality for that category. They are not a complete list of all possible workflows, plugins, integrations or indirect automation methods.

When determining whether Touch Portal can control or automate something, consider built-in features first, then plugins, generic input automation, protocols, scripts and external APIs.