PowerShell Remote – bring Windows systems into your process
Few automation tools are as versatile as PowerShell – and in many companies a large part of IT automation already runs on it. The linqi PowerShell remote connector brings this world straight into your processes: you specify a PowerShell command that is executed on a connected Windows system, and the result is available to the rest of your process as a data value.
This way your workflows can keep using existing PowerShell automation instead of rebuilding it – for example scripts that query system status, process files or call internal tools. The process step stays understandable for business teams, while the technical execution happens on the Windows system. The result of the execution is handed back cleanly to the process and can be used by the following steps.
From process logic to the Windows system
The PowerShell remote action runs a command you specify on a connected Windows system and hands the result back into the process. This bridges your no-code process logic and the Windows/IT environment: queries, scripts and system tasks become normal process steps whose result you can use in conditions, forms or exports. The connection is maintained as a connection in linqi, so you manage the integration centrally – without business teams needing to know Windows details.
Frequently asked questions about PowerShell Remote
What can I trigger with it?
You specify a PowerShell command that is executed on the connected Windows system. The result – such as a return value – is then available to the process.
What is it typically used for?
Typically system queries, calling internal tools, or file processing by existing PowerShell scripts – embedded in a documented process run.
How is the connection maintained?
The connection to the Windows system is managed centrally as a connection in linqi – with your credentials, but without manual upkeep during operation.
Do business teams need PowerShell knowledge?
No. The process step stays understandable; the technical execution runs in the background on the connected Windows system.