npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@ev1lc0rp/n8n-nodes-ninjaone

v0.12.0

Published

Professional NinjaOne RMM integration for n8n with complete ticketing and device management

Readme

n8n-nodes-ninjaone

Professional NinjaOne RMM integration for n8n with complete ticketing and device management capabilities.

This community node provides comprehensive integration with the NinjaOne Remote Monitoring and Management (RMM) platform, enabling automated workflows for IT service management, device monitoring, and helpdesk operations through n8n.

Installation

Follow the community node installation guide and install the package:

npm install @ev1lc0rp/n8n-nodes-ninjaone

Current Status

✅ Working Features:

  • Complete OAuth2 authentication with regional endpoint support (app, us2, eu, oc, ca)
  • Full CRUD ticket operations with real API field mapping based on production data
  • Partial ticket updates (only supplied fields are sent)
  • Comprehensive device management operations (get, list, activities, alerts, custom fields, etc.)
  • Device control shipped in 0.5+: reboot, run script, Windows service control, dashboard URL
  • Device control shipped in 0.8.0: maintenance windows, device owner, OS and software patch apply/scan, Windows service configuration, and device approval
  • Organization lifecycle shipped in 0.9.0: locations, installer URL generation, and partial organization update
  • Policy coverage shipped in 0.10.0: policy list, custom-field conditions, Windows-event conditions, and organization policy assignment
  • Document template lifecycle: list, get, create, update, delete, archive, and restore (single and bulk). List filters are templateName and includeTechnicianRoles. Bulk archive and restore send a raw integer array.
  • Checklist template lifecycle shipped in 0.11.0: list, create, update, delete, archive, and restore
  • Organization checklist archive and restore shipped in 0.11.0 (clientChecklistIds)
  • Organization checklist list, get, create, update, delete, create-from-templates, signed URLs, and promotion shipped in 0.12.0
  • Asset tag list, create, update, delete, merge, and device tag assignment shipped in 0.12.0
  • Vulnerability scan group list, get, and CSV upload shipped in 0.12.0
  • All ticketing workflows: Create, Read, Update, Comment with proper field validation
  • Ticket reference reads (0.7.0): log entries, attributes, contacts, ticket forms, statuses, and app user contacts
  • Severity levels: NONE, MINOR, MODERATE, MAJOR, CRITICAL (matches production API)
  • Status management: New (1000), Open (2000), Waiting for Customer (3000), Hold (4000)
  • Ticket types: PROBLEM, TASK, QUESTION support
  • Time tracking and organization assignment capabilities
  • Board-based ticket listing with proper POST method implementation

🚧 In Development:

  • Approach A domain waves are complete in 0.12.0. The pending section below records what shipped, what the Public API does not have, and what is deferred.
  • Webhook, knowledge base, organization document, and backup workflows are deferred. They are Public API tags that were not on the domain-wave checklist.

❌ Known Issues:

  • None currently identified. Note: if you upgraded from a version that defaulted the Base URL to api.ninjaone.com, update your credential to your real regional host (see Authentication).

📋 Roadmap:

  • Deferred outside Approach A: backup, reporting and analytics, organization documents, knowledge base articles, and webhooks. None of these were remaining Wave 6 endpoints.

Pending API Method Coverage Tasks

Approach A is complete in 0.12.0. The lists below record shipped operations, paths the Public API 2.0.9-draft does not have, and tags deferred outside that program. There is no unchecked item left from the domain-wave checklist.

Ticketing Endpoints

Shipped in 0.7.0. Verified against NinjaOne Public API 2.0 (apidocs-beta) on 2026-09-24. None of these paths were removed.

  • [x] Expose GET /v2/ticketing/ticket/{ticketId}/log-entry for ticket history retrieval and add matching Jest coverage. Optional query fields: type, createTime, anchorId, pageSize.
  • [x] Expose GET /v2/ticketing/attributes to surface ticket attribute metadata with schema tests.
  • [x] Add contact directory operation for GET /v2/ticketing/contact/contacts. The Public API returns the full contact list and documents no pagination parameters, so the node does not send page or cursor query parameters.
  • [x] Support GET /v2/ticketing/ticket-form/{id} for single ticket form lookups and validate required parameters in tests.
  • [x] Support GET /v2/ticketing/ticket-form for listing ticket forms with coverage mirroring board listing tests.
  • [x] Add reference data operation for GET /v2/ticketing/statuses with enumeration validation tests. Status records use statusId, name, displayName, and parentId and are tenant-defined.
  • [x] Surface technician lookup via GET /v2/ticketing/app-user-contact and assert query parameter mapping in tests (pageSize, anchorNaturalId, searchCriteria, userType, clientId).

