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 interacts with the Autotask REST API to perform various operations on different resources. Specifically, for the 'Ticket' resource with the 'Count' operation, it counts the number of tickets matching specified criteria. This is useful for workflows that need to monitor ticket volumes, generate reports, or trigger actions based on ticket counts. For example, a user might count open tickets to assess workload or trigger alerts when ticket counts exceed thresholds.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which ticket fields to map and use in the operation. This property allows users to specify and map the relevant ticket fields for the count operation, supporting custom field selection and mapping. |
Output
JSON
count- The total number of tickets matching the specified criteria.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- If the node throws an error indicating unsupported resource, ensure the 'resource' parameter is set to 'ticket'.
- Authentication errors may occur if the Autotask API credentials are missing or invalid; verify the API key credential configuration.
- Incorrect field mappings in the 'Fields' property can cause unexpected results or errors; ensure fields are correctly mapped and supported by the API.
- Network or API rate limit issues may cause failures; check network connectivity and Autotask API usage limits.