Skip to main content

đź’ˇ Nexthink Device Management Ambient Agents

  • March 9, 2026
  • 2 replies
  • 44 views
rgeroulo
Forum|alt.badge.img

Hello Community!

I wanted to share a set of practical use cases for managing device health that empowers end-users to take action when their hardware needs attention. While these notifications and workflows leverage Nexthink, other device management tools can be substituted using a similar architecture.

The Solution: Nexthink Ambient Agents

Nexthink offers a Remote Actions API to initiate tasks, native webhooks for real-time alerts, and Nexthink Query Language (NQL) to define data triggers. Combining these capabilities allows ambient agents to listen, notify, and assist users with actions such as:

  • Clear Device/Teams Cache
  • Restart Device
  • Disk and Recycling Bin Cleanup
  • Repair Office 365

Architecture Overview

  1. Nexthink Webhook

    1. Nexthink natively supports webhooks based on NQL queries. When a query condition is met, it sends a payload that Moveworks monitors in real time. The Configuring webhook NQL conditions and Configuring webhook fields: Method, Resource, and Payload are great resources for defining NQL queries in Nexthink.

  2. Agent Studio Ambient Agent

    1. Within Agent Studio, a plugin configured for System Triggers listens for and processes the incoming payload.

  3. User Engagement

    1. The payload is passed to a Compound Action, which sends a notification to the end user. These messages can include interactive buttons that trigger a Nexthink Remote Action—like clearing a Teams cache—directly from the chat interface.

This architecture provides users with real-time, machine-related notifications and the ability to resolve issues with a single click.

Have you implemented any of these or other Nexthink-related plugins? Let me know in the comments!

    2 replies

    J
    Forum|alt.badge.img+5
    • jaime.renn
    • Known Participant
    • March 9, 2026

    At Leidos, we did the teams cache reset capability - but i like this proactive approach, i will see if the team wants to enhance it.  Our team is currently working on a nexThink capability to do hardware attestations, we have to do these every 6 months as employees , so we have the agent checking the due dates from ServiceNow, getting the serial number from the device, the user email and asking NexThink if the user has logged into that specific machine in the last 7 days, if it has , the agent will complete an auto attestation for them handle the service now RITM associated and capture the details in an audit log. If the agent successfully does the auto attest, its sends the user a notification telling them what happened and hte associated RITM.  If the bot can’t do the attestation , it doesn’t send the user anything and just relies on the normal workflow of the user receiving emails from SN or a notification from the chatbot.

    • Nexthink automation for six‑month attestations in development.
    • Agent workflow: check due date (24 days out) → get hardware serial & user email → query Nexthink → auto‑attest if logged in within 7 days → complete RITM → audit log → notify user.
    • If auto‑attest fails, standard notification/workflow remains in place.
      rgeroulo
      Forum|alt.badge.img
      • rgeroulo
      • Author
      • Employee
      • March 9, 2026

      Awesome use case ​@jaime.renn. Including the ServiceNow ticketing portion as well for tracking is a great addition that can be included in any of these use cases!

      Terms & ConditionsCookie settingsAccessibility statement