Actions158
- System Actions
- Organization Actions
- Devices Actions
- Get Device
- Get Device Active Jobs
- Get Device Activities
- Get Device Alerts
- Get Device Disk Drives
- Get Device Installed OS Patches
- Get Device Installed Software Patches
- Get Device Last Logged On User
- Get Device Network Interfaces
- Get Device Pending Failed Rejected OS Patches
- Get Device Pending Failed Rejected Software Patches
- Get Device Processors
- Get Device Services
- Get Device Software
- Get Device Volumes
- Get Node Custom Fields
- Update Node Attribute Values
- Get Policy Overrides
- Groups Actions
- Queries Actions
- Get Antivirus Status Report
- Get Antivirus Threats
- Get Computer Systems
- Get Custom Fields Detailed Report
- Get Custom Fields Report
- Get Device Health Report
- Get Device Usage
- Get Disk Drives
- Get Installed OS Patches
- Get Installed Software Patches
- Get Last Logged On Users Report
- Get Network Interfaces
- Get Operating Systems
- Get Pending Failed Rejected OS Patches
- Get Pending Failed Rejected Software Patches
- Get Policy Overrides 1
- Get Processors
- Get RAID Controller Report
- Get RAID Drive Report
- Get Scoped Custom Fields Detailed Report
- Get Scoped Custom Fields Report
- Get Software
- Get Volumes
- Get Windows Services Report
- Management Actions
- Get Custom Fields Policy Conditions
- Create Custom Fields Policy Condition
- Get Windows Event Policy Conditions
- Create Windows Event Policy Condition
- Delete Policy Condition
- Get Custom Fields Policy Condition
- Get Windows Event Policy Condition
- Create Organization
- Node Approval Operation
- Reset Alert
- Reset Alert Set Activity Data
- Update Device Maintenance
- Cancel Device Maintenance
- Control Windows Service
- Update Device
- Get Device Link
- Reset Policy Overrides
- Reboot Devices
- Remove Device Owner
- Request Scripting Options
- Run Script On Device
- Set Device Owner
- Set Windows Service Configuration
- Submit OS Patch Apply
- Submit OS Patch Scan
- Submit Software Patch Apply
- Submit Software Patch Scan
- Create Location For Organization
- Get Installer
- Get Installer For Location
- Update Organization
- Update Location
- Update Node Role Policy Assignment For Organization
- Create Policy
- Ticketing Actions
- Webhooks Actions
- Related Items Actions
- Location Actions
- Backup Actions
- Knowledge Base Articles Actions
- Upload Temp Attachments
- Download Knowledge Base Article
- Get Client Knowledge Base Articles
- Get Global Knowledge Base Articles
- Get Knowledge Base Article Signed Urls
- Get Knowledge Base Folder Content
- Get Knowledge Base Folder Path Content
- Download Related Item Attachment
- Get Related Item Attachments Signed Urls
- Organization Documents Actions
- Document Templates Actions
- Checklist Templates Actions
- Custom Fields Actions
- Organization Checklists Actions
Ticketing → Create Comment
AI-generatedOverview
This node integrates with the NinjaOne API to perform various operations related to IT management. Specifically, for the Ticketing resource and the Create Comment operation, it allows users to add comments to existing tickets within the NinjaOne system. This is useful in scenarios where automated workflows need to update ticket statuses or append notes based on external triggers or processes.
For example, when a monitoring system detects an issue, this node can automatically add a comment to the relevant ticket to inform support staff of the detected problem.
Properties
| Name | Meaning |
|---|---|
| Ticket Id | The unique numeric identifier of the ticket to which the comment will be added. |
Output
The node outputs an array of JSON objects corresponding to each input item processed. Each output JSON object contains the response from the NinjaOne API after attempting to create a comment on the specified ticket. The exact structure depends on the NinjaOne API's response but generally includes details about the created comment such as its ID, content, author, and timestamps.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the NinjaOne API using OAuth2 authentication.
- The node expects the user to configure an OAuth2 API credential for NinjaOne within n8n.
- Network access to the NinjaOne API endpoints is necessary.
Troubleshooting
- Missing or invalid Ticket Id: If the
Ticket Idproperty is not provided or invalid, the API call will fail. Ensure that the ticket ID exists and is correctly passed as a number. - Authentication errors: If the OAuth2 credentials are missing, expired, or invalid, the node will throw authentication errors. Re-authenticate or update the credentials as needed.
- API request failures: Network issues or API downtime may cause request failures. Check connectivity and NinjaOne service status.
- Binary data errors: Although not applicable for this operation, other operations requiring binary data will throw errors if the expected binary property is missing.
Links and References
- NinjaOne API Documentation (general reference for API endpoints)
- n8n OAuth2 Credential Setup (for configuring OAuth2 credentials)