> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/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/user-guide/spark/setting-up-and-managing-spark/managing-agent-actions.md). # Managing Spark actions ## Understanding Spark actions Actions enable seamless automation for diagnosing issues and performing remediations directly from Spark. These actions enhance the employee experience while reducing manual IT effort by providing both ready-to-use and customizable solutions. Activate a wide range of Spark actions to prioritize automatic, instant resolutions over manual guidance and issue escalations. There are four types of actions available in Spark: * [**Agent actions**](#agent-actions-for-spark): Activate ready-to-use actions directly from the Spark Cockpit. These actions let you quickly start monitoring and remediating common issues without any setup. * [**API calls**](#api-calls-for-spark): Connect Spark to your ITSM system. Spark uses API calls to create tickets when it escalates an unresolved conversation. Refer to [API Calls](/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/api-calls.md) for more information. * [**Remote actions**](#remote-actions-and-workflows-for-spark): Create new remote actions or use existing remote actions to enable them for Spark. Refer to [Managing remote actions](/user-guide/remote-actions/setting-up-and-managing-remote-actions/managing-remote-actions.md#triggering) to activate Spark triggers for remote actions. * [**Workflows**](#workflows): Create new workflows or use existing workflows to enable them for Spark. Refer to [Creating Workflows](/user-guide/workflows/creating-workflows.md#optionally-make-the-workflow-available-in-nexthink-spark) to make workflows available in Spark. {% hint style="info" %} Spark currently does not support executing remediation actions in VDI environments. {% endhint %} Enable Spark permissions for these actions centrally on the [Manage Actions](#managing-spark-actions) page. ### Agent actions for Spark Agent actions enable Spark to automatically diagnose and resolve device issues. They are grouped into two categories: * **Diagnostic actions**: Collect real-time information about device configuration and performance to understand problems. * **Remediation actions**: Apply fixes directly, such as resetting configuration settings or repairing components. {% hint style="info" %} To ensure quality, reliability, and compatibility, agent actions are centrally managed by Nexthink. As a result, creating, configuring or deleting agent actions is not supported, except for configuring input parameters of agent actions where they are available. {% endhint %} Refer to [#using-the-action-menu-for-spark-actions](#using-the-action-menu-for-spark-actions "mention") on this page for more information on viewing details or enabling Agent actions. #### Out-of-the-box diagnostic actions Spark comes with a comprehensive set of built-in diagnostics actions, ready to use from day one. These actions are seamlessly integrated into Spark and require no configuration, activation, or management, enabling fluid employee support out of the box. To keep management simple, only manageable Spark actions are listed on the **Manage actions** page. ### API calls for Spark API calls connect Spark to your IT service management (ITSM) system. Spark uses them to create tickets when it escalates an unresolved conversation. Spark also follows up on tickets through API calls that it calls agent actions. Each agent action is an API call to your ITSM system. Refer to [Ticket escalation with Spark](/user-guide/spark/setting-up-and-managing-spark/ticket-escalation-with-spark.md)for more information on how Spark uses API calls for escalation. ### Remote actions and workflows for Spark Configure custom or Nexthink Library remote actions or workflows and enable them in Spark to extend its capabilities. Adapt these items to your organization's specific needs. #### Remote actions From **Remote Actions > Manage remote actions** in the main menu: 1. Select the remote action that you want to enable for Spark or create a new remote action. 2. Select the **Spark triggering** mechanism for the remote action. Once the Spark trigger method is saved, the remote action appears on the **Manage Actions** page, where you can enable it. Refer to the [#enabling-spark-permissions](#enabling-spark-permissions "mention") section on this page. {% hint style="warning" %} Nexthink does not recommend activating remote actions that use campaigns to communicate with employees in Spark. Employee consent and communication can be managed by Spark on the basis of your configured messages. {% endhint %} #### Workflows From **Workflows > Manage workflows** in the main menu: 1. Select the workflow that you want to enable for Spark or create a new workflow. 2. Tick the **Available in > Spark** option. Once this option is saved, the workflow appears on the **Manage Actions** page, where you can enable it. Refer to the [#enabling-spark-permissions](#enabling-spark-permissions "mention") section on this page. ## Managing Spark Actions To access the list of available actions, navigate to **Spark > Manage Spark** and select the **Actions** tab. On this page, you define: * Which Agent actions, Remote actions, and Workflows Spark can run. * Whether Spark requires employee approval before running a Remote action or Workflow. * Which messages Spark displays before, during, and after action execution. These settings help you balance automation and operational control while ensuring clear and transparent action execution for employees.
### Understanding the Spark actions list From the **Spark Actions** page, you can view a table with the list of all available actions. The table is organized by: * **Name**: The unique name of the action. * **Origin**: Indicates from where the action originates. * **Purpose**: Indicates whether the action is **Diagnostic** or **Remediation.** This applies to remote actions and [#agent-actions-for-spark](#agent-actions-for-spark "mention"). * **Type**: Indicates whether the action is an **Agent action**, **API call**, **Remote action** or **Workflow.** * **Category**: Indicates the action category based on its purpose. This applies to Agent actions only. * **Platforms**: The operating systems supported by the action. * **Spark permissions**: Toggle on to allow Spark to use the selected Agent action.
{% hint style="info" %} Only actions explicitly enabled for Spark, by an administrator, appear in the **Spark Actions** table. Additionally, Spark comes with a comprehensive set of built-in **Diagnostics** actions. These built-in actions require no configuration, activation, or management, enabling fluid employee support from day one. To keep management simple, only manageable Spark actions are listed in the **Actions** table. {% endhint %} ### Viewing action card details To view the action details, select an action row to open the action card details in the right-side panel. This card provides transparency into how the action behaves and its potential impact on the device and user. The action card displays three main sections: * **Action behavior**: Describes what happens on the device when the action runs. * **User impact:** Describes how the action affects the user experience. * **Execution details:** Shows technical information about how the action runs, including: * **Platform**: The operating systems where the action runs (Windows, macOS, or both). * **Timeout**: How long the system waits for the action to complete before stopping it. * **Runs as**: The execution context, for example *Interactive User*. * **User informed**: Whether the user receives notification about the action. * **Input parameters**: Any configurable parameters for the action.
### Filtering the Spark actions list Use the filters at the top of the list to narrow it to the actions you want to work on. Filter by **Origin**, **Type**, **Purpose**, **Platforms** or **Spark permissions**. Refer to [Filtering capabilities](/getting-started/navigating-the-web-interface.md#navigatingthewebinterface-filteringcapabilities) for more information. Use the **search bar** in the top-right corner of the page to locate an action by name. This narrows the displayed results and helps you focus on specific topics or issues. ### Enabling Spark permissions Use the **Spark permissions** column to enable or disable an Agent action, API call, Remote Action, or Workflow. When you enable an API call, Remote action, or Workflow, the **Configure action approval** panel appears. ### Using the action menu for Spark actions To display the action menu, select an action in the list and click the three dots on the right side of the row. In the action menu, you see the available actions, which will vary depending on the type of Spark action: * **Configure action approval**: Define whether Spark should request employee consent before running the action and configure messages shown to the employee. * **Edit**: Edit the selected remote action or workflow. For agent actions, only input parameters can be configured, if available. * **Execute action**: Run the action on a relevant device to verify its behavior before enabling it for Spark. * **View results**: Open Investigations with a list of specific remote action executions performed by Spark.
#### Configuring action approval Use **Configure action approval** in the action menu to define whether Spark requires employee approval and how Spark communicates with the employee. At this step, you define the messages Spark displays at each stage of the action lifecycle. These messages help employees understand what is happening and why. In the configuration dialog, specify: * **Employee approval** * **Ask for employee approval first**: Spark prompts the employee before running the action. * **Run without employee approval**: Spark executes the action automatically. * **Messages shown to employees** at each stage of execution, that ensure transparency and support a positive employee experience. * **Before action execution:** Explains why the action is required and what Spark is about to do. * **While the action is running (optional):** Informs the employee that the action is running and describes any temporary impact. * **After the action completes (optional):** Confirms that the action has completed and explains what changed or what to do next. {% hint style="info" %} Employee messaging varies by Spark action type. {% endhint %}
### Querying Agent actions with NQL Refer to the [Spark NQL capabilities](/user-guide/spark/spark-nql-capabilities.md) documentation 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.nexthink.com/user-guide/spark/setting-up-and-managing-spark/managing-agent-actions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.