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 create a comment on a specified ticket within a ticketing system. It is useful for automating the process of adding notes, updates, or additional information to support tickets or service requests. For example, a user can automatically append status updates or troubleshooting details to a ticket as part of a workflow, improving communication and record-keeping.
Properties
| Name | Meaning |
|---|---|
| Ticket Id | The unique identifier of the ticket where the comment will be added. |
| Additional Body Fields | Optional fields to customize the comment, including: |
- Comment: JSON object defining the comment content, such as whether it is public, the body text, HTML formatted body, and time tracked (in minutes). Example: {"public": true, "body": "new comment", "htmlBody": "<p>new comment</p>", "timeTracked": 60} |
|
| - Files: JSON array representing files to attach to the comment. |
Output
The node outputs JSON data representing the response from the API after creating the comment. This typically includes details about the newly created comment such as its ID, content, timestamps, and any metadata returned by the ticketing system. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the AvantGuard NinjaOne API.
- The base URL for the API must be configured in the node credentials.
- The node uses the
@avantguardllc/n8n-openapi-nodepackage and an OpenAPI specification (openapi.json) bundled internally to define its operations.
Troubleshooting
Common issues:
- Invalid or missing Ticket Id: Ensure the ticket ID provided exists and is correct.
- Malformed JSON in the "Comment" or "Files" fields: Validate JSON syntax before input.
- Authentication errors: Verify that the API key credential is correctly set up and has necessary permissions.
- Network or API endpoint errors: Check connectivity and that the base URL is correct.
Error messages:
- Unauthorized or 401 errors indicate authentication failure; recheck API credentials.
- 404 errors may mean the ticket ID does not exist.
- Validation errors from the API may occur if required comment fields are missing or incorrectly formatted.
Links and References
- AvantGuard NinjaOne API Documentation (example placeholder, replace with actual link)
- n8n documentation on creating custom nodes