# Remote Actions

## Remote Actions at a glance

The Remote Actions module lets you run remote actions on employee devices. Remote actions offer several ways to prevent and remediate issues encountered by employees and to gather additional information from devices. A remote action is an executable script that can accept parameters and optionally return outputs to be stored in the data layer.

<figure><img src="/files/UG9jtQ8jCVLm2vicpZS7" alt="" width="760"><figcaption></figcaption></figure>

## Key benefits and use cases

How you use remote actions depends on your purpose and your chosen trigger method. Nexthink has identified four main scenarios or use cases:

* Assisted service
* Self-help
* Self-healing
* On-demand data

Additionally, Remote Actions utilizes an API to programmatically launch remote actions, extending their availability to third-party products, such as self-service portals or ticketing systems. Refer to the [Triggering Remote Actions Via Their API ](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/api-and-integrations-classic/other-integrations-classic/triggering-remote-actions-via-their-api-classic.md)documentation for more information.

### Assisted service <a href="#gettingstartedwithremoteactions-assistedservice" id="gettingstartedwithremoteactions-assistedservice"></a>

Use remote actions to help support teams assist employees.

When support agents with access to the Nexthink web interface receive an incident or detect an issue on a device, they can manually trigger an appropriate remote action to fix the issue. Support agents can also trigger remote actions from the results list on the Investigations page by querying devices and triggering a remote action from the Device View page.

<figure><img src="/files/UG9jtQ8jCVLm2vicpZS7" alt="" width="760"><figcaption></figcaption></figure>

{% hint style="info" %}
Refer to the [Granting permissions to Remote Actions](#gettingstartedwithremoteactions-whatarethepermissionsrequiredtouseremoteactions) section to gain insights on permissions.
{% endhint %}

### Self-help <a href="#gettingstartedwithremoteactions-self-help" id="gettingstartedwithremoteactions-self-help"></a>

Use remote actions to help employees solve issues without requiring external intervention from support.

Run remote actions in conjunction with Nexthink Campaigns in self-help scenarios. Use campaigns to notify employees about issues and ask them to take action.

Define a remote action to be automatically triggered when a known issue is detected on an employee device. Once the system triggers the remote action, a connected campaign is sent, guiding the employee on resolving the issue.

Refer to the [Manage remote actions](/platform/user-guide/remote-actions/getting-started-with-remote-actions/managing-remote-actions.md) and [Trigger a campaign](/platform/user-guide/campaigns/working-with-campaigns/triggering-campaigns.md) documentation for more information.

How you run self-help remote actions depends on whether the script payload requires administrative privileges. Run the remote action:

* In the context of the current active user, if the action requires no special privileges.
* In the context of the local system account, if the action requires administrative privileges.

### Self-healing <a href="#gettingstartedwithremoteactions-self-healing" id="gettingstartedwithremoteactions-self-healing"></a>

Use remote actions to fully automate the remediation of specific issues on employee devices, avoiding human intervention.

Define remote actions to be automatically triggered when a known issue is detected on a device. Execute a remediation script that does not require employee interaction. Consider the frequency of execution of these kinds of remote actions.

Refer to the [Manage remote actions](/platform/user-guide/remote-actions/getting-started-with-remote-actions/managing-remote-actions.md) documentation for information on how to create and edit remote actions.

### On-demand data <a href="#gettingstartedwithremoteactions-on-demanddata" id="gettingstartedwithremoteactions-on-demanddata"></a>

Use remote actions to get additional data from devices and incorporate it into Nexthink.

Schedule remote actions periodically on specific devices to gather additional information that Nexthink does not collect by default.

Refer to the [Manage remote actions](/platform/user-guide/remote-actions/getting-started-with-remote-actions/managing-remote-actions.md) documentation for more information on how to execute remote actions on demand using Nexthink Query Language (NQL).

Create and schedule remote actions to prevent and remediate issues. Schedule them to run automatically on one or more devices using Nexthink Query Language (NQL). Monitor the success of remote actions with sophisticated remote action dashboards.

***

## Get started with Remote Actions

Nexthink Remote Actions allows you to execute small scripts on employee devices. Remote actions provide a number of opportunities for the prevention and remediation of issues encountered by employees, as well as for gathering additional information from endpoints running Nexthink Collector.

* [Working with Remote Actions](/platform/user-guide/remote-actions/using-remote-actions.md)
* [Setting up and managing Remote Actions](/platform/user-guide/remote-actions/getting-started-with-remote-actions.md)
* [Remote Actions NQL capabilities](/platform/user-guide/remote-actions/remote-actions-nql-examples.md)
* [Remote Actions in Finder (classic)](/platform/user-guide/remote-actions/remote-actions-in-finder-classic.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.nexthink.com/platform/user-guide/remote-actions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.