Client Credentials with the monitoring scope is enough for these reads. Authorization Code also works. Ticket create, update, and comment still require Authorization Code. HTTP 401 or 403 means the token, scope, or regional host is wrong.

Policy Condition Endpoints

Shipped in 0.10.0 where the Public API still has the operation. Verified against NinjaOne Public API 2.0.9-draft (apidocs-beta, NinjaRMM-API-v2.yaml) on 2026-09-24.

  • [x] Policy listing: GET /v2/policies (getAll). The Public API returns the full list and documents no pagination parameters, so none are sent.
  • [x] Custom-field conditions: GET and POST /v2/policies/{policy_id}/condition/custom-fields (getCustomFieldConditions, createCustomFieldCondition) and GET /v2/policies/{policy_id}/condition/custom-fields/{condition_id} (getCustomFieldCondition). matchAll and matchAny are sent only when that list has entries. Each entry sends fieldName, operator, and value. Operators are EQUALS, NOT_EQUALS, LESS_THAN, LESS_OR_EQUAL_THAN, GREATER_THAN, GREATER_OR_EQUAL_THAN, IS_NOT_NULL, CONTAINS, CONTAINS_NONE, and CONTAINS_ANY.
  • [x] Windows-event conditions: GET and POST /v2/policies/{policy_id}/condition/windows-event (getWindowsEventConditions, createWindowsEventCondition) and GET /v2/policies/{policy_id}/condition/windows-event/{condition_id} (getWindowsEventCondition). Create requires source and eventIds.
  • [x] Delete condition: DELETE /v2/policies/{policy_id}/condition/{condition_id} (deleteCondition). This path deletes one condition of any type.
  • [x] Organization policy mapping: PUT /v2/organization/{id}/policies (assignOrganizationPolicies). The JSON body is an array of nodeRoleId and policyId. The response is the affected device IDs.

Skipped after checking Public API 2.0.9-draft:

  • Pagination parameters on GET /v2/policies are absent, so the node does not send pageSize, after, or cursor.
  • PUT /v2/policies/{policy_id}/condition/{condition_id} is absent, so condition update is not implemented.
  • DELETE /v2/policies/{policy_id}/condition/custom-fields/{condition_id} and DELETE /v2/policies/{policy_id}/condition/windows-event/{condition_id} are absent. Delete uses the shared condition path above.
  • POST /v2/policies creates a policy (mode NEW, CHILD, or COPY) and was not on the pending checklist, so it is not in 0.10.0.

getAll uses Client Credentials with the monitoring scope. Condition reads and writes, and organization policy assignment, are tagged management and use Client Credentials with the management scope. Monitoring alone is read-only for those calls. HTTP 401 or 403 means the token, scope, or regional host is wrong.

Device Control Endpoints

Shipped in 0.5+ (not pending): POST /v2/device/{id}/reboot/{mode}, POST /v2/device/{id}/script/run, POST /v2/device/{id}/windows-service/{serviceId}/control, and GET /v2/device/{id}/dashboard-url. Listing OS/software patches and patch installs is also shipped.

Shipped in 0.8.0. Verified against NinjaOne Public API 2.0.9-draft (apidocs-beta, NinjaRMM-API-v2.yaml) on 2026-09-24.

  • [x] Maintenance windows: PUT /v2/device/{id}/maintenance (scheduleMaintenance) and DELETE /v2/device/{id}/maintenance (cancelMaintenance). disabledFeatures is ALERTS, PATCHING, AVSCANS, or TASKS. start and end accept an ISO-8601 date-time or epoch milliseconds. There is no GET on this path and no separate start/stop verb. Status is maintenance.status on GET /v2/device/{id} (PENDING, IN_MAINTENANCE, FAILED).
  • [x] Windows service configuration: POST /v2/device/{id}/windows-service/{serviceId}/configure (configureWindowsService). startType is AUTO_START, AUTO_START_DELAYED, BOOT_START, DEMAND_START, DISABLED, or SYSTEM_START. userName is sent only when set.
  • [x] Device owner: POST /v2/device/{id}/owner/{ownerUid} (setDeviceOwner) and DELETE /v2/device/{id}/owner (removeDeviceOwner). The Public API security on both calls is the management scope. Delete does not take an owner UID in the path.
  • [x] OS and software patch apply/scan: POST /v2/device/{id}/patch/os/apply, POST /v2/device/{id}/patch/os/scan, POST /v2/device/{id}/patch/software/apply, and POST /v2/device/{id}/patch/software/scan. The Public API documents no body, query, concurrency, or schedule parameters, so none are sent. Success is HTTP 204. HTTP 400 means the device is not applicable.
  • [x] Device approval: POST /v2/devices/approval/{mode} (approveDevices). Requirements are confirmed: mode is APPROVE or REJECT, and the JSON body is { "devices": [integer IDs] }.

