Actions120
- Alert Actions
- Backup Actions
- Custom Field Actions
- Device Actions
- Document Template Actions
- Group Actions
- Knowledge Base Article Actions
- Location Actions
- Organization Actions
- Organization Document Actions
- Query Actions
- Alerts
- Antivirus Status
- Antivirus Threats
- Backup Usage
- Computer Systems
- Custom Fields
- Custom Fields (Detailed)
- Device Health
- Disks
- Logged-On Users
- Network Interfaces
- Operating Systems
- OS Patch Installs
- OS Patches
- Policy Overrides
- Processors
- RAID Controllers
- RAID Drives
- Scoped Custom Fields
- Scoped Custom Fields (Detailed)
- Software
- Software Patch Installs
- Software Patches
- Volumes
- Windows Services
- Related Item Actions
- Software License Actions
- System Actions
- Get Activities
- Get Contacts
- Get Device Custom Fields
- Get Device Roles
- Get Devices (Detailed)
- Get End Users
- Get Jobs
- Get Locations
- Get Notification Channels
- Get Notification Channels (Enabled)
- Get Organizations (Detailed)
- Get Policies
- Get Scheduled Tasks
- Get Scripting Languages
- Get Scripts
- Get Software Products
- Get Technicians
- Get User Roles
- Ticketing Actions
- User Actions
- Webhook Actions
Related Item → Create
AI-generatedSummary
Create a related-item association between two NinjaOne entities. Choose the type and ID of the existing entity, then the type and ID of the entity to relate to it.
Inputs
- Authentication — Select OAuth2 (Authorization Code) or Client Credentials; the default is OAuth2. The matching NinjaOne credentials must be configured.
- Entity Type (required) — Type of the existing entity: Organization, Device, Ticket, Document, KB Article, or Checklist. Defaults to Organization.
- Entity ID (required) — Numeric ID of the existing entity.
- Related Entity Type (required) — Type of the entity to associate: Organization, Device, Ticket, Document, KB Article, or Checklist. Defaults to Device.
- Related Entity ID (required) — Numeric ID of the entity to associate.
Output shape
A single item containing the API response, or a success object if the API returns no response body.
Creates the association with a POST request. For each incoming n8n item, the node uses that item's configured parameters and emits the corresponding result.