Actions159
- Related Items Actions
- Backup Actions
- Queries Actions
- Get Disk Drives
- Get Operating Systems
- Get RAID Controller Report
- Get Volumes
- Get Computer Systems
- Get Antivirus Status Report
- Get Device Health Report
- Get Custom Fields Report
- Get Installed Software Patches
- Get Custom Fields Detailed Report
- Get Installed OS Patches
- Get Pending Failed Rejected OS Patches
- Get RAID Drive Report
- Get Windows Services Report
- Get Antivirus Threats
- Get Device Usage
- Get Network Interfaces
- Get Processors
- Get Software
- Get Last Logged On Users Report
- Get Policy Overrides 1
- Get Scoped Custom Fields Report
- Get Pending Failed Rejected Software Patches
- Get Scoped Custom Fields Detailed Report
- System Actions
- Knowledge Base Articles Actions
- Get Knowledge Base Article Signed Urls
- Get Related Item Attachments Signed Urls
- Download Knowledge Base Article
- Get Knowledge Base Folder Path Content
- Upload Temp Attachments
- Get Knowledge Base Folder Content
- Get Client Knowledge Base Articles
- Upload Knowledge Base Articles
- Get Global Knowledge Base Articles
- Download Related Item Attachment
- Organization Documents Actions
- Document Templates Actions
- Checklist Templates Actions
- Organization Checklists Actions
- Location Actions
- Management Actions
- Get Custom Fields Policy Condition
- Delete Policy Condition
- Reset Alert
- Update Device
- Request Scripting Options
- Submit OS Patch Scan
- Get Installer For Location
- Get Windows Event Policy Conditions
- Create Organization
- Cancel Device Maintenance
- Reboot Devices
- Set Windows Service Configuration
- Create Location For Organization
- Update Node Role Policy Assignment For Organization
- Create Windows Event Policy Condition
- Node Approval Operation
- Control Windows Service
- Remove Device Owner
- Submit OS Patch Apply
- Get Installer
- Create Policy
- Get Windows Event Policy Condition
- Update Device Maintenance
- Reset Policy Overrides
- Set Device Owner
- Submit Software Patch Scan
- Update Location
- Reset Alert Set Activity Data
- Get Device Link
- Run Script On Device
- Submit Software Patch Apply
- Update Organization
- Create Custom Fields Policy Condition
- Get Custom Fields Policy Conditions
- Custom Fields Actions
- Ticketing Actions
- Organization Actions
- Devices Actions
- Get Device Active Jobs
- Get Device Installed Software Patches
- Get Device Processors
- Update Node Attribute Values
- Get Device Disk Drives
- Get Device Pending Failed Rejected OS Patches
- Get Device Volumes
- Get Device Alerts
- Get Device Network Interfaces
- Get Device Software
- Get Device Activities
- Get Device Last Logged On User
- Get Device Services
- Get Policy Overrides
- Get Device
- Get Device Installed OS Patches
- Get Device Pending Failed Rejected Software Patches
- Get Node Custom Fields
- Groups Actions
- Webhooks Actions
Overview
The node implements a "Create" operation for the "Ticketing" resource in the AvantGuard NinjaOne system. It allows users to create new support tickets by specifying key ticket details such as client, form, subject, status, and various optional fields. This node is useful in IT service management workflows where automated ticket creation is needed based on events or triggers, such as monitoring alerts, user requests, or system incidents.
Practical examples include:
- Automatically creating a ticket when a monitoring system detects a hardware failure.
- Logging user-reported issues into the ticketing system with relevant metadata.
- Creating task tickets for IT staff based on scheduled maintenance or audit results.
Properties
| Name | Meaning |
|---|---|
| Client Id | Numeric identifier of the client (organization) for whom the ticket is created. |
| Ticket Form Id | Numeric identifier of the ticket form to use for this ticket. |
| Subject | Textual subject/title of the ticket describing the issue or request. |
| Status | Status code of the ticket indicating its current state (e.g., open, closed). |
| Additional Body Fields | Optional collection of extra fields to enrich the ticket data: |
| - Location Id | Numeric identifier of the location related to the ticket. |
| - Node Id | Numeric identifier of the device associated with the ticket. |
| - Description | JSON object describing a comment or note on the ticket, including public visibility, body text, HTML content, and time tracked. |
| - Type | Type/category of the ticket; options are PROBLEM, QUESTION, INCIDENT, TASK. |
| - Cc | JSON object listing user IDs and email addresses to be carbon copied on ticket notifications. |
| - Assigned App User Id | Numeric ID of the app user assigned to handle the ticket. |
| - Requester Uid | String unique identifier of the requester who opened the ticket. |
| - Severity | Severity level of the ticket; options are NONE, MINOR, MODERATE, MAJOR, CRITICAL. |
| - Priority | Priority level of the ticket; options are NONE, LOW, MEDIUM, HIGH. |
| - Parent Ticket Id | Numeric ID of a parent ticket if this ticket is a subtask or related ticket. |
| - Tags | JSON array of tags/labels associated with the ticket. |
| - Attributes | JSON array of attribute objects providing additional metadata about the ticket. |
Output
The node outputs JSON data representing the newly created ticket as returned by the NinjaOne API. This typically includes all ticket details such as identifiers, status, timestamps, and any other metadata provided or generated during creation.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the AvantGuard NinjaOne API.
- The base URL for the API must be configured in the node credentials.
- Uses the
@avantguardllc/n8n-openapi-nodepackage and an OpenAPI specification (openapi.json) bundled with the node for request building.
Troubleshooting
- Invalid or missing required fields: Ensure that all required properties (Client Id, Ticket Form Id, Subject, Status) are provided and valid.
- Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- JSON parsing errors: For properties expecting JSON input (e.g., Description, Cc, Tags, Attributes), ensure the JSON syntax is correct.
- API connectivity issues: Confirm the base URL is reachable and the network connection is stable.
- Unexpected API responses: Check the NinjaOne API documentation for error codes and messages; adjust inputs accordingly.