These writes use Client Credentials with the management scope. Monitoring alone is read-only. The control scope is remote access, not these operations. HTTP 401 or 403 means the token, scope, or regional host is wrong.

Organization Lifecycle & Installer Endpoints

Shipped in 0.9.0 where the Public API still has the operation. Verified against NinjaOne Public API 2.0.9-draft (apidocs-beta, NinjaRMM-API-v2.yaml) on 2026-09-24.

  • [x] Location listing: GET /v2/organization/{id}/locations (getLocations). The Public API returns the full list for one organization and documents no pagination parameters, so none are sent. GET /v2/locations paginates locations for every organization with pageSize and after; that endpoint is not this operation.
  • [x] Installer generation and retrieval: POST /v2/organization/generate-installer (generateInstaller) and GET /v2/organization/{id}/location/{location_id}/installer/{installer_type} (getInstaller). Both return JSON with a url property. Public API 2.0.9-draft does not return an installer binary, so the node does not use a binary property. usageLimit is read-only and is not sent. content.nodeRoleId is sent only when set and otherwise defaults to auto. Installer types are WINDOWS_MSI, WINDOWS_ARM64_MSI, MAC_DMG, MAC_PKG, LINUX_DEB, LINUX_RPM, LINUX_ARM64_DEB, LINUX_ARMV7A_DEB, LINUX_ARM64_RPM, and LINUX_ARMV7A_RPM.
  • [x] Organization update: PATCH /v2/organization/{id} (update). Partial fields are name, description, userData, and nodeApprovalMode (AUTOMATIC, MANUAL, REJECT).

Skipped after checking Public API 2.0.9-draft:

  • PUT /v2/organization/{id} is not in the API. The update verb is PATCH.
  • DELETE /v2/organization/{id} is not in the API, so organization deletion is not implemented.
  • POST /v2/organization/archive and POST /v2/organization/restore archive and restore organization checklists (clientChecklistIds), not organizations. They shipped on the Organization Checklist resource in 0.11.0.
  • PUT /v2/organization/{id}/policies changes node-role policy mappings and is not part of the organization update body. It shipped on the Policy resource in 0.10.0 as assignOrganizationPolicies.

getLocations uses Client Credentials with the monitoring scope. generateInstaller, getInstaller, and update use Client Credentials with the management scope. Monitoring alone is read-only for those three. HTTP 401 or 403 means the token, scope, or regional host is wrong.

Checklist Template Endpoints

Shipped in 0.11.0 where the Public API still has the operation. Verified against NinjaOne Public API 2.0.9-draft (apidocs-beta, NinjaRMM-API-v2.yaml) on 2026-09-24.

  • [x] List: GET /v2/checklist/templates (getAll). Filters are checklistTemplateIds, checklistTemplateName, required, and includeArchived. The Public API documents no pagination parameters, so none are sent.
  • [x] Create: POST /v2/checklist/templates (create). The JSON body is an array. Each item sends name, plus description (text and html), tasks, and required when set. Each task can include position, name, and description.
  • [x] Update: PUT /v2/checklist/templates (update). The JSON body is an array. Each item sends id and name, plus description, tasks, and required when set.
  • [x] Delete one: DELETE /v2/checklist/template/{checklistTemplateId} (delete). Success is HTTP 204.
  • [x] Delete many: POST /v2/checklist/templates/delete (deleteMany). The JSON body is a raw integer array. Success is HTTP 204.
  • [x] Archive: POST /v2/checklist/archive (archive). The JSON body is checklistTemplateIds.
  • [x] Restore: POST /v2/checklist/restore (restore). The JSON body is checklistTemplateIds.

Skipped after checking Public API 2.0.9-draft:

  • POST /v2/checklist/templates/restore is absent. Restore uses POST /v2/checklist/restore.
  • GET /v2/checklist/template/{checklistTemplateId} is absent. The list filter checklistTemplateIds selects templates. DELETE is the only method on that path.

These calls use Client Credentials with the management scope. Monitoring alone covers monitoring data and organization structure. Public API 2.0.9-draft tags these routes Checklist Templates and does not add a per-operation security override. HTTP 401 or 403 means the token, scope, or regional host is wrong.

