Actions524
- AI Helper Actions
- Tool Actions
- API Threshold Actions
- Appointment Actions
- Billing Code Actions
- Billing Items Actions
- Change Request Link Actions
- Checklist Library Actions
- Checklist Library Item Actions
- Classification Icon Actions
- Company Actions
- Company Alert Actions
- Company Location Actions
- Company Note Actions
- Company Webhook Actions
- Company Site Configuration Actions
- Configuration Item Actions
- Configuration Item Billing Product Association 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
- Contact Actions
- Contact Webhook Actions
- Contact Groups Actions
- Contact Group Contacts Actions
- Contract Actions
- Contract Block Actions
- Contract Block Hour Factor Actions
- Contract Billing Rule Actions
- Contract Charge Actions
- Contract Exclusion Billing Code 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 Rate Actions
- Contract Role Costs Actions
- Contract Retainer Actions
- Contract Service Actions
- Contract Service Adjustment Actions
- Contract Service Bundle Adjustment Actions
- Contract Service Bundle Actions
- Contract Service Bundle Unit Actions
- Contract Ticket Purchase Actions
- Department Actions
- Project Phase Actions
- Quote Item Actions
- Quote Location Actions
- Quote Template Actions
- Resource Actions
- Resource Role Actions
- Resource Role Queue Actions
- Search Filter Actions
- Service Actions
- Service Call Actions
- Subscription Actions
- Subscription Period Actions
- Ticket Category Actions
- Ticket Category Field Default Actions
- Ticket History Actions
- Ticket Note Actions
Ticket History → Get Many
AI-generatedOverview
This node operation retrieves multiple ticket history records from the Autotask PSA system for a specified ticket. It is useful for scenarios where you need to fetch the history or audit trail of changes and updates related to a particular ticket, such as tracking progress, changes, or comments over time.
Use Case Examples
- Fetch all history entries for a specific ticket to analyze the sequence of updates.
- Retrieve a limited number of recent history records for a ticket to display in a dashboard or report.
Properties
| Name | Meaning |
|---|---|
| Ticket ID | The ID of the ticket to get history for. This is the only allowed filter. |
| Get All | Whether to return all results or only up to a given limit |
| Max Records | Max number of records to return (1-500) |
| Add Picklist Labels | Whether to automatically add "_label" fields for picklist fields with human-readable values (no labels will be added for empty values) |
| Add Reference Labels | Whether to automatically add "_label" fields for reference fields with human-readable values (no labels will be added for empty values) |
| 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. When enabled, UDFs will be accessible as top-level properties instead of being nested in the userDefinedFields array |
Output
JSON
id- Unique identifier of the ticket history recordticketID- The ID of the ticket this history record belongs tochangeDate- Date and time when the change was madechangedBy- User or system that made the changechangeDescription- Description of the change made in the ticket historyadditionalFields- Additional optional fields related to the ticket history recorduserDefinedFields- User-defined fields associated with the ticket history record, if not flattened_label- Human-readable labels for picklist or reference fields, if enabled
Dependencies
- An API key credential for Autotask PSA REST API
Troubleshooting
- Ensure the Ticket ID is valid and exists in the Autotask system to avoid errors.
- If no records are returned, verify that the ticket has history entries and that filters are correctly set.
- Check API credentials and permissions if authentication errors occur.
- If the node fails to return expected fields, verify the 'Select Columns' property and adjust accordingly.
Links
- Autotask PSA REST API Documentation - Official documentation for the Autotask PSA REST API, useful for understanding available endpoints and data structures.