Chatbot integration flow
The integration follows the scheme below:
The chatbot system controls the interaction with employees, the content of the conversations and the logic used within the conversation.
The Nexthink platform provides APIs that the chatbot calls during conversations. Through the APIs, the chatbot either retrieves data from Nexthink related to a particular conversation using the NQL API or triggers a remediation with the Remote Action API.
A large amount of user data and information about their devices.
Event data to trigger proactive chatbot conversations.
Identify employee or device context
Diagnose employee device issues
Remediate user device issues
Proactive identification of issues
The following are the preliminary steps required for your Nexthink environment:
Verify that your API usage complies with Nexthink’s API usage limits. Refer to the Nexthink developer portal documentation for more information.
Understand how to match users between your chatbot solution and Nexthink. Nexthink Collector collects the username, SID, and UPN, if it is activated. You can use additional data for mapping, including user email, if you activated the Connector for Microsoft Entra ID in your Nexthink instance.
The system requires credentials to secure the calls from your chatbot solution to your Nexthink tenant, and to secure outbound connections from the Nexthink platform for Data Exporters and Webhooks.
Configure API credentials. Refer to the API credentials documentation for more information. Ensure that you have the following permissions activated:
Remote Actions API
(Optionally) Configure connector credentials if you plan to use outbound integrations. Refer to the Connector credentials documentation for more information.
Configure and activate the Nexthink content that your chatbot integration retrieves:
Preconfigure NQL queries within the Nexthink user interface so that the NQL API can call them. Refer to the Chatbot use cases documentation for more information. Typically, required queries include:
Query to retrieve devices and their basic information for a given user.
Query to retrieve ad-hoc diagnostic information for a given user or device.
Query to retrieve the status and outputs of a remote action.
Remote actions need to be created, configured and activated for the trigger type API. Nexthink library offers a large set of remote actions that you can use for various use cases.