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
Document Templates → Archive Document Template
AI-generatedOverview
This node interacts with the NinjaOne API to manage Document Templates, specifically allowing users to archive a document template by its ID. Archiving a document template typically means marking it as inactive or removing it from active use without deleting it permanently. This operation is useful in scenarios where you want to keep a record of templates but prevent them from being used further.
Practical examples:
- Automatically archiving outdated document templates as part of a cleanup workflow.
- Archiving templates that are no longer relevant after a project completion.
- Managing document lifecycle by programmatically controlling template availability.
Properties
| Name | Meaning |
|---|---|
| Document Template Id | The unique numeric identifier of the document template to be archived. |
Output
The node outputs an array of JSON objects, each representing the response from the NinjaOne API for the archive operation. The exact structure depends on the API response but generally includes confirmation of the archival action or details about the archived template.
No binary data output is involved in this operation.
Dependencies
- Requires an API authentication token credential configured in n8n to authenticate requests to the NinjaOne API.
- The node uses the NinjaOne OAuth2 API credential for authorization.
- Network access to the NinjaOne API endpoint is necessary.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Document Template Id will likely result in an error from the API.
- Missing or incorrect API credentials will cause authentication failures.
- Lack of network connectivity or API downtime can cause request failures.
Error messages and resolutions:
- "No binary data exists on item!" — Not applicable here since this operation does not require binary input.
- API errors related to invalid IDs or permissions should be resolved by verifying the Document Template Id and ensuring the API credentials have sufficient permissions.
- If the node throws an error about missing parameters, ensure the "Document Template Id" property is set and is a valid number.
Links and References
- NinjaOne API Documentation (general reference): https://api.ninjaone.com/docs
- n8n OAuth2 Credential Setup Guide: https://docs.n8n.io/credentials/oauth2/