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 1
AI-generatedOverview
This node interacts with the NinjaOne API to create a related item for a specified entity. It is useful when you want to link or associate additional data or metadata with an existing entity in NinjaOne, such as organizations, documents, locations, nodes, checklists, or knowledge base documents. For example, you might use this node to add a related document to an organization or attach a checklist to a location.
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 identifier (number) of the entity for which the related item is being created |
Output
The output is a JSON object 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 operation's success. The node does not output binary data.
Example output structure (simplified):
{
"id": "12345",
"entityType": "ORGANIZATION",
"entityId": 67890,
"relatedItemDetails": { /* additional info returned by API */ }
}
Dependencies
- Requires an active NinjaOne API OAuth2 credential configured in n8n.
- The node uses NinjaOne's REST API endpoints and requires network access to NinjaOne services.
Troubleshooting
- Missing or invalid credentials: Ensure that the NinjaOne API OAuth2 credentials are correctly set up and authorized.
- Invalid entity ID or type: Verify that the entity ID exists and matches the selected entity type.
- No binary data error: Not applicable here since this operation does not handle binary data.
- API errors: If the NinjaOne API returns an error, it will be included in the output JSON under an
errorfield if "Continue On Fail" is enabled; otherwise, the node execution will stop with an error.
Links and References
- NinjaOne API Documentation (general reference for API endpoints)
- n8n Documentation - Creating Custom Nodes