Actions158
- System Actions
- Organization Actions
- Devices Actions
- Get Device
- Get Device Active Jobs
- Get Device Activities
- Get Device Alerts
- Get Device Disk Drives
- Get Device Installed OS Patches
- Get Device Installed Software Patches
- Get Device Last Logged On User
- Get Device Network Interfaces
- Get Device Pending Failed Rejected OS Patches
- Get Device Pending Failed Rejected Software Patches
- Get Device Processors
- Get Device Services
- Get Device Software
- Get Device Volumes
- Get Node Custom Fields
- Update Node Attribute Values
- Get Policy Overrides
- Groups Actions
- Queries Actions
- Get Antivirus Status Report
- Get Antivirus Threats
- Get Computer Systems
- Get Custom Fields Detailed Report
- Get Custom Fields Report
- Get Device Health Report
- Get Device Usage
- Get Disk Drives
- Get Installed OS Patches
- Get Installed Software Patches
- Get Last Logged On Users Report
- Get Network Interfaces
- Get Operating Systems
- Get Pending Failed Rejected OS Patches
- Get Pending Failed Rejected Software Patches
- Get Policy Overrides 1
- Get Processors
- Get RAID Controller Report
- Get RAID Drive Report
- Get Scoped Custom Fields Detailed Report
- Get Scoped Custom Fields Report
- Get Software
- Get Volumes
- Get Windows Services Report
- Management Actions
- Get Custom Fields Policy Conditions
- Create Custom Fields Policy Condition
- Get Windows Event Policy Conditions
- Create Windows Event Policy Condition
- Delete Policy Condition
- Get Custom Fields Policy Condition
- Get Windows Event Policy Condition
- Create Organization
- Node Approval Operation
- Reset Alert
- Reset Alert Set Activity Data
- Update Device Maintenance
- Cancel Device Maintenance
- Control Windows Service
- Update Device
- Get Device Link
- Reset Policy Overrides
- Reboot Devices
- Remove Device Owner
- Request Scripting Options
- Run Script On Device
- Set Device Owner
- Set Windows Service Configuration
- Submit OS Patch Apply
- Submit OS Patch Scan
- Submit Software Patch Apply
- Submit Software Patch Scan
- Create Location For Organization
- Get Installer
- Get Installer For Location
- Update Organization
- Update Location
- Update Node Role Policy Assignment For Organization
- Create Policy
- Ticketing Actions
- Webhooks Actions
- Related Items Actions
- Location Actions
- Backup Actions
- Knowledge Base Articles Actions
- Upload Temp Attachments
- Download Knowledge Base Article
- Get Client Knowledge Base Articles
- Get Global Knowledge Base Articles
- Get Knowledge Base Article Signed Urls
- Get Knowledge Base Folder Content
- Get Knowledge Base Folder Path Content
- Download Related Item Attachment
- Get Related Item Attachments Signed Urls
- Organization Documents Actions
- Document Templates Actions
- Checklist Templates Actions
- Custom Fields Actions
- Organization Checklists Actions
Related Items → Create Related Item For Entity
AI-generatedOverview
This node integrates with the NinjaOne API to create a related item for a specified entity type. It allows users to link or associate additional data or items (related items) with entities such as organizations, documents, locations, nodes, checklists, or knowledge base documents within the NinjaOne platform.
Common scenarios include:
- Associating a document or checklist with an organization for better context.
- Linking location information to a node or device.
- Creating relationships between various resource types to maintain structured and connected data in NinjaOne.
Practical example:
- A user wants to add a checklist related to a specific organization entity to track compliance or maintenance tasks directly linked to that organization.
Properties
| Name | Meaning |
|---|---|
| Entity Type | The type of entity to which the related item will be attached. Options: ORGANIZATION, DOCUMENT, LOCATION, NODE, CHECKLIST, KB DOCUMENT |
| Entity Id | The unique numeric identifier of the entity instance to which the related item is being created |
Output
The node outputs JSON data representing the response from the NinjaOne API after creating the related item. This typically includes details about the newly created related item or confirmation of the association.
No binary data output is indicated by the source code.
Dependencies
- Requires an active NinjaOne API OAuth2 authentication credential configured in n8n.
- Uses the NinjaOne REST API endpoints to perform operations.
- No other external dependencies are required.
Troubleshooting
- Missing Binary Data Error: Although not relevant for this operation, the code references binary data handling in other operations. For this operation, ensure that the
Entity IdandEntity Typeare correctly provided. - API Authentication Errors: If the node fails due to authentication, verify that the NinjaOne API OAuth2 credentials are valid and have sufficient permissions.
- Invalid Entity Id or Type: Providing an incorrect or non-existent entity ID or unsupported entity type may cause API errors. Double-check these inputs.
- Network or API Endpoint Issues: Ensure network connectivity and that the NinjaOne API service is operational.
Links and References
- NinjaOne API Documentation (general reference for API endpoints)
- n8n OAuth2 Credential Setup (for configuring NinjaOne API credentials)