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
This node operation retrieves log entries associated with a specific ticket by its Ticket Id from a ticketing system. It is useful for tracking the history and changes made to a ticket, such as comments, status updates, or other logged events. Practical applications include auditing ticket activity, monitoring progress, or extracting detailed ticket histories for reporting or integration purposes.
Properties
| Name | Meaning |
|---|---|
| Ticket Id | The unique identifier of the ticket for which log entries are to be retrieved. |
| Additional Query Parameters | Optional filters and pagination controls for refining the log entries returned: |
| - Type | Filter log entries by type. Options: DESCRIPTION, COMMENT, CONDITION, SAVE, DELETE |
| - Create Time | Filter log entries by their creation time (string format expected). |
| - Anchor Id | Numeric filter parameter, possibly to anchor or offset the query results. |
| - Page Size | Number of log entries to return per page; default is 500. |
Output
The output consists of JSON data representing the list of log entries for the specified ticket. Each entry typically includes details such as the type of log entry (e.g., comment or description), timestamps, and content related to the ticket's history. If binary data were involved, it would represent attachments or files linked to the log entries, but this operation focuses on JSON-formatted log information.
Dependencies
- Requires an API key credential for authenticating requests to the ticketing system.
- Needs the base URL of the ticketing API configured in the node credentials.
- Depends on the external ticketing service's API endpoint that supports querying ticket log entries by ticket ID.
Troubleshooting
- Common Issues:
- Invalid or missing Ticket Id will result in no data or errors.
- Incorrect API credentials or base URL configuration can cause authentication failures.
- Using unsupported or incorrectly formatted additional query parameters may lead to unexpected results or API errors.
- Error Messages:
- Authentication errors indicate issues with the API key or credential setup.
- "Ticket not found" or empty responses suggest the Ticket Id does not exist or has no log entries.
- Pagination limits exceeded if the page size is set too high; reduce the number accordingly.
Links and References
- Refer to the ticketing system’s official API documentation for detailed descriptions of log entry types and query parameters.
- n8n documentation on how to configure API credentials and use collection-type input properties.