RMM Integrations
ConnectWise Automate, Zabbix, ScreenConnect and Azure Resource Manager connected to one asset register, one alert queue and one ticket — with remote actions from the ticket a technician is already reading.
How Solidlio helps
Solidlio imports the devices your RMM manages as assets, mapped into the right client organization by Automate client, Automate group or Zabbix host group. Alerts arrive as monitoring records, deduplicate onto an already-open ticket rather than opening a second one, and are suppressed while a change-management maintenance window is in effect. A technician acts on the machine — command, script, reboot, remote session — from the ticket. Every action is audited.
Capabilities
| Capability | What it does |
|---|---|
| Device discovery | Imports Automate computers, Zabbix hosts and Azure resources as assets |
| Multi-tenant routing | Maps Automate clients and groups, and Zabbix host groups, to individual client organizations |
| Software inventory | Imports the installed-software register from Automate, resolving shared vendors safely |
| Drive and patch metadata | Records total storage across all volumes, plus patch status |
| Alert ingestion | Polls or receives alerts, deduplicating onto an existing open ticket |
| Alert-to-ticket | Raises a ticket through the full pipeline — queue routing, SLA assignment and queue notification |
| Maintenance suppression | Suppresses alerts during a change-management maintenance window, and pushes the window to Zabbix |
| Auto-resolve | Closes the linked ticket when the underlying alert clears |
| Remote actions | Command, script, reboot and shutdown via Automate; control, wake, message and lock via ScreenConnect |
| Ad-hoc support sessions | A technician starts an attended session from a ticket, the customer is emailed the join link, and each technician manages the sessions they opened. Provider-agnostic — ScreenConnect today, any remote tool later |
| Remote session time capture | Session time is recorded automatically and offered as a pre-filled, editable time entry on the ticket — never logged without a click, and never suggested when the number would be misleading |
| Azure cost ingestion | Imports Cost Management data alongside the resource inventory |
| Sync history | Records every run with counts, duration, status and errors |
Built for MSPs and their clients
One Automate server or one Zabbix instance serves every client you manage. Mapping is what turns that into per-tenant data rather than one shared pile.
| Organization | MSP | |
|---|---|---|
| Connecting the RMM | — | Connects and owns the credentials |
| Device attribution | Sees only its own assets | Maps each Automate client / Zabbix host group to a client organization |
| Alerts | Sees alerts for its own machines | Sees alerts across every managed client |
| Remote actions | — | Runs commands and remote sessions, with every action audited |
How it works
- Connect — enter the RMM’s URL and credentials, or grant admin consent for Azure. Credentials are encrypted at rest and never displayed again.
- Map — Automate clients or groups, and Zabbix host groups, to the client organizations they belong to.
- Discover — devices import as assets, matched to existing assets by serial, hostname or MAC within that organization, never across tenants.
- Alert — alerts arrive on a schedule or by inbound webhook, deduplicate onto an open ticket, and raise a new one through the normal ticket pipeline when there is none.
- Act — a technician runs a command or opens a remote session from the ticket or the asset. The action is recorded in the audit trail.
Provider coverage
| Provider | Status |
|---|---|
| ConnectWise Automate | Ships — the fullest integration: inventory, software, drives, patches, alerts, remote actions |
| Zabbix | Ships — host discovery, alert ingestion, inbound webhook, maintenance push. Version-aware auth, including the Bearer transport Zabbix 7.2 requires |
| ConnectWise ScreenConnect | Ships — sessions imported as assets with company → customer placement, online status, remote control, commands with output, wake, message, lock, support sessions |
| Azure Resource Manager | Ships with limits — resource inventory, decommission detection, cost ingestion |
| Datto RMM, NinjaOne | Roadmap. No integration exists; setup is refused |
Honest limits
- Azure has no subscription-to-client mapping. Every Azure resource lands in the connecting organization, so an MSP cannot yet attribute Azure resources to individual clients the way it can with Automate and Zabbix.
- ScreenConnect has its own management page in both portals: companies → customers, site placement, a machines list with overrides, sync history and settings.
- Per-volume drive detail is available live on the Automate device page, not stored on the asset — the asset carries the total.
Security
- Requests to self-hosted RMM servers pass an SSRF guard that pins the connection to the address it validated, so a hostname cannot be repointed at an internal address between the check and the request. Private, reserved, loopback, link-local and cloud-metadata addresses are refused.
- Every device, session and inventory read requires organization administrator.
- Every remote action requires organization administrator and writes an audit record naming the actor, the asset and the action.
- Remote session launch URLs are restricted to sessions the tenant’s own integration knows about.
- Alerts and asset mappings are tenant-pinned; a device can never be re-parented into another customer’s organization by a stale external id.
Plans and access
Availability depends on your plan, role and account permissions. Capacity limits and service terms apply. Compare current plans and integration requirements, or ask us about your setup.