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 (Advanced)
AI-generatedOverview
The node interacts with Kaseya's Autotask PSA REST API to retrieve multiple ticket history records based on advanced filtering criteria. It supports fetching all records or limiting the number of records returned, applying complex JSON-based filters, and customizing the output fields. This operation is useful for users who need to query detailed ticket history data with specific conditions, such as filtering by date ranges, status changes, or other ticket history attributes.
Use Case Examples
- Retrieve all ticket history entries for a specific ticket within a date range using an advanced JSON filter.
- Fetch up to 100 ticket history records with specific status changes and include human-readable labels for picklist and reference fields.
Properties
| Name | Meaning |
|---|---|
| Get All | Whether to return all results or only up to a given limit (max 500). |
| Max Records | Maximum number of ticket history records to return when 'Get All' is false, between 1 and 500. |
| Advanced Filter | A JSON string containing a 'filter' array with Autotask API query criteria to filter ticket history records. This allows complex queries based on ticket history fields. |
| Add Picklist Labels | Whether to automatically add '_label' fields for picklist fields with human-readable values in the output. |
| Add Reference Labels | Whether to automatically add '_label' fields for reference fields with human-readable values in the output. |
| Select Columns Names or IDs | Choose which ticket history fields to include in the response. If no fields are selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | Whether to bring user-defined fields up to the top level of each ticket history object instead of nesting them in the userDefinedFields array. |
Output
JSON
id- Unique identifier of the ticket history record.ticketID- Identifier of the ticket associated with the history record.dateTime- Timestamp of the history event.fieldName- Name of the field that was changed.oldValue- Previous value of the field before the change.newValue- New value of the field after the change.userID- Identifier of the user who made the change.userName_label- Human-readable name of the user who made the change, if 'Add Reference Labels' is enabled.fieldName_label- Human-readable label for the field name, if 'Add Picklist Labels' is enabled.userDefinedFields- Array of user-defined fields related to the ticket history record, unless flattened.
Dependencies
- Kaseya Autotask PSA REST API
- API authentication token or API key credential
Troubleshooting
- Ensure the advanced filter JSON is correctly formatted and matches the Autotask API query criteria syntax to avoid query errors.
- If no records are returned, verify the filter criteria and date ranges are correct and that the ticket history data exists for those conditions.
- API rate limits may apply; if requests fail due to rate limiting, consider retrying after some time or optimizing the query to reduce load.
- If 'Add Picklist Labels' or 'Add Reference Labels' options are enabled but labels do not appear, confirm that the fields support labels and that the API returns label data.
Links
- Autotask REST API Documentation - Official documentation for Autotask REST API including query syntax and resource details.
- n8n Autotask Node GitHub Repository - Source code and documentation for the n8n Autotask integration node.