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 → Get Related Items With Entity Type
AI-generatedOverview
This node interacts with the NinjaOne API to retrieve related items filtered by a specified entity type. It is useful when you want to fetch entities that are related to other records within the NinjaOne platform, such as organizations, documents, locations, or technicians. For example, you might use this node to get all documents related to a specific organization or all attachments linked to a particular technician.
Properties
| Name | Meaning |
|---|---|
| Related Entity Type | The type of related entity to retrieve. Options include: ORGANIZATION, DOCUMENT, LOCATION, NODE, ATTACHMENT, TECHNICIAN, CREDENTIAL, CHECKLIST, END USER, CONTACT, KB DOCUMENT |
Output
The node outputs an array of JSON objects representing the related items fetched from the NinjaOne API. Each item in the output corresponds to one related entity matching the selected entity type. The exact structure of each JSON object depends on the NinjaOne API response for the related entity type requested.
No binary data output is indicated for this operation.
Dependencies
- Requires an active NinjaOne API OAuth2 credential configured in n8n.
- The node uses the NinjaOne REST API endpoints and requires network access to NinjaOne services.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
- Missing or invalid API credentials: Ensure the NinjaOne OAuth2 API credential is correctly set up and authorized.
- No binary data error: Not applicable here since this operation does not handle binary data.
- API request failures: Check network connectivity and NinjaOne API status if requests fail.
- Invalid entity type selection: Make sure the "Related Entity Type" property is set to one of the supported options.
- Error messages from API: These will be returned in the output JSON under an
errorfield if the node is set to continue on failure.
Links and References
- NinjaOne API Documentation (for detailed API endpoint info)
- n8n OAuth2 Credential Setup