Remote action thinklet

The Remote Action Thinklet allows workflows to execute a Nexthink Remote Action on the device targeted by the workflow or another specified device. It supports parameterized remote actions, enabling you to adapt the execution dynamically based on workflow execution context.

Once triggered, the workflow waits for the action result before the workflow continues. The workflow can then:

• Use the output values returned by the Remote Action in subsequent Thinklets or conditions.
• Handle expired scenarios (for example, when the device is offline or does not respond within the configured timeout) through a fallback action path.

If the Expired exit of the Remote Action remains unconnected, the workflow will stop processing when the expiration occurs.

Whenever available, the system provides user context to the remote action thinklet to enable more reliable user-context execution, including VDI/session-based use cases.

• Name: Enter a unique name for the Remote action thinklet.
• ID: The system generates the ID automatically based on the name.
• Description (optional): Describe the purpose of the thinklet and what it does. This information is useful for other users of the workflow who may not be familiar with it.
• Timeout: Set the timeout in minutes or hours. This dictates how long the workflow waits for a response from the remote action before timing out. If the device is offline, the workflow may reach the timeout before the device gets back online. When the timeout limit is reached, the thinklet enters an Expiration state.
• Select remote action: Identify the remote action that the thinklet will execute. The remote action must have the Workflow trigger configured in order to appear on the list.
• Select device: Select the device on which the remote action will be executed. To apply the device against the executed workflow, ensure the Select device input field is set as a Targeted device.
• Parameters: Configure the required parameters for the remote action.

  • When a remote action has defined parameters, set Allow user to enter a custom value under the Script tab on the Remote action page.
• Outputs: View the outputs of the remote action. When assessing the status of a remote action in a condition, use the following values:

  • 0 for FAILURE: The script executed but returned an error or failed to complete successfully.
  • 1 for SUCCESS: The remote action executed successfully on the target device.
  • 5 for CANCELED: The execution was canceled, typically because the remote action was deleted before execution completed.
  • 6 for OLD COLLECTOR: The target device has an unsupported or older Collector version and cannot execute the remote action.
  • 7 for NO SCRIPT: No applicable script exists for the device platform.
  • Two statuses - WAITING ON DEVICE and EXPIRED - are not reported as numerical values.

If you select a device other than the targeted device and use a remote action configured to run as a Service, configure Collector on that device appropriately.

Refer to the Running remote actions as service documentation for more information about the configuration.