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 → Delete Document Template
AI-generatedOverview
This node interacts with the NinjaOne API to manage Document Templates. Specifically, the "Delete Document Template" operation allows users to remove a document template by its unique identifier. This is useful in scenarios where outdated or unnecessary templates need to be cleaned up from the system to maintain organization and relevance.
Practical examples include:
- Automating the cleanup of deprecated document templates as part of a maintenance workflow.
- Removing templates that are no longer compliant with updated company policies.
- Managing templates dynamically based on project lifecycle or user roles.
Properties
| Name | Meaning |
|---|---|
| Document Template Id | The unique numeric identifier of the document template to delete. This property is required. |
Output
The output of this node is a JSON object representing the response from the NinjaOne API after attempting to delete the specified document template. Typically, this will contain confirmation of deletion or relevant status information.
If an error occurs during the deletion process, the output JSON will contain an error field with the error message, provided the node is configured to continue on failure.
Dependencies
- Requires an active connection to the NinjaOne API using OAuth2 authentication.
- The node expects the NinjaOne API credentials to be configured in n8n.
- 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 expired API authentication tokens can cause authorization failures.
- Lack of proper permissions in the NinjaOne account to delete document templates.
Error messages:
"No binary data exists on item!"or similar errors are not relevant for this operation since it does not handle binary data.- API errors returned in the JSON response under the
errorfield should be reviewed for details such as invalid IDs or permission issues.
Resolutions:
- Verify the Document Template Id is correct and exists.
- Ensure the API credentials are valid and have sufficient permissions.
- Check network connectivity and NinjaOne service status.
Links and References
- NinjaOne API Documentation (general): https://api.ninjaone.com/docs
- NinjaOne OAuth2 Authentication Guide (for setting up credentials in n8n)
- n8n Documentation on HTTP Request and API Integration Nodes