Actions389
- Contract Actions
- Ticket History Actions
- Ticket Note Webhook Actions
- Ticket Note Actions
- Ticket Webhook Actions
- Time Entry Actions
- Resource Actions
- Role Actions
- Resource Role Actions
- Search Filter Actions
- Service Actions
- Skill Actions
- Service Call Actions
- Survey Results Actions
- Survey Actions
- Ticket Actions
- Opportunity Actions
- Notification History Actions
- Invoice Actions
- Product Actions
- Product Vendor Actions
- Project Actions
- Project Charge Actions
- Project Phase Actions
- Project Task Actions
- Project Note Actions
- Contract Retainer Actions
- Contract Service Actions
- Contract Service Adjustment Actions
- Contract Service Bundle Actions
- Contract Service Bundle Unit Actions
- Contract Service Bundle Adjustment Actions
- Contract Ticket Purchase Actions
- Contract Service Unit Actions
- Domain Registrar Actions
- Holiday Actions
- Holiday Set Actions
- Contract Exclusion Billing Code Actions
- Contract Rate Actions
- Contract Exclusion Role Actions
- Contract Exclusion Sets Actions
- Contract Exclusion Set Excluded Role Actions
- Contract Exclusion Set Excluded Work Type Actions
- Contract Milestone Actions
- Contract Note Actions
- Contract Role Costs Actions
- Contact Groups Actions
- Contact Actions
- Contact Webhook Actions
- Contact Group Contacts Actions
- Contract Block Hour Factor Actions
- Contract Block Actions
- Contract Billing Rule Actions
- Contract Charge Actions
- Configuration Item Category Actions
- Configuration Item Category UDF Association Actions
- Configuration Item DNS Record Actions
- Configuration Item Note Actions
- Configuration Item Related Item Actions
- Configuration Item SSL Subject Alternative Name Actions
- Configuration Item Type Actions
- Configuration Item Webhook Actions
- Company Alert Actions
- Company Actions
- Billing Code Actions
- Company Location Actions
- Company Note Actions
- Company Webhook Actions
- Configuration Item Actions
- Configuration Item Billing Product Association Actions
Overview
The 'Ticket History - Get' operation retrieves detailed historical records of a specific ticket from the Autotask system. It allows users to fetch the history of changes or events related to a ticket by specifying the ticket's ID or a specific ticket history record ID. This operation is useful for tracking the lifecycle and updates of support or service tickets, enabling audit trails, and understanding ticket progression over time.
Properties
| Name | Meaning |
|---|---|
| Ticket History ID | The unique identifier of the specific ticket history record to retrieve. |
| Ticket ID | The unique identifier of the ticket for which the history is requested. This is the only allowed filter when retrieving multiple history records. |
| Add Picklist Labels | Determines whether to automatically add human-readable '_label' fields for picklist fields in the response, improving readability by showing descriptive values instead of raw codes. |
| Add Reference Labels | Determines whether to automatically add human-readable '_label' fields for reference fields in the response, providing descriptive values for referenced entities. |
| Select Columns Names or IDs. | Allows selection of specific fields to include in the response. If no fields are selected, all fields are returned. The ID field is always included regardless of selection. |
| Flatten User-Defined Fields | When enabled, user-defined fields (UDFs) are brought to the top level of each object instead of being nested inside a userDefinedFields array, simplifying access to these fields. |
Output
JSON
id- The unique identifier of the ticket history record.ticketID- The ID of the ticket associated with this history record.changeDate- The date and time when the change or event occurred.changedBy- Identifier or name of the user who made the change.fieldName- The name of the field that was changed.oldValue- The previous value before the change.newValue- The new value after the change.picklistLabels- Optional human-readable labels for picklist fields if 'Add Picklist Labels' is enabled.referenceLabels- Optional human-readable labels for reference fields if 'Add Reference Labels' is enabled.userDefinedFields- Array of user-defined fields related to the ticket history, or flattened to top-level properties if 'Flatten User-Defined Fields' is enabled.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- If the node returns an error about missing or invalid Ticket History ID or Ticket ID, verify that the provided IDs are correct and exist in the Autotask system.
- If no data is returned, ensure that the ticket has history records and that the correct filters are applied.
- Errors related to permissions may indicate that the API key used does not have sufficient rights to access ticket history data.
- If picklist or reference labels are missing despite enabling the options, check if the fields actually have associated labels in Autotask.
- When selecting specific columns, ensure that the field names or IDs are valid; invalid selections may cause incomplete or failed responses.