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 → Restore Document Template
AI-generatedOverview
This node interacts with the NinjaOne API to manage Document Templates, specifically allowing users to restore a previously deleted or archived document template. It is useful in scenarios where a document template was removed but needs to be recovered without recreating it from scratch. For example, if an IT administrator accidentally deletes a standard operating procedure template, this node can restore it quickly.
Properties
| Name | Meaning |
|---|---|
| Document Template Id | The unique numeric identifier of the document template to restore. This is required to specify which template to recover. |
Output
The node outputs JSON data representing the response from the NinjaOne API after attempting to restore the document template. This typically includes details about the restored template such as its ID, name, status, and other metadata confirming the restoration.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the NinjaOne API.
- Needs an API authentication token configured via OAuth2 credentials within n8n.
- The node uses the NinjaOne OAuth2 credential for authenticated requests.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Document Template Id will likely result in an error from the API indicating the template cannot be found.
- Missing or expired API authentication tokens will cause authentication failures.
- Network connectivity problems may prevent the node from reaching the NinjaOne API.
Error messages:
"No binary data exists on item!"or similar errors are not relevant here since this operation does not handle binary data.- API errors related to permissions or invalid IDs should be resolved by verifying the Document Template Id and ensuring the API credentials have sufficient rights.
Links and References
- NinjaOne API Documentation (general reference for API endpoints)
- n8n OAuth2 Credential Setup Guide (for configuring API authentication)