> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Connect your Remote Monitoring and Management tools to allow Neo to find and run scripts

When you connect your RMM with Neo, Neo gains visibility into all of your scripts and registered devices. Neo can then suggest relevant scripts to technicians working on tickets, or execute scripts directly against devices—monitoring jobs and taking automated actions based on the results.

Neo also links each synced device to its PSA company so reports, automations, and agents know which customer it belongs to — see [Device mapping](/integrations/rmm/device-mapping) for how that works and how to correct it.

You can connect **more than one RMM at the same time** — for example your main RMM plus ScreenConnect, or two RMMs during a migration. Each connected RMM gets its own card on the Integrations page with independent credentials, sync, and last-sync status, and every synced device and script stays tied to the RMM it came from, so agents always act through the right platform.

<Tip>
  Setting up your RMM with Neo is a simple process. You will need to generate API credentials for your RMM and then configure the integration in Neo.
</Tip>

## Use Cases

Neo's RMM integration enables two powerful categories of automation:

### Issue Remediation — Zero Human Touch

Neo can automatically execute scripts to resolve common issues without technician intervention:

* **Software management** — Installing, updating, or repairing applications
* **Device maintenance** — Rebooting devices, clearing caches, removing temp files
* **Service management** — Starting, stopping, or restarting services and processes
* **Any typical RMM task** — If you have a script for it, Neo can run it

<Info>
  You control the level of automation. Neo can either execute scripts automatically or request approval from a technician before taking action.
</Info>

After executing a script, Neo monitors the job and takes intelligent follow-up actions based on the result:

* **Success** — Close the ticket and notify the end user
* **Failure** — Escalate to a technician or try an alternative remediation
* **Partial success** — Document findings and recommend next steps

### Revenue & Opportunity Creation

Neo can identify upsell and service opportunities by combining RMM data with intelligent automation.

<AccordionGroup>
  <Accordion title="Example: Disk space alert triggers upgrade opportunity">
    When a device triggers an alert for 95% disk usage:

    1. Neo receives the ticket and runs a cleanup script
    2. Neo waits for the result (disk usage drops to 90%)
    3. Neo checks the device age from your RMM
    4. If the device is over 5 years old, Neo automatically messages the customer:

    > "Your device is over 5 years old and running low on storage. Would you like a quote for an upgrade?"

    This transforms a routine maintenance ticket into a potential hardware sale.
  </Accordion>

  <Accordion title="Example: Recurring issues trigger service review">
    When Neo detects a pattern of repeated issues on a device:

    1. Neo resolves the immediate issue
    2. Neo analyzes ticket history for the device
    3. Neo identifies the recurring pattern
    4. Neo reaches out to the customer suggesting a proactive maintenance plan or device refresh
  </Accordion>
</AccordionGroup>

<Tip>
  Configure Neo's automation rules to match your business processes. You decide which actions Neo takes automatically and which require human approval.
</Tip>

## Supported RMM Platforms

Select your RMM platform to view the complete setup guide:

<CardGroup cols={2}>
  <Card title="ConnectWise Automate" icon="gear" href="/integrations/rmm/connectwise-automate/overview">
    Connect using API credentials with dedicated user class permissions.
  </Card>

  <Card title="ConnectWise Asio" icon="diagram-project" href="/integrations/rmm/connectwise-rmm/overview">
    Connect using API access credentials. Script suggestions available; execution coming soon.
  </Card>

  <Card title="Datto RMM" icon="shield" href="/integrations/rmm/datto/overview">
    Integrate using API key and secret with administrator security levels.
  </Card>

  <Card title="N-Able N-Sight" icon="eye" href="/integrations/rmm/n-able-n-sight/overview">
    Connect using API key authentication with monitoring permissions.
  </Card>

  <Card title="N-Able N-Central" icon="server" href="/integrations/rmm/n-able-n-central/overview">
    Integrate using role-based permissions and dedicated API user.
  </Card>

  <Card title="NinjaOne" icon="bolt" href="/integrations/rmm/ninjaone/overview">
    Connect using secure OAuth authentication flow—no API keys required.
  </Card>

  <Card title="Kaseya VSA X" icon="key" href="/integrations/rmm/vsax/overview">
    Connect using a Third-Party Token (Token ID + Token Secret) from your VSA X tenant.
  </Card>
</CardGroup>

## Quick Setup Summary

| RMM Platform         | Authentication Method           | Typical Setup Time |
| -------------------- | ------------------------------- | ------------------ |
| ConnectWise Automate | User Class + API Credentials    | 10-15 minutes      |
| ConnectWise Asio     | Client ID + Client Secret       | 5-10 minutes       |
| Datto RMM            | API Key + Secret                | 5-10 minutes       |
| N-Able N-Sight       | API Key                         | 5-10 minutes       |
| N-Able N-Central     | Role-Based API User             | 10-15 minutes      |
| NinjaOne             | OAuth (No API Keys)             | 2-5 minutes        |
| Kaseya VSA X         | Third-Party Token (ID + Secret) | 5-10 minutes       |

<Tip>
  All integrations can be configured from the [Neo Agent Dashboard](https://dashboard.neoagent.io/integrations). Navigate to the RMM section and select your platform to begin.
</Tip>