Autotask icon

Autotask

Interact with Kaseya's Autotask PSA REST API to manage companies, tickets, contracts, and more.

Actions524

Ticket History → Get

AI-generated

Overview

This node operation retrieves a specific ticket history record from the Autotask PSA system using the provided Ticket History ID. It is useful for scenarios where detailed information about a particular change or event in a ticket's lifecycle is needed, such as auditing ticket updates or tracking changes over time.

Use Case Examples

  1. Retrieve the history of a ticket to audit changes made by support agents.
  2. Fetch a specific ticket history entry to display detailed information in a custom dashboard.

Properties

Name Meaning
Ticket History ID The ID of the ticket history to retrieve, used to specify which ticket history record to fetch.
Ticket ID The ID of the ticket to get history for, used as a filter to narrow down the ticket history records.
Add Picklist Labels Whether to automatically add '_label' fields for picklist fields with human-readable values, enhancing the readability of picklist data.
Add Reference Labels Whether to automatically add '_label' fields for reference fields with human-readable values, improving the clarity of reference data.
Select Columns Names or IDs. Choose which fields to include in the response. If no fields are selected, all fields will be returned. The ID field is always included regardless of selection.
Flatten User-Defined Fields Whether to bring user-defined fields up to the top level of each object, making UDFs more accessible as top-level properties instead of nested in the userDefinedFields array.

Output

JSON

  • id - The unique identifier of the ticket history record.
  • ticketID - The ID of the ticket associated with the history record.
  • changeDate - The date and time when the change was made.
  • changedBy - The user or system that made the change.
  • changeDetails - Details about what was changed in the ticket history entry.

Dependencies

  • An API key credential for Autotask PSA REST API

Troubleshooting

  • Ensure the Ticket History ID provided is valid and exists in the Autotask system to avoid 'not found' errors.
  • Check API credentials and permissions if the node fails to retrieve data due to authentication issues.
  • If no fields are returned, verify the 'Select Columns' property to ensure the desired fields are included.
  • Enable 'Add Picklist Labels' and 'Add Reference Labels' to improve data readability, but disable if performance issues occur due to additional processing.

Links

Discussion