Connect NinjaOne
NinjaOne is an RMM and PSA platform for IT service providers. DomainWarn connects through an app you create in your NinjaOne account and can then do four things: create tickets for incidents, show the domain status per client in NinjaOne, take over the organizations from NinjaOne as clients and export clients to NinjaOne as organizations. You switch on each feature separately under “Features”; after connecting, everything is off. It is included from the Agency plan.
In NinjaOne, under Administration › Apps › API › Client App IDs, add a new app: application platform “Web”, scopes “Monitoring” and “Management”, grants “Authorization Code” and “Refresh Token”. As redirect URI, enter the address DomainWarn shows under Settings › Integrations › NinjaOne (https://app.domainwarn.com/integrations/ninjaone/callback). Client ID and client secret go into DomainWarn, together with the region of your instance (app, us2, eu, ca or oc.ninjarmm.com). “Connect with NinjaOne” leads to the NinjaOne sign-in; after you confirm, the connection is in place.
DomainWarn stores client secret and tokens encrypted and renews the access token itself. If the app is deleted in NinjaOne or the access revoked, the error shows on the connection and “Reconnect” restores it. “Disconnect” deletes credentials, mappings and ticket references; clients in DomainWarn and tickets in NinjaOne remain.
NinjaOne is in beta: the connection follows the official NinjaOne Public API 2.0 but is new. Check the first tickets, mappings and exports, and let us know if anything looks off.
Map and import organizations
Under “Organizations and clients” you see every organization from NinjaOne. Map it to an existing DomainWarn client; this always works, because tickets and domain status need the mapping. With the feature “Import customers from NinjaOne” you can also add organizations as new clients – one by one or with “Add all unmapped as clients”. If a client with exactly that name exists, it is mapped instead of created twice; importing again creates no duplicates. Nothing is ever deleted, neither in DomainWarn nor in NinjaOne.
A client belongs to at most one NinjaOne organization. If you rename an organization in NinjaOne, the name follows the next time you open the list. If it disappeared there, the mapping stays with the note “No longer present in NinjaOne” until you unmap it.
Tickets for incidents
Pick the ticket form, the status of new tickets and – if you like – the status on resolution, plus the ticket priority and severity for each DomainWarn severity. Then add a “NinjaOne” channel under notifications; like every channel it has a minimum severity and follows the notification rules.
A new incident opens a ticket on the NinjaOne organization of the client the domain belongs to; domains without a mapped client use the chosen default organization, without one no ticket is created. Escalation and reminders are added as internal comments, on resolution DomainWarn comments and sets the chosen status. There is exactly one ticket per incident – even if a notification is retried or several incidents arrive as a summary. The test send checks connection, form and status without creating a ticket.
Domain status in NinjaOne
Create an organization field of type “WYSIWYG” in NinjaOne, for example domainwarnStatus, with API permission “Read/Write”, and enter its name in DomainWarn. With “Send domain status”, DomainWarn writes an overview into it daily and shortly after every new or resolved incident for each mapped organization: a table with every domain, its state as a coloured badge (healthy, warning, critical), the expiry date and the number of open incidents, followed by the open incidents – each linked to the dashboard. Technicians see right on the client in NinjaOne how its domains are doing.
If the field is a multi-line text field, DomainWarn writes the same overview without formatting and points this out in the settings; after switching the field to WYSIWYG, the next sync brings the table. If the field is missing or the app may not write it, NinjaOne refuses and the error shows on the connection. “Send now” starts the sync immediately.
See also: Notification channels · Clients
Export clients to NinjaOne
With the feature “Export customers to NinjaOne” the export card appears. It lists every active client without a NinjaOne organization and creates them as organizations in NinjaOne with one click. If a free organization with the same name (ignoring case) already exists there, it is mapped instead of created twice. Archived clients are left out, nothing is deleted.
Optionally pick a template organization: new organizations then copy its settings in NinjaOne. The export runs in the background, for many clients in several passes, because NinjaOne limits calls per minute. The result (created, mapped, failed) shows in the card afterwards. If the app may not create organizations (scope “Management”), the export stops with that note.