NinjaOne icon

NinjaOne

Interact with the NinjaOne API
Join our community

Actions30

Overview

The node enables creating a new ticket in the NinjaOne system via its API. It is useful for automating IT service management workflows, such as logging incidents, tasks, or questions directly from other systems or triggers. For example, when an alert is generated by monitoring software, this node can create a corresponding ticket automatically to track and resolve the issue.

Properties

Name Meaning
Version Version number for optimistic locking
Client ID Organization ID
Ticket Form ID ID of the ticket form
Location ID Location ID
Node ID Device/Node ID
Summary Ticket summary or subject
Status Ticket status: New, Open, Waiting for Customer, Hold
Type Ticket type: Problem, Task, Question
CC User IDs Comma-separated list of user UIDs to CC on ticket
CC Emails Comma-separated list of email addresses to CC on ticket
Assigned App User ID ID of the assigned technician
Requester UID UID of the ticket requester
Severity Ticket severity level: None, Minor, Moderate, Major, Critical
Priority Ticket priority level: None, Low, Medium, High, Critical
Parent Ticket ID ID of the parent ticket for sub-tickets
Tags Comma-separated list of tags for the ticket
Attributes JSON string representing custom attributes for the ticket
Organization Department or organization assignment
Total Time Tracked Total time tracked in seconds
Description Ticket description (required)
Description Public Whether the description is public (boolean)
HTML Body HTML formatted description
Time Tracked Time tracked for this entry in seconds
Duplicate in Incidents Whether to duplicate the ticket in incidents (boolean)

Output

The node outputs the created ticket data in the json field of the output item. This typically includes all details of the newly created ticket as returned by the NinjaOne API, such as ticket ID, status, summary, assigned user, timestamps, and any other metadata. The node does not output binary data.

Dependencies

  • Requires an API authentication credential configured in n8n to connect to the NinjaOne API.
  • The base URL for the API can be customized via credentials but defaults to https://api.ninjaone.com.
  • The node depends on the NinjaOne API being accessible and the provided credentials having permission to create tickets.

Troubleshooting

  • Authentication errors: Ensure the API key or OAuth2 token is valid and has sufficient permissions.
  • Validation errors: Required fields like "Description" must be provided; missing these will cause the API to reject the request.
  • Incorrect option values: Status, Type, Severity, and Priority must be one of the allowed options; invalid values will cause errors.
  • API connectivity issues: Check network access and NinjaOne API availability.
  • Malformed JSON in Attributes: If providing custom attributes, ensure the JSON string is well-formed.

Links and References

Discussion