Axonius Documentation
  1. Enforcement Action Library
  2. Execute Endpoint Security Agent Action

Nexthink Infinity NQL - Trigger Remote Action

Nexthink Infinity NQL - Trigger Remote Action executes a Nexthink remote action on devices for:

  • Assets returned by the selected query or assets selected on the relevant asset page.

See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.

📘

Note


Required Fields

These fields must be configured to run the Enforcement Action.

📘

Note

The Collector UID field must be available in the asset data for this Enforcement Action to work. This field is automatically collected by the Nexthink Infinity NQL adapter and uniquely identifies each device in the Nexthink platform.

  • Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
  • Configure Dynamic Values (optional) - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.
  • Use stored credentials from the Nexthink Infinity NQL adapter - Select this option to use credentials from the adapter connection. By default, the first connection is selected.

    • When you select this option, the Select Adapter Connection drop-down becomes available. Select the adapter connection to use for this Enforcement Action.

  • Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Working with Axonius Compute Nodes.

  • Remote Action ID - The Nexthink remote action identifier (e.g., #ExampleRA). This ID corresponds to a remote action configured in your Nexthink platform.

Additional Fields

These fields are optional.

  • Expires In Minutes - How long the remote action trigger remains valid before expiring if the device does not come online to process it. Default: 60 minutes, valid range: 60-10080 minutes.

  • Trigger Reason - Provide a human-readable reason for triggering the remote action. The default is "Triggered by Axonius", but you can edit it.

  • External Reference - Provide an external ticket or reference identifier (e.g., ServiceNow ticket number, Jira issue ID). This allows you to correlate the remote action execution with external workflows.

Connection Settings

💡

Connection and Credentials

When Use stored credentials from the adapter is disabled, some of the connection fields below are required to create the connection, while other fields are optional.

  • Host Name or IP Address - Base domain for the Nexthink Infinity API, for example, https://{instance}.api.{region}.nexthink.cloud.
    • Replace {instance} and {region} with your specific values.
    • Do not add any specific endpoints after the domain.
  • Client ID and Client Secret - OAuth credentials for authentication with the Nexthink Infinity API.
  • Device Query ID (required) - The NQL query ID for retrieving device data.
  • Software Query ID (optional) - The NQL query ID for retrieving software data.
  • User Query ID (optional) - NQL query ID for retrieving user data.
  • Verify SSL, HTTPS Proxy, HTTPS Proxy User Name, and HTTPS Proxy Password - Refer to the adapter documentation for explanations on these optional fields.
  • Gateway Name - Select the Gateway through which to connect to perform the action.

APIs

Axonius uses the Nexthink Remote Actions API - POST /api/v1/act/execute

Required Ports

Axonius must be able to communicate via the following ports:

  • TCP port 443 (HTTPS)

Required Permissions

The stored credentials, or those provided in Connection and Credentials, must have the following permission(s) to perform this Enforcement Action:

  • OAuth Application - A registered OAuth application in Nexthink with appropriate scopes to execute remote actions via API.
  • Remote Action Execution Permission - The API credentials must have permission to execute remote actions on target devices.
  • Remote Action Configuration - The remote action must be configured in Nexthink with API triggering enabled.
📘

Note

The exact permission names should be confirmed with your Nexthink administrator or Nexthink support, as the publicly available API documentation does not include granular permission details.

To learn more about Enforcement Actions, see Enforcement Actions.

Version Matrix

This Enforcement Action was tested only with the versions marked as supported, but may work with other versions. Please contact Axonius Support if you have a version that is not listed and it is not functioning as expected.

VersionSupportedNotes
Nexthink Infinity CloudYesTested with Nexthink Infinity Cloud platform