Bridge supports connections to several RMM platforms for syncing device and agent data into the platform's CMDB (configuration management). The supported RMM connectors are NinjaOne (Ninja RMM) and Datto RMM. Each uses its own authentication method and pulls device records that can be linked to client companies.
Supported RMM Platforms
| Platform | Auth Method |
|---|---|
| NinjaOne (Ninja RMM) | OAuth 2.0 client credentials (region-specific) |
| Datto RMM | API key + secret |
Setting Up an RMM Connection
The steps are the same for all RMM platforms:
- Open Bridge and go to Connections.
- Click New Connection and select your RMM platform from the list.
- Enter a name for the connection.
- Enter the credentials for your platform (see the table above for what each requires).
- Click Test Connection. Bridge encrypts the credentials and makes a test call to confirm the API responds. Fix any errors shown before proceeding.
- Click Save.
NinjaOne Credentials
NinjaOne requires OAuth 2.0 client credentials. Create an API application in your NinjaOne admin console under Administration > Apps > API and note the Client ID and Client Secret. NinjaOne API endpoints are region-specific; make sure your credentials match the region your NinjaOne instance runs on.
Datto RMM Credentials
Datto RMM uses an API key and secret. Generate them in Datto RMM under Setup > API Keys (admin access required).
What Syncs
RMM sync targets device and configuration item (CI) records. Typical fields that sync include:
- Device name and description
- Linked company (matched via company mappings)
- Operating system, OS version
- Hardware details (manufacturer, model, serial number)
- Online/offline status
- Last seen timestamp
- Agent version
The exact fields available depend on your RMM platform's API. Use Field Mappings to configure which RMM fields map to which CMDB fields in the platform.
Linking Devices to Companies
Device records from the RMM are linked to platform company records via company mappings. After your first RMM sync run, review the company mappings to confirm the RMM's client names have been correctly matched to platform companies. Devices attached to unmatched clients will sync but will not have a company link until the mapping is confirmed.
Sync Frequency
RMM data changes frequently (agent check-ins, status changes). An hourly sync profile works well for most setups. Realtime sync is also available if your RMM supports webhook events — see the Webhooks article for how to configure inbound events from your RMM.
FAQ
Can I connect more than one RMM? Yes. Create a separate connection for each RMM platform. All device records land in the same CMDB, deduplicated by external ID per connection.
Does Bridge sync RMM alerts or monitoring events? The standard device sync covers configuration data, not live alerts. For alert events, set up an inbound webhook to receive alert payloads from your RMM in real time and route them through an Integration Flow.
My NinjaOne test fails with a 401 — what should I check? Confirm the OAuth application in NinjaOne is set to "Machine-to-Machine" (client credentials) and that the Client ID and Secret are entered correctly. Also verify the API application has the scopes needed to read device data.