NinjaOne icon

NinjaOne

Interact with the NinjaOne API

Overview

The node integrates with the NinjaOne API to manage tickets, specifically allowing users to add comments to existing tickets. This operation is useful in scenarios where you want to programmatically update a ticket's discussion thread by appending new information, feedback, or status updates. For example, an IT support team could automate adding diagnostic notes or customer responses to tickets as part of their workflow.

Properties

Name Meaning
Ticket ID The unique identifier of the ticket to which the comment will be added (required).
Comment Body The text content of the comment to add (required).
Comment Public Boolean flag indicating whether the comment should be visible publicly or internally.
Comment Time Tracked Number of seconds tracked for this comment, representing time spent related to it.
Binary Property Name of the binary property containing a file to attach to the comment (optional).

Output

The node outputs JSON data representing the result of the "Add Comment" operation on the ticket. This typically includes details about the newly created comment such as its ID, content, visibility, and any metadata returned by the NinjaOne API.

If a binary file is attached via the specified binary property, the node handles uploading that file along with the comment, but the output remains focused on the comment's JSON representation.

Dependencies

  • Requires an API authentication token credential configured in n8n to access the NinjaOne API.
  • The base URL for the API can be customized via credentials; otherwise, it defaults to https://api.ninjaone.com.
  • No additional external dependencies are required beyond the NinjaOne API access.

Troubleshooting

  • Missing Required Fields: Errors may occur if the Ticket ID or Comment Body is not provided. Ensure these fields are filled.
  • Authentication Errors: If the API key or OAuth2 token is invalid or expired, the node will fail to authenticate. Verify and refresh credentials as needed.
  • File Attachment Issues: If specifying a binary property for attachment, ensure the binary data exists and is correctly referenced; otherwise, the upload may fail.
  • API Rate Limits: Frequent requests might hit NinjaOne API rate limits, causing temporary failures. Implement retry logic or reduce request frequency.
  • Permission Denied: The authenticated user must have permission to add comments to the specified ticket; otherwise, the API will reject the request.

Links and References

Discussion