@vaiyen/n8n-nodes-ninjaone
v1.4.2
Published
n8n community node for NinjaOne RMM – full API coverage including organizations, devices, ticketing, users, groups, queries, management, backup, locations, custom fields, webhooks, knowledge base, document templates, and more.
Maintainers
Readme
@vaiyen/n8n-nodes-ninjaone
Vollständige n8n Community Node für die NinjaOne RMM API (v2). Unterstützt alle regionalen Instanzen (EU, US, OC, CA) mit OAuth2 Authorization Code und Client Credentials Authentifizierung.
Installation
- Öffne deine n8n-Instanz
- Gehe zu Settings → Community Nodes
- Klicke Install
- Gib
@vaiyen/n8n-nodes-ninjaoneein - Bestätige die Installation
Authentifizierung
Option 1: OAuth2 Authorization Code (für Ticket-Erstellung mit User-Kontext)
- In NinjaOne: Administration → Apps → API → Client App IDs → Add
- Plattform: Web
- Wähle Authorization Code und Refresh Token als Grant Types
- Scopes:
monitoring,management,control - Redirect URI:
https://<dein-n8n>/rest/oauth2-credential/callback - In n8n: Neue Credential erstellen → NinjaOne OAuth2 API
- Toggle auf OAuth2 (Authorization Code)
- Trage Client ID, Client Secret ein und wähle die Region
- Klicke Connect zum Autorisieren
Option 2: Client Credentials / Machine-to-Machine (für Kontakte, Lesen, etc.)
- In NinjaOne: Administration → Apps → API → Client App IDs → Add
- Plattform: Machine-to-Machine
- Scopes:
monitoring,management,control - In n8n: Neue Credential erstellen → NinjaOne OAuth2 API
- Toggle auf Client Credentials
- Trage Client ID, Client Secret ein und wähle die Region
- Klicke Save
Wann welche Credential?
- OAuth2 Authorization Code → Tickets erstellen/bearbeiten (braucht User-Kontext)
- Client Credentials → Kontakte lesen/erstellen, Devices auflisten, alles was keinen User-Kontext braucht
Du kannst beide Credentials im selben Workflow verwenden – einfach pro Node die passende auswählen.
Unterstützte Ressourcen & Operationen
Organization
- Create, Get, Get Many, Update, Delete
Device
- Get, Get Many (mit Device Filter Syntax)
- Get Activities, Custom Fields, Disks, Network Interfaces, OS Patches, Processors, Software, Volumes
- Approve/Reject, Reboot, Run Script, Maintenance Mode
- Update Custom Fields
Ticketing
- Create Ticket, Get Ticket, Get Many (per Board ID), Update, Delete
- Create Contact, Get Contacts
- Add Comment, Get Log Entries
- Get Boards, Statuses, Ticket Forms
User
- Create, Get, Get Many, Update, Delete
Group
- Get, Get Many, Get Device IDs
Query (Bulk-Abfragen)
- Alerts, Antivirus Status, Antivirus Threats, Custom Fields
- Device Health, Disks, Network Interfaces
- OS Patches, OS Patch Installs, Processors
- RAID Drives, Software, Software Patches, Windows Services
Alert
- Get Many, Reset, Reset with Activity Data
Location
- Create, Get Many, Update
Backup
- Get Backup Jobs, Get Integrity Check Results
Webhook
- Configure (Create/Update), Delete
Custom Field
- Get/Update Device Custom Fields
- Get/Update Organization Custom Fields
Knowledge Base Article
- Create, Get, Get Many, Update, Delete
Organization Document
- Create, Get, Get Many, Update, Delete
Document Template
- Get, Get Many
Related Item
- Create, Get Many, Delete
Trigger Node
Der NinjaOne Trigger Node empfängt Webhook-Events in Echtzeit:
- Alert Triggered/Reset
- Condition Triggered/Reset
- Device Added/Deleted/Online/Offline/Approval
- Patch Management
- Script Run
- Ticket Created/Updated/Deleted
Device Filter Syntax
Viele Endpoints unterstützen die NinjaOne Device Filter Syntax (Parameter df), z.B.:
class in (WINDOWS_WORKSTATION, WINDOWS_SERVER)
org = 1
status = ONLINESiehe NinjaOne Device Filter Dokumentation.
API Regionen
| Region | Base URL |
|----------|-----------------------------|
| EU | https://eu.ninjarmm.com |
| US | https://app.ninjarmm.com |
| Oceania | https://oc.ninjarmm.com |
| Canada | https://ca.ninjarmm.com |
Lizenz
MIT