Document Template Endpoints

Corrected in 0.11.0 against Public API 2.0.9-draft. The resource already listed, got, created, updated, deleted, archived, and restored templates. The request shapes below match the spec.

  • [x] List: GET /v2/document-templates (getAll). Query parameters are templateName and includeTechnicianRoles. There is no fields, limit, or offset parameter.
  • [x] Get: GET /v2/document-templates/{documentTemplateId} (get). The only query parameter is includeTechnicianRoles. HTTP 404 means the template was not found.
  • [x] Create: POST /v2/document-templates (create). The API requires name. allowMultiple is create-only.
  • [x] Update: PUT /v2/document-templates/{documentTemplateId} (update). Only fields you add are sent. allowMultiple is not an update property.
  • [x] Delete: DELETE /v2/document-templates/{documentTemplateId} (delete). Success is HTTP 204.
  • [x] Archive one: POST /v2/document-templates/{documentTemplateId}/archive (archive). No body. Success is HTTP 204.
  • [x] Archive many: POST /v2/document-templates/archive (archiveMany). The JSON body is a raw integer array.
  • [x] Restore one: POST /v2/document-templates/{documentTemplateId}/restore (restore). No body.
  • [x] Restore many: POST /v2/document-templates/restore (restoreMany). The JSON body is a raw integer array. The response schema is one document template object.

These calls use Client Credentials with the management scope. Monitoring alone covers monitoring data and organization structure. The routes are tagged Document Templates and have no per-operation security override. HTTP 401 or 403 means the token, scope, or regional host is wrong.

Organization Checklist Archive

Shipped in 0.11.0. Verified against Public API 2.0.9-draft.

  • [x] Archive: POST /v2/organization/archive (archive on Organization Checklist). The JSON body is clientChecklistIds. This does not archive the organization.
  • [x] Restore: POST /v2/organization/restore (restore on Organization Checklist). The JSON body is clientChecklistIds. This does not restore the organization.

Same management-scope rule as the template calls above. HTTP 401 or 403 means the token, scope, or regional host is wrong.

Organization Checklist Endpoints

Shipped in 0.12.0 where the Public API still has the operation. Archive and restore shipped in 0.11.0. Verified against NinjaOne Public API 2.0.9-draft (apidocs-beta, NinjaRMM-API-v2.yaml) on 2026-09-24.

  • [x] List: GET /v2/organization/checklists (getAll). Filters are checklistIds, organizationIds, checklistName, assignedToUserId, completed, required, and includeArchived. The Public API documents no pagination parameters, so none are sent.
  • [x] Get: GET /v2/organization/checklist/{checklistId} (get).
  • [x] Signed URLs: GET /v2/organization/checklist/{checklistId}/signed-urls (getSignedUrls). The response is a map of content IDs to signed URLs.
  • [x] Create: POST /v2/organization/checklists (create). The JSON body is an array. Each item sends name and organizationId, plus description, required, dueDate, assignedToUserId, checklistTemplateId, and tasks when set.
  • [x] Update: PUT /v2/organization/checklists (update). The JSON body is an array. Each item sends checklistId and name, plus description, required, dueDate, assignedToUserId, and tasks when set. organizationId is not an update property.
  • [x] Delete one: DELETE /v2/organization/checklist/{checklistId} (delete). Success is HTTP 204.
  • [x] Delete many: POST /v2/organization/checklists/delete (deleteMany). The JSON body is a raw integer array. Success is HTTP 204.
  • [x] Create from templates: POST /v2/organization/{organizationId}/checklists-from-templates (createFromTemplates). The JSON body is a raw integer array of template IDs.
  • [x] Promote: POST /v2/organization/checklists/promote (promote). The JSON body is a raw integer array. Success is HTTP 204.
  • [x] Promote with name: POST /v2/organization/checklists/promote-with-name (promoteWithName). The JSON body is an array of id and name. Success is HTTP 204.

These calls use Client Credentials with the management scope. Monitoring alone covers monitoring data and organization structure. Public API 2.0.9-draft tags these routes Organization Checklists and does not add a per-operation security override. HTTP 401 or 403 means the token, scope, or regional host is wrong.

Tagging and Vulnerability Endpoints

