> ## 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 Syncro's RMM side to Neo Agent for device, software, patch and alert context — and what Syncro's API cannot do

Syncro is one product with two surfaces: the PSA (tickets, customers, invoicing) and the RMM (managed devices, alerts). Neo treats them as **two integrations**, because an MSP can run Syncro RMM alongside a completely different PSA.

<Info>
  **If you have already connected the Syncro PSA, the RMM is probably connected too.** Connecting the PSA with a token that can read assets connects the RMM for you — see [Connecting to Neo Agent](/integrations/rmm/syncro/connecting-to-neo). You only need that page if you want the RMM to use a different token.
</Info>

## What Neo Can Do with Syncro RMM

Neo reads device, software, patch and alert data, and — where you allow it — acts on alerts. Every area is gated by the permission groups you configure in Agent Settings.

<AccordionGroup>
  <Accordion title="Devices">
    * **Device lookup** — find managed devices, read their detail (operating system, serial, model, memory, last user, agent version)
    * **Company mapping** — each device is matched to the right customer automatically. On a tenant that runs Syncro for *both* PSA and RMM this is exact rather than a name match, because it is the same customer record on both sides
    * **Write** — create an asset, or update its name, customer, serial, type and properties (opt-in per the Devices permission group)
  </Accordion>

  <Accordion title="Software & Patches">
    * **Installed applications** — the software inventory for a device, read on demand
    * **Patch status** — Windows patch state for a device

    <Note>
      Patch data is **Windows only**. A Mac or Linux device returns nothing here — that is Syncro's behaviour, not a gap in Neo.
    </Note>
  </Accordion>

  <Accordion title="Alerts">
    * **Read** — query RMM alerts and the device that raised each one
    * **Write** — mute an alert, raise a new one, or resolve one

    <Warning>
      Resolving an alert clears it from your technicians' console and Neo cannot undo it, so it sits behind its own **Resolve** toggle and always asks for technician approval — even when the rest of the group is set to autonomous.
    </Warning>
  </Accordion>
</AccordionGroup>

## What the Syncro API Cannot Do

Read this section before comparing Syncro RMM against another RMM you use. These are limits of **Syncro's own API**, not features Neo has not built yet — Neo cannot work around them, and no setting will turn them on.

### Scripts: Neo cannot run or report on them

**Syncro's API exposes no way to run a script that Neo can act on, and no way to query one.**

* There is **no endpoint to list scripts**, so Neo cannot show you which scripts exist or let an agent choose one.
* There is **no endpoint to read a script's result** — no output, no exit code, no run history.
* Syncro does have a single "schedule a script" call, but it returns nothing beyond an acknowledgement: no run identifier, and no way to ask later what happened.

Because Neo could never tell you whether a script succeeded, what it printed, or even that it finished, **script execution is not offered for Syncro at all**. Neo will say so plainly rather than start something it cannot report on. If a ticket needs a script, run it from the Syncro console.

<Warning>
  This is the biggest difference from ConnectWise Automate, NinjaOne, Datto and the rest, where Neo can run a script and read its output. If your automations depend on that, Syncro RMM cannot replace them today.
</Warning>

Syncro lists script execution via the public API as shipping soon on their [public roadmap](https://syncrosecure.com/platform/roadmap/). Neo will support it once the API can report what a run did.

### Other limits

* **No webhooks for RMM alerts.** Nothing pushes an alert to Neo — an agent reads them when it needs them, so a new alert does not on its own start a workflow.
* **No recurring schedules** through the API.

## Available Actions

| Category    | Actions                                                                                | Status                                                  |
| ----------- | -------------------------------------------------------------------------------------- | ------------------------------------------------------- |
| **Devices** | Find devices, read device detail, read installed applications and Windows patch status | Available (read)                                        |
| **Devices** | Create an asset; update name, customer, serial, type, properties                       | Available (read/write)                                  |
| **Alerts**  | Read alerts and the device that raised them                                            | Available (read)                                        |
| **Alerts**  | Mute an alert, raise a new one                                                         | Available (read/write)                                  |
| **Alerts**  | Resolve an alert                                                                       | Available (read/write + approval)                       |
| **Scripts** | Run a script, read script output, list scripts                                         | **Not available** — Syncro's API cannot report a result |

<Tip>
  Write access is opt-in per area. In Agent Settings → Permission Groups, set the Syncro RMM **Alerts** group to **Read & Write** to allow muting and raising alerts (enable **Resolve** separately), or the **Devices** group to allow asset writes.
</Tip>

## Prerequisites

* A Syncro account with the RMM in use and at least one agent installed
* A Syncro API token whose permissions include **Assets** — the same token used for the [Syncro PSA integration](/integrations/psa/syncro/overview) is fine, and is what Neo uses by default