Actions30
- Device Actions
- Ticket Actions
- Organization Actions
- Document Actions
Overview
The node allows users to create a new document template within the NinjaOne platform. This operation is useful for automating the management of document templates, which can be used for generating standardized documents such as reports, invoices, or internal forms. By creating templates programmatically, users can integrate document management into their workflows, ensuring consistency and saving time.
Practical examples include:
- Automatically creating a new report template when onboarding a new client.
- Generating document templates for recurring tasks or compliance documentation.
- Managing and updating templates in bulk through automation.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the document template to be created. |
| Description | A textual description providing details about the document template. |
| JSON Parameters | A JSON object representing the full structure and content of the document template. |
Output
The node outputs a JSON object representing the newly created document template as returned by the NinjaOne API. This typically includes fields such as the template's unique identifier, name, description, creation timestamps, and any other metadata provided by the API.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the NinjaOne API.
- Requires an API authentication token credential configured in n8n (OAuth2 or similar).
- The base URL for the API defaults to
https://api.ninjaone.combut can be overridden via credentials.
Troubleshooting
- Authentication errors: Ensure that the API key or OAuth2 credentials are correctly set up and have sufficient permissions to create document templates.
- Validation errors: The "Name" property is required; missing it will cause the request to fail. Also, ensure that the JSON parameters are well-formed JSON objects.
- API connectivity issues: Verify network access to the NinjaOne API endpoint and check for any firewall or proxy restrictions.
- Unexpected API responses: Confirm that the NinjaOne API version matches the expectations of the node and that no breaking changes have occurred.
Links and References
- NinjaOne API Documentation (for detailed API endpoints and schema)
- n8n Documentation (for general usage of custom nodes and credentials)