NinjaOne icon

NinjaOne

Consume NinjaOne API

Actions158

Ticketing → Update

AI-generated

Overview

This node allows updating a ticket in a ticketing system via the NinjaOne API. It is designed to modify existing tickets by specifying their unique identifier and providing updated details such as status, subject, priority, severity, and other metadata.

Common scenarios where this node is beneficial include:

  • Automating ticket updates based on external triggers or workflows.
  • Synchronizing ticket information from other systems.
  • Programmatically changing ticket status or reassigning tickets without manual intervention.

For example, you could use this node to update the status of a support ticket to "resolved" after an automated diagnostic script completes, or to assign a ticket to a different user based on workload balancing.

Properties

Name Meaning
Ticket Id The unique numeric identifier of the ticket to update.
Version The version number of the ticket (used for concurrency control).
Client Id Identifier of the client organization associated with the ticket.
Ticket Form Id Identifier of the form used for the ticket.
Location Id Identifier of the location related to the ticket.
Node Id Identifier of the device or node related to the ticket.
Subject The subject or title of the ticket.
Status Current status code of the ticket (e.g., open, closed).
Type Type/category of the ticket. Options: PROBLEM, QUESTION, INCIDENT, TASK.
Cc JSON object containing arrays of user IDs and email addresses to be CC'd on the ticket.
Assigned App User Id Numeric ID of the user assigned to the ticket.
Requester Uid Unique string identifier of the user who requested the ticket.
Severity Severity level of the ticket. Options: NONE, MINOR, MODERATE, MAJOR, CRITICAL.
Priority Priority level of the ticket. Options: NONE, LOW, MEDIUM, HIGH.
Parent Ticket Id Numeric ID of a parent ticket if this ticket is a sub-ticket.
Tags JSON array of tags/labels associated with the ticket.
Attributes JSON array of attribute objects related to the ticket (each with id and attributeId fields).

Output

The node outputs an array of items, each containing a json field with the response data from the NinjaOne API after updating the ticket. This typically includes the updated ticket details as returned by the API.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the NinjaOne API using OAuth2 authentication.
  • The node depends on the NinjaOne API endpoint /v2/tickets/{ticketId} (implied by the update operation).
  • Proper API credentials must be configured in n8n to authenticate requests.

Troubleshooting

  • Missing Required Fields: Ensure all required properties like Ticket Id, Version, Client Id, Ticket Form Id, Subject, Status, and Requester Uid are provided; otherwise, the API may reject the request.
  • Invalid JSON in Cc, Tags, or Attributes: These fields expect valid JSON strings. Malformed JSON will cause parsing errors.
  • Version Conflicts: If the ticket version is outdated, the API might reject the update to prevent overwriting concurrent changes. Use the latest version number.
  • Authentication Errors: Verify that the OAuth2 credentials are correctly set up and have sufficient permissions.
  • API Rate Limits or Network Issues: Temporary failures can occur due to rate limiting or connectivity problems; consider enabling "Continue On Fail" to handle such cases gracefully.

Links and References

Discussion