--- title: "PowerShell Module Basics" slug: "powershell" description: "This document shows users how to execute PowerShell scripts from Flows within Decisions, via the PowerShell Module. Prior to using this module, users must have PowerShell 3.0 instead onto their Decisions server. The document provides a tutorial for how to create a PowerShelll Script Project, which will then be usable as a category in the Flow Designer. " updated: 2026-08-13T20:04:19Z published: 2026-08-13T20:04:19Z canonical: "documentation.decisions.com/powershell" --- > ## Documentation Index > Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt > Use this file to discover all available pages before exploring further. # PowerShell Module Basics Security RiskThis add-on module provides scripting capability.  Administrators acknowledge and accept full responsibility for securing the environment ahead of installing and using it. | ## Module Details | | --- | | **Installation Location** | Core module | | **Step Location** | Integration > Powershell | | **Settings Location** | N/A | | **Prerequisites** | PowerShell Module [Installed](/version-10/docs/installing-modules-decisions) Project Dependency [created](https://documentation.decisions.com/version-10/docs/project-dependencies) | ## Overview The **PowerShell Module** allows the execution of PowerShell scripts from Flows. PowerShell supports numerous plugins for integrating with system software and enterprise applications. PowerShell can only run via a **remote connection**. ## Considerations Note for Third-Party Systems and SubscriptionsCustomers are responsible for securing and maintaining accounts with third-party systems and subscriptions. --- ## Run PowerShell Remotely All PowerShell steps run remotely. This exposes new inputs to specify which machine to remotely run the script and uses **"WS-Management-based Windows PowerShell remoting".** Users must add the IP of the VM to the TrustedHosts list during configuration by entering the following command: Limitations of PowerShell in ContainersIn containerized environments, the 'Run Remotely' option on PowerShell steps, which facilitates remote script execution, is not supported.PowerShellPowerShell ```powershell Set-Item WSMan:\localhost\Client\TrustedHosts -Value (IP Address) ``` PowerShell To verify that the command works, use the following PowerShell command: PowerShellPowerShell ```powershell Get-Item WSMan:\localhost\Client\TrustedHosts ``` PowerShell This will allow PowerShell to be run remotely as described in this article: [Computer Trusted Hosts](https://www.dtonias.com/add-computers-trustedhosts-list-powershell/). ### Troubleshooting - Enabling PowerShell Remoting While not required for the PowerShell module or for enabling remote connection, Administrators experiencing difficulties with the above option may instead enable Powershell Remoting. This method enables remote PowerShell connections by calling the server itself remotely. By default, WS-Man and PowerShell remoting use ports 5985 and 5986 for connections over HTTP and HTTPS, respectively. Open PowerShell as an Administrator to enable remoting and run the following command. PowerShellPowerShell ```powershell Enable-PSRemoting -Force ``` PowerShell The following response should be returned:![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/psr_3.png) --- ## Example 1. In a Project, navigate to **[Project Name]****> Manage > Integrations > Scripting> Powershell**. Right-click Powershell Script Projects and click **Add Script Folder**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1783011249681.png) 2. On the Add Script Project window, enter a name for the Script Project that will be used and click SAVE. This name will be used as a category in the Flow Designer to group PowerShell steps.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1783011275793.png) 3. Right-click on the new PowerShell Script Project and click **Add Script**. There is also an **Add Script** action towards the top of the folder. In v9.6 and above, script folders can be deleted by right-clicking the folder, then selecting **Manage | More > Delete**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1783011295419.png) 4. On the Add Script window, enter a name for the script under **ScriptName** and the code under **Script**. If applicable, add input and output values. Input values must be strings, match the PowerShell token name minus the dollar $ symbol, and allow array input via a comma-separated list to mimic PowerShell console behavior. Output values cannot return structured data; however, a script returning an object can specify its data members to return as string arrays. For further information, refer to the "[Process Class](https://docs.microsoft.com/en-us/dotnet/api/system.diagnostics.process?redirectedfrom=MSDN&view=netframework-4.8)" article in Microsoft's documentation.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1783011316729.png) 5. Click SAVE to return to the PowerShell Script Project. 6. In a Flow Designer, navigate to **Integration > PowerShell> [Script Project Name]**. Add the script step to the workspace. The values entered for the **Input** and **Output** categories should appear on the step. Refer to the next article to learn more about the [PowerShell Script Step Outputs](https://documentation.decisions.com/version-10/docs/working-powershell-script-step-output). --- ## System Level Starting in Version 10, Scripts can only be created at the Project level. However, if migrating from earlier versions (such as Version 8 or Version 9) to Version 10, previously created Scripts can still be found at the System level. For more information, please refer to: [Projects Conversion](https://documentation.decisions.com/docs/projects-conversion). The screenshot below depicts how a Script folder can be moved to a specific Project. Right-click the folder and select **Manage > Move to Project**. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1786649963436.png) --- ## Feature Changes | Description | Version | Release Date | Developer Task | | --- | --- | --- | --- | | Updated styling for the PowerShell scripting module folder icon. | [10.1](https://documentation.decisions.com/v99/docs/version-10-1-release-notes) | August 2026 | [DT-048252] |