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 → Count (Advanced)
AI-generatedOverview
This node operation interacts with the Autotask PSA REST API to perform an advanced count query on the Ticket History resource. It allows users to specify a complex filter in JSON format to count ticket history records that match specific criteria. This is useful for scenarios where users need to get the number of ticket history entries based on detailed conditions, such as filtering by date ranges, status changes, or specific ticket attributes.
Use Case Examples
- Count the number of ticket history records where the status changed to 'Closed' within the last month.
- Get the count of ticket history entries related to a specific ticket or customer using a custom filter.
Properties
| Name | Meaning |
|---|---|
| Advanced Filter | A JSON string containing a 'filter' array with Autotask API query criteria to specify the conditions for counting ticket history records. |
Output
JSON
count- The total number of ticket history records matching the advanced filter criteria.
Dependencies
- Requires an API key credential for Autotask PSA REST API authentication.
Troubleshooting
- Ensure the Advanced Filter JSON is correctly formatted and follows the Autotask API query criteria syntax to avoid query errors.
- Verify that the API credentials are valid and have sufficient permissions to access ticket history data.
- Common errors may include invalid JSON format, unsupported filter fields, or API authentication failures. Check error messages for details and correct the input accordingly.
Links
- Autotask API Basic Query Calls - Official documentation for constructing query filters for Autotask API calls.