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 → Get Ticket Log Entries By Ticket Id
AI-generatedOverview
This node operation retrieves log entries associated with a specific ticket in a ticketing system. It allows users to fetch detailed logs filtered by type, creation time, and pagination parameters. This is useful for tracking the history or changes made to a ticket, such as comments added, status updates, or other logged events.
Practical examples include:
- Fetching all comment entries on a support ticket to review customer interactions.
- Retrieving only description changes to audit modifications.
- Paginating through large sets of log entries for tickets with extensive histories.
Properties
| Name | Meaning |
|---|---|
| Ticket Id | The unique identifier of the ticket for which to retrieve log entries. |
| Type | The category of log entries to retrieve. Options: DESCRIPTION, COMMENT, CONDITION, SAVE, DELETE. |
| Create Time | Filter log entries created at a specific time (exact format depends on API expectations). |
| Anchor Id | An anchor point ID used for pagination or filtering within the log entries. |
| Page Size | Number of log entries to return per request, defaulting to 500. |
Output
The output is an array of JSON objects representing the retrieved ticket log entries. Each object corresponds to a log entry matching the query parameters. The exact structure of each log entry depends on the external API response but typically includes details like entry type, timestamp, content, and related metadata.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential configured for authenticating with the NinjaOne API.
- The node uses OAuth2 authentication under the credential named generically here as "an API key credential".
- The node sends HTTP GET requests to endpoints following the pattern
/v2/tickets/{ticketId}/logwith query parameters based on input properties.
Troubleshooting
Common issues:
- Invalid or missing Ticket Id will result in errors or empty responses.
- Incorrect formatting of the Create Time filter may cause the API to reject the request.
- Exceeding page size limits might lead to truncated results or API errors.
- Missing or expired API credentials will cause authentication failures.
Error messages:
- Errors returned from the API are passed through; typical messages include "Unauthorized" (check API credentials), "Not Found" (invalid Ticket Id), or "Bad Request" (invalid query parameters).
- If no binary data is found when expected (not applicable here but relevant for other operations), the node throws a descriptive error.
Links and References
- NinjaOne API documentation (general reference): NinjaOne API Docs
- n8n documentation on creating custom nodes and using credentials: n8n Docs