--- title: "Python Module" slug: "python" description: "This document shows discuses how to setup and use the Decisions Python module to execute python scripts. The module allows users to input python script via file upload, or by text input. " tags: ["module"] updated: 2025-10-29T15:06:07Z published: 2025-10-29T15:06:07Z --- > ## 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. # Python Module ## Overview | ## Module Details | | --- | | **Core or GitHub Module** | Core | | **Restart Required** | No (for installation) / Yes (for configuration) | | **Steps Exposed** | Yes | | **Step Location** | Integration > Python | | **Settings Location** | System > Settings Python Module Settings | | **Prerequisites** | - A version of [Python](https://www.python.org/downloads/windows/) installed on the Decisions environment - Access to the file path to the Python directory after installation - A [Project dependency](https://documentation.decisions.com/docs/project-dependencies) is required. | The **Python Module** allows custom scripts written in Python to be created and used as steps inside a Flow. In order to utilize the module, the file path must contain the Python executable to be run. For example, **C:\Program Files\Python\python.exe** will be entered in **Python Module Settings.** Note for Third-Party Systems and SubscriptionsCustomers are responsible for securing and maintaining accounts with third-party systems and subscriptions. --- ## Settings Security RiskThis add-on module provides scripting capability.  Administrators acknowledge and accept full responsibility for securing the environment before installing and using it. Navigate to **System > Settings**. Click on **Python Module Settings** and enter the full file path to the Python executable. Click **SAVE** once the file path has been configured. In order to update the file path, [Decisions must be restarted](/v9/docs/restart-decisions-application).![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1750260801976.png) --- | Feature Details | | --- | | **Introduced in Version** | 8.10 | | **Modified in Version** | 9.6 | | **Location** | System > Settings > Python Module Settings | ## Python Module in Container In order to use the **Python Module** in containers, Decisions has included Python in the container [image](https://hub.docker.com/r/decisionscore/platform/tags). The container will have the most up-to-date version of Python installed. The default path for Python in containers is at `/usr/bin/python3`. After [installing](https://documentation.decisions.com/v9/docs/installing-modules-decisions) the **Python Module**, users need to point the **Python Module Settings** path to `/usr/bin/python3`.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/Screenshot%202024-04-19%20131439.png) --- ## Using Python Scripts in Flow Designer #### Two primary methods exist for utilizing Python scripts within the Decisions Flow Designer: #### 1. Creating Script Projects **Script Projects** house **Python Scripts** that will be generated as steps. They are mainly used for organization, as the name of the**Python Script Project**will appear as a sub-category under **Integrations > Python** in the step **Toolbox**. 1. Navigate to [**Project Name] > Manage > Integrations > Scripting > Python**. Right-click **Python** and select **Add Script Project**. Name the project and click **SAVE.**This action is not available in v9.0 or v9.1.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1740580654297.png) 2. Right-click on the newly created **Python Script Project** and select **Add Script**. A dialog box will appear where you can enter a name for your Custom Python Script and upload your custom `.py` script file under the **File**field.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1740581049298.png) 3. In the **Inputs** field, specify the number of input parameters that your Script will accept. These parameters will be visible when the Script is added as a step in the Decision Flow. After defining your inputs, click **SAVE**. This Script can now be used as a Flow step. 4. Create a Flow and navigate to**Integration > Python > [****Python Script Project ] > [ Custom Python Script ]**(which will now function as a Flow step). Drag and drop this step to the Flow designer. In the properties panel, you will see each declared input parameter listed as an individual input field.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1750170725176.png) NoteAll input parameters will be of type String. #### 2. Execute Python Script Step The **Execute Python Script** step allows **Python Scripts** to be executed without the need to create a **Python****Script Project**. However, only parameter values can be passed to the script; the values cannot be defined in the Flow. | Input | Description | | --- | --- | | Parameter(s) | The parameter inputs to the Script. | | Script File | Similar to the File input when configuring a Script as a Flow step, this will be the file containing the Python script. | | Working Directory | The input controls the first location used to search for the Python executable, along with being the location custom files will be outputted from the script. | ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1750170885329.png) In v9.7+, the Execute Python Simple Script step can also be used. However, this step has limitations and is designed for scripts that: - Do not reference any external libraries. - Do not interact with the file System. This step is optimized for better performance when used with the "Run Flows for List" function, addressing the issue of response time degradation over time that was present in the "Execute Python Script" step. --- ## System Level Scripts can also be created at the System level. After being created, the 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/2024-12-23_09h26_35(1).png) --- ## Feature Changes | Description | Version | Release Date | Developer Task | | --- | --- | --- | --- | | Added the right-click action "Add Script Project" to the Python folder. | [9.2](https://documentation.decisions.com/v99/docs/version-92x-release-notes) | August 2024 | [DT-041379] | | Script folders now have a delete action. | [9.6](https://documentation.decisions.com/v99/docs/version-96x-release-notes) | January 2025 | [DT-042782] | | Script folders at the System level can be moved to a Project. | [9.6](https://documentation.decisions.com/v99/docs/version-96x-release-notes) | January 2025 | [DT-042781] | | Added Execute Python Simple Script step with limitations on external libraries and file system interactions. | [9.7](https://documentation.decisions.com/v99/docs/version-97x-release-notes) | January 2025 | [DT-043521] | For further information on Modules, visit the [Decisions Forum](https://community.decisions.com/categories/Modules).