All Integrations
N1
LivePro

NinjaOne RMM

RMMBuilt by cAND/or REST API · Key Pair Setup: ~10 minutes

Full bidirectional sync with NinjaOne. Alerts auto-create tickets, assets sync, and Helix can trigger automations and device queries.

Required Credentials

3 fields
Client ID
Required

Found in NinjaOne: Administration → Apps → API → Client Credentials → Create Credentials

Format:helix-integration
Enables →
alert_to_ticketasset_syncrun_automationdevice_query
Client Secret
RequiredSecret

Generated alongside the Client ID in NinjaOne Administration → Apps → API. Store it immediately — it is shown only once.

Format:••••••••••••••••••••••••••••••••
Enables →
alert_to_ticketasset_syncrun_automationdevice_query
Instance URL
Optional

Optional. Your NinjaOne instance base URL. Defaults to https://app.ninjarmm.com if not specified.

Format:https://app.ninjarmm.com
Enables →
alert_to_ticketasset_syncrun_automationdevice_query

Data Flow

4 capabilities
Helix initiates
Vendor notifies Helix
Both directions
// Helix → VendorHelix initiates

Run Automation from Helix

Helix → Vendor

Trigger NinjaOne scripts from a ticket

ProtocolREST API call
TriggerTech clicks Run Automation on a Helix ticket and selects a NinjaOne script
AuthClient ID + Client Secret
You configureAutomation scripts must already exist in NinjaOne. Helix pulls your script catalog from NinjaOne on connection.
Helix doesAvailable NinjaOne automations appear in the ticket action menu. Execution results are logged as a ticket note.

Query Device Status

Helix → Vendor

Pull live device health into Helix

ProtocolREST API call (read-only)
TriggerTicket opened against a company with a linked NinjaOne device, or tech clicks Refresh Device
AuthClient ID + Client Secret
You configureNo configuration needed in NinjaOne.
Helix doesDevice status (online/offline, CPU, memory, last patch) surfaces in the Helix ticket sidebar in real time.
// Vendor → HelixVendor notifies Helix

RMM Alert to Ticket

Vendor → Helix

NinjaOne alerts automatically create Helix tickets

ProtocolWebhook — NinjaOne posts alerts to Helix
TriggerAlert threshold exceeded, device offline, patch failure, disk space critical
AuthWebhook signature verification
You configureIn NinjaOne: Administration → Webhooks → Add Webhook. Set the URL to your Helix inbound alert endpoint (displayed in App Marketplace → NinjaOne → Setup). Select event types: device offline, alert triggered, alert resolved.
Helix doesHelix parses the NinjaOne payload, matches the device to a Helix asset, and creates a ticket assigned to the on-call technician. Alert-resolved events auto-close the ticket if still open.
// BidirectionalBoth sides communicate

Device / Asset Sync

Bidirectional

Device records stay synchronized

ProtocolREST API (both directions)
TriggerScheduled sync every 4 hours. Manual sync available via Sync Now in App Marketplace.
AuthClient ID + Client Secret (OAuth 2.0 client credentials flow)
You configureNo additional configuration needed in NinjaOne beyond the API credentials.
Helix doesNinjaOne devices become Helix assets. Device attributes (OS, last seen, warranty) are pulled from NinjaOne and stored on the Helix asset record.

Ready to connect?

Log into Helix and open App Marketplace to configure this integration.

Open Helix