Shipped in 0.12.0 where the Public API still has the operation. Verified against NinjaOne Public API 2.0.9-draft (apidocs-beta, NinjaRMM-API-v2.yaml) on 2026-09-24.

  • [x] List tags: GET /v2/tag (getAll). The response is an object with a tags array. The Public API documents no pagination parameters, so none are sent.
  • [x] Create: POST /v2/tag (create). The body sends name, plus description when set.
  • [x] Update: PUT /v2/tag/{tagId} (update). Only name and description that you set are sent.
  • [x] Delete one: DELETE /v2/tag/{tagId} (delete). The Public API documents a default response.
  • [x] Delete many: POST /v2/tag/delete (deleteMany). The JSON body is a raw integer array.
  • [x] Merge: POST /v2/tag/merge (merge). mergeMethod is MERGE_INTO_EXISTING_TAG or MERGE_INTO_NEW_TAG.
  • [x] Set asset tags: PUT /v2/tag/device/{assetId} (setAssetTags). The device tags become exactly the supplied IDs.
  • [x] Update asset tags: POST /v2/tag/device (updateAssetTags). The body sends assetIds, plus tagIdsToAdd and tagIdsToRemove when those lists have IDs.
  • [x] List scan groups: GET /v2/vulnerability/scan-groups (getAll). The Public API documents no pagination parameters, so none are sent. Status is COMPLETE, IN_PROGRESS, or FAILED.
  • [x] Get scan group: GET /v2/vulnerability/scan-groups/{scan-group-id} (get). HTTP 404 means the scan group was not found.
  • [x] Upload CSV: POST /v2/vulnerability/scan-groups/{scan-group-id}/upload (upload). The multipart field name is csv and the content type is text/csv. The Public API limit is 200MB. HTTP 200 means the upload was accepted.

Skipped after checking Public API 2.0.9-draft:

  • GET /v2/tag/{assetType} is absent. Listing is GET /v2/tag.
  • GET /v2/tag/{assetType}/{assetId} is absent. Setting tags is PUT /v2/tag/{assetType}/{assetId}. The asset type enum contains only device.
  • A create scan group route is absent. The scan-group routes are list, get, and CSV upload.

These calls use Client Credentials with the management scope. Monitoring alone covers monitoring data and organization structure. Public API 2.0.9-draft tags the routes Asset Tags and Vulnerability Management and does not add a per-operation security override. HTTP 401 or 403 means the token, scope, or regional host is wrong.

Deferred after Approach A

0.12.0 completes the domain-wave checklist. These Public API tags were not on that checklist, so they are not open gaps from Waves 0–6:

  • Organization Documents
  • Knowledge Base Articles
  • Webhooks
  • Backup
  • Reporting and analytics endpoints

There is no remaining unchecked Public API item from the Approach A pending list.

Authentication

The NinjaOne API uses OAuth 2.0 Client Credentials Flow for secure server-to-server communication. This is the recommended authentication method for all API operations.

