--- title: "Create Actions" slug: "create-actions-1" description: "Build an action in Action Builder in SysTrack Cloud by uploading its files, then edit it later and send it for approval again." status: "update" updated: 2026-11-05T08:25:38Z published: 2026-11-05T08:25:38Z canonical: "documentation.lakesidesoftware.com/create-actions-1" --- > ## Documentation Index > Fetch the complete documentation index at: https://documentation.lakesidesoftware.com/llms.txt > Use this file to discover all available pages before exploring further. # Create Actions Create an action in Action Builder to package the files that an automation runs on your systems. **Create Action** is available only in SysTrack Cloud, to users with the **Action Builder** permission. After you save the action, it waits for approval on the **Pending Approval** tab. ## Prerequisites - SysTrack Cloud. - The **Action Builder** permission. See [Configure Action Governance Permissions](/documentation/docs/configure-action-governance-permissions-1). ## Create an Action 1. Go to **Configure** > **Tools** > **Automations and Collection Extensions** > **Action Governance** > **Actions**. 2. Click the lock icon in the upper-right corner of the page to enable editing, and click **Create Action**. ![](https://cdn.document360.io/87d11426-6b1f-4b19-b593-b71e55a81af3/Images/Documentation/image(191).png?sv=2026-02-06&spr=https&st=2026-11-06T17%3A01%3A33Z&se=2026-11-06T18%3A01%3A33Z&sr=c&sp=r&sig=uxR2uw51Q4PWyrGGQprYUUutlV3u8DI6B0uP9rT715I%3D) 3. Enter a **Name**, a **Version**, and a **Description**. The **Name** can be up to 60 characters long and can contain only letters, numbers, and spaces. ![](https://cdn.document360.io/87d11426-6b1f-4b19-b593-b71e55a81af3/Images/Documentation/image(192).png?sv=2026-02-06&spr=https&st=2026-11-06T17%3A01%3A33Z&se=2026-11-06T18%3A01%3A33Z&sr=c&sp=r&sig=uxR2uw51Q4PWyrGGQprYUUutlV3u8DI6B0uP9rT715I%3D) 4. Under **Supported OS**, select one or more of **Windows**, **Mac**, and **Linux**. No system is selected when the form opens. You must select at least one to save the action. 5. Click **+** next to **Build Files** to browse to a file and add it to the action. You can add one file at a time, and the maximum file size is 150 MB. Each file is scanned when you upload it. If the scan fails, remove the file and add it again. **Save Action** is available only after every file has passed the scan. 6. For each file, select the **File Type**: **Exec** or **Support**. For an **Exec** file, also select the **Command Type** (**Automation** or **Collection Extension**) and whether the file runs Sync or Async. When you add a file, **Exec**, **Automation**, and **Sync** are selected. For a Support file, the Command Type and Sync or Async options are hidden. To remove a file, click the trash icon. 7. Optional: add **Parameters** for the action and **Usage Examples** that show how to use those parameters. - Create a parameter entry for every parameter option in the action. The entries help users who create automations see what data they need to provide to run the action. - **Parameters** have these fields: - **Name**: the name of the parameter. It can be a descriptive name, because it only guides users on what to pass to the action. - **Units**: optional. The units of the value that is passed for this parameter. - **Required?**: guidance on how to use the action. - Select **Required** if the script needs the parameter to run properly. **Required** is selected by default. - Select **Not Required** if the parameter is optional. Optional parameters usually change or extend the default behavior of the script, for example to turn on conditional logic or branching. For example, an action might clear the recycle bin by default. If an automation provides an optional parameter value, the action can also clear a specified directory. - **Description**: the purpose of the parameter and any other information that users need to use it. - Use **Usage Examples** to show how to build an automation for this action, and what the automation is for. **Usage Examples** have these fields: - **Action File**: the name of the file that runs when the automation runs. - **Arguments**: the parameters or command-line options that an automation passes to the action. - **Description**: the purpose of the example and any other information about how to use it. 8. Click **Save Action**. The action is not approved or enabled until someone approves it. > [!CAUTION] > **WARNING**: **Clear All** in Action Builder removes all uploaded files and clears all fields in the form. To check the result, select the **Pending Approval** tab. The new action is listed there. To approve it, see [Approve and Enable Actions](/documentation/docs/approve-actions). ## Edit an Action Edit an action in Action Builder to change its details, files, parameters, or usage examples. Editing an action is available only in SysTrack Cloud, to users with the **Action Builder** permission. After you save the changes, the action needs approval again. Prerequisites: - SysTrack Cloud. - The **Action Builder** permission. See [Configure Action Governance Permissions](/documentation/docs/configure-action-governance-permissions-1). > [!CAUTION] > **WARNING**: When you save the changes, the action is no longer sent to systems until someone approves it again. Automations that use the action stop getting it. 1. Go to **Configure** > **Tools** > **Automations and Collection Extensions** > **Action Governance** > **Actions**. 2. Click the lock icon in the upper-right corner of the page to enable editing, then click the name of the action. ![](https://cdn.document360.io/87d11426-6b1f-4b19-b593-b71e55a81af3/Images/Documentation/image(193).png?sv=2026-02-06&spr=https&st=2026-11-06T17%3A01%3A33Z&se=2026-11-06T18%3A01%3A33Z&sr=c&sp=r&sig=uxR2uw51Q4PWyrGGQprYUUutlV3u8DI6B0uP9rT715I%3D) 3. Change the details of the action. You can remove and replace files, and update the parameters and usage examples. 4. Click **Save Action**, then confirm in **Overwrite Action**. The action becomes unapproved and disabled and moves back to **Pending Approval** until someone approves it again. > [!NOTE] > **NOTE**: The **Version** of an action does not change automatically when you update the action. To change it, enter a new value in **Version**. To check the result, select the **Pending Approval** tab. The edited action is listed there. To approve it again, see [Approve and Enable Actions](/documentation/docs/approve-actions). ## Troubleshooting Action Builder Uploads ### A File Upload Fails with a 403 Forbidden Error When a file upload in Action Builder fails with a 403 Forbidden response, a security tool in your network can block the upload. See [Troubleshoot .sys Driver File Upload Failures in Action Builder](/documentation/docs/troubleshoot-sys-driver-file-upload-failures-in-action-builder). ### A File Scan Does Not Finish A file that is still scanning after 5 minutes is marked as failed. Remove it and add it again. If you still can't upload a file to Action Builder, contact Lakeside.