# Remote Actions

**Last Updated On**: 22 Aug 2025  
**4 minutes read**

## Overview

Remote Actions in DEX Manager Plus are reusable, script-based tasks designed to be executed within Workflows. These actions enable IT administrators to perform system-level operations—such as restarting services, clearing temporary files, or uninstalling software—remotely, consistently, and without user intervention. They are not standalone deployments and must be embedded into a workflow to run.

## Why Use Remote Actions?

| Benefit | Description |
|---|---|
| Reusable Automation | Define once and reuse across multiple workflows. |
| Remote Execution | Perform critical tasks on endpoints from a central console. |
| Workflow Integration | Seamlessly insert into any workflow to enable dynamic remediation. |

## Accessing the Remote Actions Module

Navigate to **Remote Actions** in the left pane within the DEX tab. Browse or search for existing scripts. Click **+ Add Script** to create a new remote action for workflow use.

![remote action images](https://cdn.manageengine.com/sites/meweb/images/digital-employee-experience/help/dex/raction1.webp)

## Creating a Remote Action

### Step 1: Upload the Script

Use **Upload Script** to select your script file.

- File size limit: 250 MB
- Supported script types: .ps1, .sh, .vbs, etc.

### Step 2: Configure Properties

| Field | Description |
|---|---|
| Script Arguments (optional) | Define runtime parameters, if required. |
| Exit Codes | Indicate successful execution (e.g., 0). Refer this [document](https://www.manageengine.com/digital-employee-experience/help/dex/returning-error-codes.html) for details |
| Platform | Specify the OS the script is intended for (Windows, Linux, macOS). |

![remote actions](https://cdn.manageengine.com/sites/meweb/images/digital-employee-experience/help/dex/raction2.webp)

### Step 4: Save

Click **Add** to register the script in the Remote Actions library for future use in workflows.

## Using Remote Actions in Workflows

Remote Actions are designed to function as executable steps in a workflow. You can combine them with conditions, user prompts, delays, or alerts to create robust endpoint automation.

**How to use in a workflow:**

- Go to **Workflows > Create Workflow**.
- Drag and drop a **Remote Action** block into the Builder view.
- Choose the required script from your library.
- Add preceding or succeeding blocks (e.g., Condition, Engage, Mail) to build the logic flow.

**Note:** Remote Actions do not run unless embedded inside a deployed workflow.

## Example Use Cases

| Use Case | Description |
|---|---|
| Disk Cleanup | Remove temporary files to reclaim storage. |
| Restart Spooler Service | Resolve printer queue issues remotely. |
| Uninstall Unauthorized Software | Maintain software compliance. |
| Reset DNS/Network Settings | Fix intermittent connectivity without user action. |

## Best Practices

| Recommendation | Why It Matters |
|---|---|
| Test scripts in a controlled group | Prevent negative impact on production devices |
| Include comments in scripts | Improve maintainability and handoffs |
| Use consistent naming conventions | Helps locate and organize scripts |
| Map correct exit codes | Ensures workflows behave predictably |
| Limit sensitive scripts to admin use | Maintains compliance and security |