NinjaOne Tool icon

NinjaOne Tool

Read NinjaOne data and create tickets - safe subset of the NinjaOne node for AI agents

Actions28

Ticketing → Create

AI-generated

Summary

Create a NinjaOne ticket for the specified organization with a required summary and optional ticket details. The node sends a POST request to NinjaOne and returns the API response as an n8n item.

Inputs

  • Authentication (required) — Choose OAuth2 (Authorization Code) or Client Credentials and configure the matching credentials.
  • Organization ID (required) — NinjaOne organization ID to associate with the ticket.
  • Summary (required) — Ticket summary; sent to NinjaOne as the ticket subject.
  • Additional Fields — Optionally set status, type, priority, severity, assigned user, requester UID, location or device IDs, ticket form ID, parent ticket ID, comma-separated tags, follow-up time in epoch seconds, and time tracked in seconds. You can also provide comma-separated technician IDs, CC emails or user UIDs, and custom attributes as a JSON array of {attributeId, value}. Description body and HTML body, visibility, time tracked, and incident duplication are sent together as ticket description details when any of those description settings is set.

Output shape

A single item containing the created ticket API response for each input item.

The node maps each input item to a ticket creation request. If the API returns no response body, it emits {"success":true}; with Continue On Fail enabled, an error item is returned for the failed input.

Links

Discussion