Nine Minds Logo

Navigation

10.15. NinjaOne RMM Integration: Sync Devices, Alerts, and Organizations

Connect NinjaOne RMM to AlgaPSA to synchronize organizations, map devices, receive alerts, monitor fleet compliance, and automate alert-to-ticket workflows.

10.15. NinjaOne RMM Integration: Sync Devices, Alerts, and Organizations
Connect NinjaOne RMM to AlgaPSA to synchronize organizations, map devices, receive alerts, monitor fleet compliance, and automate alert-to-ticket workflows.
10. SettingsUpdated: 7/5/2026

This guide walks through connecting your NinjaOne RMM account to AlgaPSA. Once connected, NinjaOne organizations map to your clients, devices sync into Assets, alerts become tickets through your alert rules, and a fleet compliance dashboard summarizes device health inside the PSA.

NinjaOne is an Enterprise Edition integration. For the model all RMM integrations share, see How RMM Integrations Work in AlgaPSA. For alert rules, maintenance windows, and polling, see Turn RMM Alerts into Tickets.

Getting Started

  1. Navigate to Settings > General > Integrations > RMM in AlgaPSA and select NinjaOne.
  2. Review the Setup Instructions displayed on the NinjaOne integration page.

Create an API Application in NinjaOne

  1. Log into your NinjaOne dashboard.
  2. Navigate to Administration > Apps > API.
  3. Click the + Add client app button.
  4. Fill in the Application Details:
    • Application platform: Select "Web (PHP, Java, .Net Core, etc.)".
    • Name: Enter "AlgaPSA" (or your preferred name).

Configure the API Application

  1. Add the Redirect URI:

    • Click the Redirect URIs dropdown.
    • Enter the callback URL shown in AlgaPSA's setup instructions, for example: https://algapsa.com/api/integrations/ninjaone/callback
    • Press Enter to add the URI.

  2. Select the required Scopes:

    • Monitoring: Grants read-only access to monitoring data and organization structure.
    • Management: Allows modification of device and organization information.

  3. Check the Allowed grant types:

    • Authorization code: Required for OAuth authentication.
    • Client credentials: Enables machine-to-machine authentication.
    • Refresh token: Allows token renewal without re-authentication.

  4. Click Add to create the application.

Note: After clicking Add, you will see the Client ID and Client Secret. This is the only time you will be able to view the Client Secret, so make sure to copy it immediately.

Copy API Credentials

  1. Copy the Client ID by clicking the copy icon next to it.
  2. Copy the Client Secret by clicking the copy icon next to it.

Note: Store these credentials securely. If you lose the Client Secret, you will need to generate a new one.

Configure AlgaPSA

  1. Navigate to Settings > Integrations > RMM > NinjaOne in AlgaPSA.
  2. Paste the Client ID from NinjaOne into the Client ID field.
  3. Paste the Client Secret from NinjaOne into the Client Secret field.
  4. Click Save Credentials.

Connect to NinjaOne

  1. Select your NinjaOne region from the Region dropdown (US, US2, EU, OC, or CA).
  2. Click Connect to NinjaOne.

Authorize Access

  1. Review the requested permissions on the NinjaOne authorization page:

    • Monitoring: Grants read-only access to monitoring data and organization structure.
    • Management: Allows modification of device and organization information.
    • Offline Access: Access to your NinjaRMM account even when you are offline.

  2. Check the Remember my decision checkbox (optional).

  3. Click Authorize to grant AlgaPSA access to your NinjaOne account.

Sync Organizations and Devices

  1. Once connected, you will see the status panel report "Connected to NinjaOne" with your instance URL, organization count, and device count.

  2. Click Sync Organizations to import your NinjaOne organizations.

  3. Map your NinjaOne organizations to AlgaPSA clients in the Organization Mappings section:

    • Select the corresponding AlgaPSA client from the dropdown for each NinjaOne organization.
    • Enable Auto-Sync to automatically keep data synchronized.
    • Enable Auto-create tickets for organizations whose alerts should produce tickets.
    • Optionally set a Default Contact using the contact picker — this contact is attached to alert-created tickets from this organization and triggers the Ticket Created client email when a ticket opens. AlgaPSA falls back to the client's primary contact if the field is left blank.

  4. Click Sync Devices to import devices from your mapped organizations.

Monitor Fleet Compliance

Once devices have synced, the Fleet Compliance dashboard summarizes device health across your fleet:

  • Devices Online / Offline — connectivity at a glance.
  • Patches Pending / Patches Failed — patch posture, with Sync Patches to refresh.
  • Devices with Alerts — endpoints that currently need attention.
  • Sync Software — refresh the software inventory on synced assets.

Automate Alerts into Tickets

NinjaOne alerts reach AlgaPSA two ways, and both feed the same pipeline:

  • Webhooks deliver alerts in real time as soon as you connect.
  • Alert Polling fetches active alerts on a schedule (5–60 minutes) and catches anything a webhook missed. It also resolves alerts that cleared in NinjaOne, closing their untouched tickets.

The Alert Automation section at the bottom of the NinjaOne panel holds your alert rules, maintenance windows, and the polling toggle. Rules route alerts onto boards with severity-mapped priorities, repeat firings stack onto the existing ticket instead of duplicating it, and closing a ticket can reset the alert in NinjaOne. See Turn RMM Alerts into Tickets for the full guide.

Disconnecting

Disconnect stops device synchronization and alert ingestion and removes your stored API credentials. Organization mappings are preserved, so reconnecting later does not mean re-mapping every client.

The NinjaOne integration is now complete. Devices and organizations stay synchronized, alerts become routed tickets, and your team manages RMM work without leaving AlgaPSA.

Related topics