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
Organization Documents → Delete Client Document
AI-generatedOverview
This node integrates with the NinjaOne API to manage various organizational resources. Specifically, for the "Organization Documents" resource and the "Delete Client Document" operation, it allows users to delete a client document by specifying its unique identifier. This is useful in scenarios where outdated or incorrect client documents need to be removed from the system to maintain data accuracy and compliance.
Practical example: A user wants to automate the cleanup of client documents that are no longer valid or required. By providing the client document ID, this node will send a request to delete that document from the organization's records.
Properties
| Name | Meaning |
|---|---|
| Client Document Id | The unique numeric identifier of the client document to delete |
Output
The node outputs a JSON object representing the response from the NinjaOne API after attempting to delete the specified client document. This typically includes confirmation of deletion or details about any errors encountered.
No binary data output is involved in this operation.
Dependencies
- Requires an API authentication token configured via OAuth2 credentials for NinjaOne.
- The node uses the NinjaOne API endpoints to perform operations.
- Proper network access to the NinjaOne API service is necessary.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Client Document Id will likely result in an error response from the API.
- Missing or expired API authentication tokens will cause authentication failures.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Errors returned from the NinjaOne API will be included in the node's output if "Continue On Fail" is enabled.
- If the node throws an error, verify that the Client Document Id is correct and that the API credentials are valid and have sufficient permissions.
Links and References
- NinjaOne API documentation (general reference): https://api.ninjaone.com/docs
- n8n OAuth2 credential setup guide: https://docs.n8n.io/credentials/oauth2/