> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/platform/user-guide/remote-actions/using-remote-actions.md).

# Working with Remote Actions

To start using Remote Actions:

* Review the following [Key Remote Actions concepts](#key-remote-actions-concepts).
* See guides on:
  * [Executing remote actions](/platform/user-guide/remote-actions/using-remote-actions/executing-remote-actions.md)
  * [Monitoring remote actions execution statistics](/platform/user-guide/remote-actions/using-remote-actions/monitoring-remote-actions-execution-statistics.md)
  * [Monitoring specific remote action executions](/platform/user-guide/remote-actions/using-remote-actions/monitoring-specific-remote-action-executions.md)

## Key Remote Actions concepts

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.

### Remote action targets and purpose

Remote action administrators define the target and purpose of each remote action based on the intended use case.

* **Target**: Remote actions can target **devices**, **VDI sessions**, or both. For example, device-targeted actions can collect hardware information or remediate memory issues, while VDI-targeted actions can gather server status information or log off sessions.
  * The selected target determines the context in which the remote action is used and how it interacts with other Nexthink features.

{% hint style="warning" %}
Executing remote actions on **VDI sessions requires** [Nexthink VDI Experience](/platform/user-guide/vdi-experience.md).
{% endhint %}

* **Purpose**: Remote actions can be designed for **data collection**, **remediation**, or both. Data collection actions gather information from targeted devices or sessions, while remediation actions perform changes or corrective actions. This classification helps organize and identify remote actions in dashboards.

### Remote actions execution methods

Remote actions can be triggered with one of the following methods:

* **Manual:** triggered directly by a user through the Nexthink web interface.
* **Scheduled**: launched automatically based on defined targeting and timing rules.
* **API**: triggered by API calls
* **Workflow**: triggered during the execution of a workflow.
* **Spark**: triggered by Spark to automatically collect information or remediate the issue upon employee approval.

Refer to [Executing remote actions](/platform/user-guide/remote-actions/using-remote-actions/executing-remote-actions.md) for more information.

### Remote Action dashboards

Effortlessly keep track of the success of remote actions across your entire organization through advanced Remote Action dashboards.

Refer to [Monitoring remote actions execution statistics](/platform/user-guide/remote-actions/using-remote-actions/monitoring-remote-actions-execution-statistics.md) and [Monitoring specific remote action executions](/platform/user-guide/remote-actions/using-remote-actions/monitoring-specific-remote-action-executions.md) for more information.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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/using-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.