Commandline Execute Action
The Commandline Execute Action node can be used to run shell commands on either the client or the server.
This node supports multiple operating systems, including Windows, macOS, and Unix/Linux environments. Depending on the operating system, the command will be executed using the respective system shell (e.g., Windows Command Prompt, macOS Terminal, or a Unix shell). This makes it possible to trigger external third-party tools directly from a stream.
Unlike the CMD Execute Action node, this node is not limited to Windows clients and can also be executed in server streams, provided the target system supports shell execution.
Complex or concatenated commands should be avoided. If more advanced execution is required, it is recommended to prepare a script file (e.g., .bat, .ps1, .sh) in advance and execute that script using this node.
The result of the node can be retrieved either via the {stream.last_result} wildcard or directly through {node.result.?}.
When the Async option is enabled, no result is returned because the command is executed in the background while subsequent node(s) are already being processed.
Important — Operating System Compatibility
Commands are not automatically translated between operating systems. The Commandline Execute Action node executes the command exactly as provided and does not adapt it to the target system.
You must write the command specifically for the operating system of the host that executes the node. For example:
Windows:
dirmacOS / Linux:
ls
Another common example is opening a file or application:
Windows:
start notepad.exemacOS:
open -a TextEditLinux:
xdg-open file.txt
A command created for one operating system will typically fail on another. It is the responsibility of the user to ensure that the correct syntax, paths, executables, and shell conventions are used for the designated host (client or server).
Last updated