Datto RMM: connect, sync devices and alerts, map customers
Enable the API in Datto RMM, generate an Access + Secret key, and pull each customer's device inventory and open-alert counts into Current on a read-only sync. A tenant admin can also set up writes, so a ticket's remediation plan runs components from your own Datto RMM library.
On this page · 8 sections
Connect Datto RMM and the machine behind a ticket, each customer's fleet and patch rate, and the fleet numbers in their business review are already in Current, so your team answers the first questions on a call without opening Datto RMM.
What it does for you
| Where in Current | What you get |
|---|---|
| Service desk tickets | With the service desk and the device register switched on, the ticket's Device panel shows the machine's last check-in, last restart, whether it needs a restart, pending patches, antivirus, who is signed in and its open alerts, with Refresh for a live read and a Datto RMM web remote you start from the ticket. Once alert tickets are on in Settings › Service desk › Alerts, Datto RMM alerts open tickets on the 15-minute check. After a tenant admin sets up Datto RMM writes, a ticket's remediation plan can run a component from your own library, such as restarting a service or clearing temporary files, each step pressed by a person. |
| Company page | The Fleet group under Infrastructure & security shows the customer's devices, the share patched and the machines offline, and the device trend chart tracks the count over the last 90 days. |
| Alerts | Endpoint compliance slipping opens when fewer than 80% of at least 5 reporting machines are patched, or the offline count grows 25% or more on the week before, so your team hears about a slipping estate before the next review. It closes itself when the numbers recover. |
| Reports and dashboards | The Devices compliant, Endpoints per customer and Reactive ticket hours per endpoint tiles count Datto RMM's machines, so a dashboard shows which accounts take the most support time per machine. |
| Business reviews | The fleet chapter states the managed fleet, its patch-compliant share and the machines offline from the synced numbers, so nobody types them into the review by hand. |
| Ask Current | Ask about one customer and Current answers with its device count, patch rate and open device alerts. Ask across your book and it names the companies whose devices have open alerts. |
The sync reads two things out of Datto RMM (each customer's device inventory and their open-alert counts) and attaches them to the matching Current company. The sync only reads: it never changes anything in Datto RMM. The one way Current acts in Datto RMM is a remediation plan step a person runs from a ticket, after the write setup below.
Turn on API access in Datto RMM (one time)
Datto RMM ships with the API switched off. Enabling it and creating a key are two separate admin actions, and both require a Datto RMM Administrator.
- 11 · Enable API AccessIn Datto RMM, go to Setup ▸ Global Settings ▸ Access Control and switch on Enable API Access. Until this is on, every key is rejected. This is the single most common reason a connection fails.
- 22 · Generate the API keys for a userGo to Setup ▸ Users, click the username the integration should run as (a dedicated service account is best practice, not a person who might leave), and choose Generate API Keys. Datto shows an Access key and a Secret key.
- 33 · Copy both keys nowCopy the Access key and the Secret key before you leave the page. The Secret key is not shown again. If you lose it, regenerate the pair (which invalidates the old one).
- 44 · Note your platform/regionYour Datto RMM URL tells you your platform: pinotage, merlot, concord, vidal, zinfandel, or syrah. Current needs it to reach the right API host, and it must match the region you log into.
Connect it in Current
- 1Open the Datto RMM cardIn Current, open Settings › Integrations, press the Datto RMM row in the RMM group, then Manage on its card. Only Tenant Admins can paste credentials.
- 2Pick the platform, paste both keysChoose your platform/region from the dropdown, then paste the Access key into API Key and the Secret key into API Secret Key.
- 3Press Test connectionCurrent fetches a token from Datto live to prove the credentials work before storing anything. A bad key, a disabled API, or the wrong platform is rejected on the spot with the real reason. On success the keys are stored server-side only, the browser never sees them again.
What Current syncs, and how often
The sync runs every 6 hours on its own, and Sync now covers the impatient path. Each run walks your account-wide site list, device list, and open alerts, then writes value-signals, never a raw event firehose.
| Data set | What Current stores | Where it lands |
|---|---|---|
| Customer sites | Each Datto site (your customer) by siteUid and name, its device count, and its open-alert count | The mapped Current company + SBR packs |
| Device inventory | Per device: hostname, device type, operating system, online/last-seen, and a patch-status and antivirus-status summary. No end-user personal data beyond the hostname | The mapped Current company + SBR packs |
| Open alerts | A count of open alerts per customer, aggregated from the account-wide open-alert list | The site's open-alert count on the company + SBR packs |
The sync's read-only guarantee
Every request the sync makes to Datto RMM passes through a read-only guard that only permits the specific GET endpoints above. The endpoints that change things (resolving or muting alerts, moving a device between sites, running a quick job, editing site variables, and especially resetting API keys) are not on the list and are unreachable from the sync, even by a code bug. The sync cannot write to Datto RMM.
Fix it from a ticket: remediation plans
A remediation plan on a service desk ticket can run Datto RMM steps for the ticket's device: a component already in your Datto RMM library (restart an approved service, clean temporary files, flush DNS and renew the IP address, clear print jobs, collect diagnostics, restart the backup agent, scan for threats), resolving the device's monitoring alert, or restarting the device. Each step waits for a person to press Run, and Current reads Datto RMM back to confirm the result. Current never writes or uploads a script.
Nothing runs until a tenant admin sets it up. On the Datto RMM card, Turn on writes walks through creating a separate Current Automation user in Datto RMM and pasting its key (the sync key stays read-only). The setup test runs on a test device you pick, and once it has passed a tenant admin turns Datto RMM's writes on in Settings › Service desk › Actions. A step runs only a component bound to that action; the same page lists each binding and whether it needs review. While the card's Writes row is on Test only, steps run only on the test device you registered. The remediation plans article covers the plan card and its safety stops.
Mapping Datto customers to your companies
In Datto RMM a customer is a Site, identified by its siteUid. Current matches each site to one of your Current companies automatically by normalized name (lowercased, with punctuation and Inc/LLC/Ltd-style suffixes stripped), and links it when exactly one company matches. When two or more of your companies share that name and the names differ only by a suffix like Inc or LLC, Current links the one that is an active customer, or, if none of them is, the one linked to your PSA. Anything still tied or unmatched is left for you.
- Unmatched sites appear on the Datto RMM card's mapping panel, press Map to pick the right Current company by hand.
- A manual mapping is never overwritten by the auto-matcher on a later sync, and neither is a manual unlink.
- Unmapped sites still sync (their devices and alerts are stored), but the data only appears on a company once the site is mapped to it.
When something looks wrong
| What you see | What it means |
|---|---|
| Test connection fails immediately | Usually API access isn't enabled yet (Setup ▸ Global Settings ▸ Access Control ▸ Enable API Access), the platform/region is wrong, or the key pair was mistyped or regenerated. The message names the real reason. |
| Card shows Error mentioning 401 after it was working | The stored key was rejected. The pair was regenerated or revoked in Datto RMM, or API access was turned off. Generate a fresh pair and reconnect. |
| A company shows no Datto data | Its Datto site isn't mapped yet, or the site genuinely has no devices. Check the mapping panel's Unmatched list. |
| Alert counts are missing but devices synced | The open-alerts read hiccuped on that run; devices are treated as load-bearing and alerts as best-effort, so the run still succeeds and alert counts fill in on the next sync. |
| Rate-limited | Current paces itself well under Datto's 600-reads-per-minute limit and backs off when asked. Nothing to do, the sync resumes on its own. |
