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
This node operation counts the number of history entries for a specific ticket in the Autotask system. It is useful for workflows that need to monitor or analyze the volume of changes or updates made to a ticket over time. For example, it can be used to trigger alerts if a ticket has an unusually high number of history entries, or to generate reports on ticket activity.
Properties
| Name | Meaning |
|---|---|
| Ticket ID | The unique identifier of the ticket for which the history count is requested. This is the only filter allowed to specify which ticket's history to count. |
Output
JSON
count- The total number of history entries associated with the specified ticket.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- If the Ticket ID is missing or invalid, the node will throw an error indicating that the ticket could not be found or the request is invalid. Ensure the Ticket ID is correct and exists in Autotask.
- API authentication errors may occur if the provided credentials are incorrect or expired. Verify the API key credential is valid and has sufficient permissions.
- Network or connectivity issues with the Autotask API endpoint can cause failures. Check network access and API service status.