Actions159
- Related Items Actions
- Backup Actions
- Queries Actions
- Get Disk Drives
- Get Operating Systems
- Get RAID Controller Report
- Get Volumes
- Get Computer Systems
- Get Antivirus Status Report
- Get Device Health Report
- Get Custom Fields Report
- Get Installed Software Patches
- Get Custom Fields Detailed Report
- Get Installed OS Patches
- Get Pending Failed Rejected OS Patches
- Get RAID Drive Report
- Get Windows Services Report
- Get Antivirus Threats
- Get Device Usage
- Get Network Interfaces
- Get Processors
- Get Software
- Get Last Logged On Users Report
- Get Policy Overrides 1
- Get Scoped Custom Fields Report
- Get Pending Failed Rejected Software Patches
- Get Scoped Custom Fields Detailed Report
- System Actions
- Knowledge Base Articles Actions
- Get Knowledge Base Article Signed Urls
- Get Related Item Attachments Signed Urls
- Download Knowledge Base Article
- Get Knowledge Base Folder Path Content
- Upload Temp Attachments
- Get Knowledge Base Folder Content
- Get Client Knowledge Base Articles
- Upload Knowledge Base Articles
- Get Global Knowledge Base Articles
- Download Related Item Attachment
- Organization Documents Actions
- Document Templates Actions
- Checklist Templates Actions
- Organization Checklists Actions
- Location Actions
- Management Actions
- Get Custom Fields Policy Condition
- Delete Policy Condition
- Reset Alert
- Update Device
- Request Scripting Options
- Submit OS Patch Scan
- Get Installer For Location
- Get Windows Event Policy Conditions
- Create Organization
- Cancel Device Maintenance
- Reboot Devices
- Set Windows Service Configuration
- Create Location For Organization
- Update Node Role Policy Assignment For Organization
- Create Windows Event Policy Condition
- Node Approval Operation
- Control Windows Service
- Remove Device Owner
- Submit OS Patch Apply
- Get Installer
- Create Policy
- Get Windows Event Policy Condition
- Update Device Maintenance
- Reset Policy Overrides
- Set Device Owner
- Submit Software Patch Scan
- Update Location
- Reset Alert Set Activity Data
- Get Device Link
- Run Script On Device
- Submit Software Patch Apply
- Update Organization
- Create Custom Fields Policy Condition
- Get Custom Fields Policy Conditions
- Custom Fields Actions
- Ticketing Actions
- Organization Actions
- Devices Actions
- Get Device Active Jobs
- Get Device Installed Software Patches
- Get Device Processors
- Update Node Attribute Values
- Get Device Disk Drives
- Get Device Pending Failed Rejected OS Patches
- Get Device Volumes
- Get Device Alerts
- Get Device Network Interfaces
- Get Device Software
- Get Device Activities
- Get Device Last Logged On User
- Get Device Services
- Get Policy Overrides
- Get Device
- Get Device Installed OS Patches
- Get Device Pending Failed Rejected Software Patches
- Get Node Custom Fields
- Groups Actions
- Webhooks Actions
Overview
This node integrates with the AvantGuard NinjaOne API to manage organization documents. Specifically, the "Archive Client Document" operation allows users to archive a client document by its unique identifier. This is useful in scenarios where documents related to clients need to be organized or removed from active use without permanent deletion, such as archiving outdated contracts, reports, or correspondence.
Practical examples include:
- Archiving client invoices after payment is completed.
- Moving old client project documentation to an archive state for record-keeping.
- Managing document lifecycle within an organization's document management system.
Properties
| Name | Meaning |
|---|---|
| Client Document Id | The unique numeric identifier of the client document to be archived. |
Output
The node outputs JSON data representing the result of the archive operation. This typically includes confirmation of the archival status and any relevant metadata returned by the API about the archived document. The exact structure depends on the API response but generally confirms success or failure of the archival request.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the AvantGuard NinjaOne service.
- Needs the base URL of the NinjaOne API configured in the node credentials.
- Depends on the
@avantguardllc/n8n-openapi-nodepackage for building requests based on the OpenAPI specification.
Troubleshooting
- Invalid Client Document Id: If the provided document ID does not exist or is invalid, the API may return an error indicating the document was not found. Verify the ID before running the node.
- Authentication Errors: Missing or incorrect API credentials will cause authentication failures. Ensure the API key and base URL are correctly set in the node credentials.
- Network Issues: Connectivity problems can prevent the node from reaching the NinjaOne API. Check network settings and firewall rules.
- API Rate Limits: Excessive requests might trigger rate limiting. Implement retries or backoff strategies if needed.
Links and References
- AvantGuard NinjaOne API Documentation (generic link, replace with actual if available)
- n8n Documentation on Creating Custom Nodes