Actions32
- Device Actions
- Control Windows Service
- Get
- Get Activities
- Get Alerts
- Get Custom Fields
- Get Dashboard URL
- Get Disks
- Get Jobs
- Get Last Logged On User
- Get Many
- Get Network Interfaces
- Get OS Patch Installs
- Get OS Patches
- Get Policy Overrides
- Get Processors
- Get Software
- Get Software Patch Installs
- Get Software Patches
- Get Volumes
- Get Windows Services
- Reboot Device
- Run Script
- Update Custom Fields
- Ticket Actions
- Organization Actions
Ticket → Add Comment
AI-generatedOverview
This node operation allows users to add a comment to a specific ticket in the NinjaOne system. It is useful for scenarios where users need to update or communicate additional information related to a ticket, such as support requests or issue tracking. For example, a support agent can add a public comment to inform the end user about the progress or resolution of their ticket.
Use Case Examples
- Adding a comment to a support ticket to provide status updates.
- Attaching a file to a ticket comment for additional context or evidence.
Properties
| Name | Meaning |
|---|---|
| Ticket ID | ID of the ticket to which the comment will be added. |
| Comment Body | Text content of the comment to be added to the ticket. |
| Comment Is Public | Boolean flag indicating whether the comment is visible to the end user. |
| Comment Time Tracked (Seconds) | Time tracked for this comment in seconds, representing work done or time spent. |
| Binary Property | Name of the binary property that holds a file to attach to the comment. Leave empty if no attachment is needed. |
Output
JSON
commentId- Unique identifier of the added comment.ticketId- ID of the ticket to which the comment was added.body- Text content of the added comment.isPublic- Indicates if the comment is public or private.timeTracked- Time tracked for the comment in seconds.attachment- Details of any file attached to the comment, if applicable.
Dependencies
- NinjaOne API with OAuth2 authentication
Troubleshooting
- Ensure the Ticket ID is valid and exists in the NinjaOne system to avoid errors.
- Verify that the comment body is not empty as it is required.
- If attaching a file, confirm the binary property name is correctly specified and the file data is available.
- Check API credentials and permissions to ensure the node can add comments to tickets.
- Common error messages may include authentication failures, invalid ticket IDs, or missing required fields. Resolving these typically involves verifying credentials, input data, and API access rights.