Skip to main content

RMM Integrations

NeoAgent integrates with Remote Monitoring & Management (RMM) tools to automate device management, execute remediation scripts, and enhance ticket resolution.

Supported RMM Tools​

  • Datto RMM
  • N-central
  • N-Sight RMM
  • NinjaRMM

What You Can Automate and Manage with RMM Integrations​

NeoAgent empowers you to automate a wide range of tasks by integrating deeply with your RMM tools:

Intelligent Script-Based Remediation​

  • Automated Script Suggestion & Execution: Neo analyzes PSA tickets and intelligently suggests and executes the most relevant RMM scripts/components from your library to resolve issues. This can be done with or without prior human approval via Human-in-the-Loop workflows.
  • Risk-Aware Execution: Considers RMM component risk levels (e.g., Low, Medium, High) and can be configured with safeguards against automatically running high-risk scripts.
  • Targeted Operations: Ensures scripts run on the correct device linked to a ticket, identified via PSA configuration item IDs or device names discovered by Neo.
  • Execution Monitoring: Neo can monitor script execution (e.g., wait for completion status like "Active", "Completed", "Failed") and use the outcome to drive further workflow actions.

Enhanced Workflow Automation​

  • Multi-Step Problem Solving: If an initial script doesn't resolve an issue, Neo can be configured to attempt alternative scripts or retry execution based on workflow logic.
  • Outcome-Driven Ticket Management: Automatically updates ticket statuses (e.g., "Neo is Working," "Resolved," "Escalated"), assigns tickets to a Neo resource in your PSA, and logs time entries based on RMM script outcomes and duration.
  • Post-Remediation Verification: Workflows can be designed to check ticket status or, in broader L1 agent contexts, await end-user feedback to confirm resolution after a script runs.

RMM Data Utilization​

  • Component Synchronization & Discovery: Neo syncs your RMM scripts/components (including their names, descriptions, categories, variables, and risk levels) into its knowledge base. This data is then vectorized to enable powerful semantic search, allowing Neo to find the best script for a given problem described in a ticket.
  • Device Information Access: Retrieve RMM device details (like RMM device UID, name, and other metadata) by querying your RMM system. This facilitates targeted actions and enriches the information available to Neo.

Data NeoAgent Accesses and Syncs from Your RMM​

  • RMM Components/Scripts: Neo performs a regular sync of your RMM components. This includes their names, descriptions, categories, variables, and risk levels. This data is embedded and stored in a vector database to enable Neo to intelligently search for and suggest the most relevant script to solve a ticket.
  • Device Information: Neo can query your RMM for device details (like RMM device UID, name, and other metadata) based on PSA configuration item IDs or device names found in tickets. This ensures actions are targeted at the correct assets and provides context for automation.

How to Connect​

Connecting NeoAgent to your RMM system allows these advanced automations. The process typically involves providing API credentials via the Neo Dashboard:

  1. Navigate to Integrations: In the NeoAgent Dashboard, go to the "Integrations" section.
  2. Click on the "RMM" tab.
  3. Select Your RMM Tool: Choose your RMM (Datto RMM, N-central, N-Sight RMM, or NinjaRMM) from the list of available RMM integrations.
  4. Provide API Credentials: You will generally need to provide:
    • Your RMM instance URL (the web address you use to access your RMM).
    • An API Key.
    • Depending on the specific RMM system, you might also need to provide an API Secret, a JWT Token, or other specific authentication details required by your RMM's API.
  5. Configure and Activate: Review any specific settings for the integration. Once configured with the necessary credentials, activate the integration. NeoAgent will then begin to sync necessary data (like RMM components) and enable RMM actions within your workflows.
Secure Credentials

For security best practices, generate dedicated API credentials (API user, key, or token) for NeoAgent within your RMM tool.

Ensure these credentials have the necessary permissions for Neo to perform its functions but are restricted according to the principle of least privilege.

Refer to your RMM's official documentation

On the Neo Dashboard, you'll find links to the official documentation for each RMM tool.

Use it to get guidance on creating and managing API access.