Setup Instructions

  1. Create NinjaOne OAuth2 API Credentials in n8n:

    • Go to Credentials in n8n
    • Add NinjaOne OAuth2 API credential type
    • Configure your NinjaOne application credentials
  2. Regional Endpoint Configuration:

    • Base URL: The host you use to log in to NinjaOne, with no trailing slash. The API and OAuth token endpoint share this host.
      • North America: https://app.ninjaone.com (or https://us2.ninjaone.com)
      • Europe: https://eu.ninjaone.com
      • Oceania: https://oc.ninjaone.com
      • Canada: https://ca.ninjaone.com
    • Access Token URL: <Base URL>/ws/oauth/token — must be on the same host as the Base URL (e.g. https://eu.ninjaone.com/ws/oauth/token).
    • Client ID: Your NinjaOne application client ID
    • Client Secret: Your NinjaOne application client secret
    • Scope: monitoring management (required for full API access)

    ⚠️ There is no api.ninjaone.com host. Earlier versions defaulted to that, which caused every request (including ticket updates) to fail. Make sure the Base URL matches your dashboard host.

  3. Obtain Application Credentials:

    • Log in to your NinjaOne account
    • Navigate to Administration > Apps > API > Client App IDs
    • Click Add and choose API Services (machine-to-machine)
    • Select the scopes you need and enable the Client Credentials grant type
    • Copy the Client ID and Client Secret to n8n
    • Use the Test button on the credential to confirm authentication works

Ticket Management

Complete CRUD Operations

Create Tickets

{
  "clientId": 1,
  "ticketFormId": 1,
  "summary": "Server maintenance required",
  "description": "Scheduled maintenance for production server",
  "severity": "MODERATE",
  "priority": "HIGH",
  "type": "TASK",
  "status": "1000"
}

Update Tickets

Updates are partial — only the fields you add under Update Fields are sent, so existing ticket data is never overwritten with defaults. Supported fields include:

  • Summary, status, severity, priority, type
  • Organization assignment and time tracking
  • CC lists (UIDs and email addresses)
  • Tags, attributes, and custom fields
  • Parent ticket relationships for sub-tickets
  • Version (optional, for instances that enforce optimistic locking — supply the value from a prior Get)

Comment System

  • Add public/private comments to tickets
  • Time tracking integration for billable hours
  • Support for HTML formatted content

Board-Based Listing

  • Retrieve tickets by ticketing board ID
  • Pagination and filtering support
  • Sorting and search capabilities
  • Custom column selection

Field Mapping Accuracy

All ticket operations use field mappings verified against real NinjaOne API responses:

  • Severity Levels: NONE, MINOR, MODERATE, MAJOR, CRITICAL
  • Status IDs: 1000 (New), 2000 (Open), 3000 (Waiting for Customer), 4000 (Hold)
  • Ticket Types: PROBLEM, TASK, QUESTION
  • Summary Field: Uses 'summary' (not 'subject') to match API response structure
  • Organization Assignment: Department/team assignment support
  • Time Tracking: Seconds-based time tracking for accurate billing

Device Management

Available Operations

  • Get Device – Retrieve detailed device information by ID
  • List Devices – Get all devices with filtering and pagination
  • Device Activities – Monitor device activity logs and events
  • Device Alerts – Access critical alerts and notifications
  • Custom Fields – Read and update device custom field data
  • Hardware Inventory – Disks, processors, network interfaces, volumes
  • Software Management – Installed software, patches, and updates
  • System Information – OS details, Windows services, last logged user
  • Policy Management – Policy overrides and compliance status
  • Reboot Device – POST /v2/device/{id}/reboot/{mode}
  • Run Script – POST /v2/device/{id}/script/run
  • Control Windows Service – POST /v2/device/{id}/windows-service/{serviceId}/control
  • Configure Windows Service – POST /v2/device/{id}/windows-service/{serviceId}/configure
  • Dashboard URL – GET /v2/device/{id}/dashboard-url
  • Schedule / Cancel Maintenance – PUT and DELETE /v2/device/{id}/maintenance
  • Set / Remove Device Owner – POST /v2/device/{id}/owner/{ownerUid} and DELETE /v2/device/{id}/owner
  • OS Patch Apply / Scan – POST /v2/device/{id}/patch/os/apply and /scan
  • Software Patch Apply / Scan – POST /v2/device/{id}/patch/software/apply and /scan
  • Approve or Reject Devices – POST /v2/devices/approval/{mode}

Policies

  • List Policies – GET /v2/policies (monitoring scope, no pagination parameters)
  • Custom-Field Conditions – list, get, and create under /v2/policies/{policy_id}/condition/custom-fields
  • Windows-Event Conditions – list, get, and create under /v2/policies/{policy_id}/condition/windows-event
  • Delete Condition – DELETE /v2/policies/{policy_id}/condition/{condition_id}
  • Assign Organization Policies – PUT /v2/organization/{id}/policies (management scope)

API Coverage

Implemented Endpoints

Ticketing Operations:

  • POST /v2/ticketing/ticket - Create tickets
  • GET /v2/ticketing/ticket/{id} - Get ticket details
  • PUT /v2/ticketing/ticket/{id} - Update tickets
  • POST /v2/ticketing/ticket/{id}/comment - Add comments
  • GET /v2/ticketing/trigger/boards - List ticketing boards
  • POST /v2/ticketing/trigger/board/{id}/run - Get tickets by board
  • GET /v2/ticketing/ticket/{ticketId}/log-entry - Ticket log entries (Client Credentials)
  • GET /v2/ticketing/attributes - Ticket attribute metadata (Client Credentials)
  • GET /v2/ticketing/contact/contacts - Contact directory, no pagination parameters (Client Credentials)
  • GET /v2/ticketing/ticket-form - List ticket forms (Client Credentials)
  • GET /v2/ticketing/ticket-form/{id} - Get one ticket form (Client Credentials)
  • GET /v2/ticketing/statuses - Tenant ticket statuses (Client Credentials)
  • GET /v2/ticketing/app-user-contact - Technicians, end users, and contacts (Client Credentials)

Device Operations:

  • GET /v2/device/{id} - Device details
  • GET /v2/devices - List devices
  • GET /v2/device/{id}/activities - Device activities
  • GET /v2/device/{id}/alerts - Device alerts
  • POST /v2/device/{id}/reboot/{mode} - Reboot device
  • POST /v2/device/{id}/script/run - Run script
  • POST /v2/device/{id}/windows-service/{serviceId}/control - Control a Windows service
  • GET /v2/device/{id}/dashboard-url - Device dashboard URL
  • PUT /v2/device/{id}/maintenance - Schedule maintenance (Client Credentials, management scope)
  • DELETE /v2/device/{id}/maintenance - Cancel maintenance (Client Credentials, management scope)
  • POST /v2/device/{id}/owner/{ownerUid} - Set device owner (management scope)
  • DELETE /v2/device/{id}/owner - Remove device owner (management scope)
  • POST /v2/device/{id}/patch/os/apply and /scan - OS patch jobs, no body
  • POST /v2/device/{id}/patch/software/apply and /scan - Software patch jobs, no body
  • POST /v2/device/{id}/windows-service/{serviceId}/configure - Windows service startup settings
  • POST /v2/devices/approval/{mode} - Approve or reject devices (APPROVE or REJECT)
  • Plus additional device inventory endpoints (patches, disks, processors, software, volumes)

Organization Operations:

  • POST /v2/organizations - Create an organization
  • GET /v2/organization/{id} - Organization details
  • GET /v2/organization/{id}/locations - Locations for one organization, no pagination parameters (monitoring scope)
  • POST /v2/organization/generate-installer - Installer URL (management scope)
  • GET /v2/organization/{id}/location/{location_id}/installer/{installer_type} - Installer URL for a location (management scope)
  • PATCH /v2/organization/{id} - Partial organization update (management scope)

Policy Operations:

  • GET /v2/policies - List policies, no pagination parameters (monitoring scope)
  • GET /v2/policies/{policy_id}/condition/custom-fields - List custom-field conditions (management scope)
  • GET /v2/policies/{policy_id}/condition/custom-fields/{condition_id} - Get one custom-field condition (management scope)
  • POST /v2/policies/{policy_id}/condition/custom-fields - Create a custom-field condition (management scope)
  • GET /v2/policies/{policy_id}/condition/windows-event - List Windows-event conditions (management scope)
  • GET /v2/policies/{policy_id}/condition/windows-event/{condition_id} - Get one Windows-event condition (management scope)
  • POST /v2/policies/{policy_id}/condition/windows-event - Create a Windows-event condition (management scope)
  • DELETE /v2/policies/{policy_id}/condition/{condition_id} - Delete one condition of any type (management scope)
  • PUT /v2/organization/{id}/policies - Assign policies to node roles (management scope)

Document Template Operations:

  • GET /v2/document-templates - List templates (templateName, includeTechnicianRoles; management scope)
  • GET /v2/document-templates/{id} - Get a template (includeTechnicianRoles)
  • POST /v2/document-templates - Create a template (name required)
  • PUT /v2/document-templates/{id} - Update a template (no allowMultiple)
  • DELETE /v2/document-templates/{id} - Delete a template
  • POST /v2/document-templates/{id}/archive and /restore - Archive or restore one template
  • POST /v2/document-templates/archive and /restore - Archive or restore many templates (raw integer array)

Checklist Template Operations:

  • GET /v2/checklist/templates - List templates, no pagination parameters (management scope)
  • POST /v2/checklist/templates - Create templates (JSON array)
  • PUT /v2/checklist/templates - Update templates (JSON array with id)
  • DELETE /v2/checklist/template/{checklistTemplateId} - Delete one template
  • POST /v2/checklist/templates/delete - Delete many templates (raw integer array)
  • POST /v2/checklist/archive - Archive templates (checklistTemplateIds)
  • POST /v2/checklist/restore - Restore templates (checklistTemplateIds)

Organization Checklist Operations:

  • POST /v2/organization/archive - Archive organization checklists (clientChecklistIds, management scope)
  • POST /v2/organization/restore - Restore organization checklists (clientChecklistIds, management scope)
  • GET /v2/organization/checklists - List organization checklists, no pagination parameters (management scope)
  • GET /v2/organization/checklist/{checklistId} - Get one organization checklist
  • GET /v2/organization/checklist/{checklistId}/signed-urls - Signed URLs for checklist content
  • POST /v2/organization/checklists - Create organization checklists (JSON array)
  • PUT /v2/organization/checklists - Update organization checklists (JSON array with checklistId)
  • DELETE /v2/organization/checklist/{checklistId} - Delete one organization checklist
  • POST /v2/organization/checklists/delete - Delete many organization checklists (raw integer array)
  • POST /v2/organization/{organizationId}/checklists-from-templates - Create checklists from template IDs
  • POST /v2/organization/checklists/promote - Promote checklists (raw integer array)
  • POST /v2/organization/checklists/promote-with-name - Promote checklists with id and name

Tag Operations:

  • GET /v2/tag - List tags, no pagination parameters (management scope)
  • POST /v2/tag - Create a tag
  • PUT /v2/tag/{tagId} - Update a tag
  • DELETE /v2/tag/{tagId} - Delete a tag
  • POST /v2/tag/delete - Delete tags (raw integer array)
  • POST /v2/tag/merge - Merge tags
  • PUT /v2/tag/device/{assetId} - Set device tags exactly
  • POST /v2/tag/device - Add and remove device tags

Vulnerability Operations:

  • GET /v2/vulnerability/scan-groups - List scan groups, no pagination parameters (management scope)
  • GET /v2/vulnerability/scan-groups/{scan-group-id} - Get one scan group
  • POST /v2/vulnerability/scan-groups/{scan-group-id}/upload - Upload a CSV (csv multipart field)

Regional Endpoint Support

The integration supports all NinjaOne regional deployments. Set the Base URL to the host you log in with:

  • North America: https://app.ninjaone.com (or https://us2.ninjaone.com)
  • Europe: https://eu.ninjaone.com
  • Oceania: https://oc.ninjaone.com
  • Canada: https://ca.ninjaone.com

The OAuth token endpoint must be on the same host (<Base URL>/ws/oauth/token).

Usage Examples

Basic Ticket Workflow

  1. List Ticketing Boards to identify available boards
  2. Get Tickets by Board to retrieve current tickets
  3. Create Ticket for new issues or tasks
  4. Update Ticket to modify status, priority, or assignment
  5. Add Comments for progress updates and communication

Device Monitoring Workflow

  1. List Devices to get inventory overview
  2. Get Device Alerts to identify issues requiring attention
  3. Get Device Activities to review recent events
  4. Create Tickets automatically for critical alerts
  5. Update Custom Fields to track remediation status

Documentation

Troubleshooting

400 Bad Request : Verify all required fields are provided for the operation. Check that the Base URL matches your regional endpoint and doesn't contain trailing slashes.

401 Unauthorized : Confirm OAuth2 credentials are correct and have appropriate scopes. Make sure the Base URL and Access Token URL are on the same regional host. Use the credential Test button to verify the Client Credentials flow before running the node.

405 Method Not Allowed : Ensure you're using the latest version - older versions had incorrect HTTP methods for some operations.

TLS/SSL Errors : Verify the Base URL uses https and matches your actual NinjaOne regional domain. Check network connectivity and proxy settings.

Version History

Version 0.12.0

Approach A domain waves are complete. Tags, vulnerability scan groups, and organization checklist promotion are in this release. See CHANGELOG.md.

Version 0.3.0

Major Enhancements:

  • Complete ticket field mapping overhaul based on production API data
  • Enhanced Create and Update operations with all available fields
  • Fixed Get Tickets by Board operation (GET → POST method)
  • Added comprehensive Comment operations with time tracking
  • Updated severity levels to match real API: MINOR, MODERATE, MAJOR
  • Implemented proper status ID mapping for accurate state management
  • Repository reorganization and professional documentation structure

Technical Improvements:

  • All field names match actual API responses ('summary' vs 'subject')
  • TypeScript compilation and ESLint compliance maintained
  • Comprehensive testing against live NinjaOne API endpoints
  • Optimized icon and branding throughout the package

Releasing

npm publishes only when a GitHub Release is published. Pull requests and pushes to master run install, test, lint, and build, and do not publish.

  1. Bump version in package.json on a pull request, using the existing wave process.
  2. After that pull request merges to master, create a GitHub Release with tag vX.Y.Z matching package.json (version 0.12.0 uses tag v0.12.0).
  3. Actions checks out that tag, runs tests, and runs npm publish --access public. prepublishOnly builds and lints before upload. If that version is already on npm, the workflow exits successfully and does not publish again.

One-time setup: add a repository Actions secret named NPM_TOKEN. Use an npm granular access token with publish rights for the @ev1lc0rp scope or @ev1lc0rp/n8n-nodes-ninjaone (npm's CI publish token; not a classic token). Do not commit the token.

Contributing

This project follows standard n8n community node development practices. See docs/development/ for detailed contribution guidelines.

License

MIT License - see LICENSE.md for details.

Support


Professional NinjaOne integration for n8n - Automate your IT service management workflows with confidence.