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 'Get Many (Advanced)' operation for the 'Ticket History' resource in the Autotask node allows users to retrieve multiple ticket history records using advanced filtering criteria. This operation is beneficial when you need to query ticket history data with complex conditions beyond simple filters, such as combining multiple criteria in a JSON filter array. For example, you can fetch all ticket history entries related to specific ticket statuses or date ranges by constructing an appropriate JSON filter. It supports returning all matching records or limiting the number of results, and can enhance the output with human-readable labels for picklist and reference fields.
Properties
| Name | Meaning |
|---|---|
| Get All | Determines whether to return all matching ticket history records or limit the results to a specified maximum number. |
| Max Records | Specifies the maximum number of ticket history records to return when 'Get All' is false. The value must be between 1 and 500. |
| Advanced Filter | A required JSON string containing a 'filter' array that defines the Autotask API query criteria for filtering ticket history records. This allows complex queries using the Autotask REST API filtering syntax. |
| Add Picklist Labels | If enabled, adds additional '_label' fields to the output for picklist fields, providing human-readable values instead of raw codes. |
| Add Reference Labels | If enabled, adds additional '_label' fields to the output for reference fields, showing human-readable values. |
| 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. |
| Flatten User-Defined Fields | If enabled, user-defined fields (UDFs) are moved to the top level of each returned object instead of being nested inside a 'userDefinedFields' array. |
Output
JSON
id- Unique identifier of the ticket history record.fieldName- Name of the field that was changed in the ticket history.oldValue- Previous value of the field before the change.newValue- New value of the field after the change.changeDate- Date and time when the change was made.changedBy- Reference to the user or entity who made the change._label- Additional human-readable labels for picklist or reference fields if enabled.userDefinedFields- Array of user-defined fields related to the ticket history record, unless flattened.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- Invalid JSON in the 'Advanced Filter' property will cause the operation to fail. Ensure the JSON string is correctly formatted and follows the Autotask API filter syntax.
- Requesting more than 500 records when 'Get All' is false will be limited to 500 due to API constraints.
- If no records are returned, verify that the filter criteria match existing ticket history data.
- Enabling 'Add Picklist Labels' or 'Add Reference Labels' may increase response size and processing time.
- Incorrect field names in 'Select Columns' or 'Advanced Filter' may cause errors or empty results; use 'Get Field Info' to confirm exact field names.
Links
- Autotask API Basic Query Calls - Official Autotask documentation describing how to construct advanced filter queries for API calls.