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 → Delete Related Item
AI-generatedOverview
This node interacts with the NinjaOne API to manage "Related Items." Specifically, the "Delete Related Item" operation allows users to delete a related item by its ID. This is useful in scenarios where you need to programmatically remove associations or linked records within the NinjaOne platform, such as cleaning up outdated or incorrect related items.
Practical example: If you have an automated workflow that identifies obsolete related items linked to assets or tickets, this node can be used to delete those items automatically, keeping your data clean and relevant.
Properties
| Name | Meaning |
|---|---|
| Related Item Id | The unique numeric identifier of the related item to delete |
Output
The node outputs a JSON object representing the response from the NinjaOne API after attempting to delete the related item. Typically, this will include confirmation of deletion or any error messages returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an active NinjaOne API OAuth2 authentication credential configured in n8n.
- The node uses the NinjaOne API endpoint for deleting related items.
- Network connectivity to the NinjaOne API service is necessary.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Related Item Id will likely result in an error from the API.
- Missing or expired API credentials will cause authentication failures.
- Network issues may prevent the request from completing.
Error messages:
- Errors returned from the NinjaOne API will be passed through in the node's output if "Continue On Fail" is enabled.
- Typical errors include "Not Found" if the Related Item Id does not exist, or "Unauthorized" if credentials are invalid.
Resolutions:
- Verify the Related Item Id is correct and exists in NinjaOne.
- Ensure the API credentials are valid and have sufficient permissions.
- Check network connectivity and retry if transient errors occur.
Links and References
- NinjaOne API Documentation (for detailed API endpoints and payloads)
- n8n documentation on OAuth2 Credentials