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 Category Field Default → Count
AI-generatedOverview
This node interacts with the Autotask PSA REST API to perform a count operation on the Ticket Category Field Default resource. It is useful for scenarios where you need to determine the number of ticket category field defaults that meet certain criteria within your Autotask environment. For example, it can be used to count how many default field settings exist for ticket categories, which helps in managing and auditing ticket configurations.
Use Case Examples
- Count the number of default field settings for ticket categories to monitor configuration consistency.
- Retrieve the count of ticket category field defaults that match specific filters for reporting purposes.
Properties
| Name | Meaning |
|---|---|
| Fields | Specifies the fields to map and use in the count operation, allowing filtering or selection of specific data points related to ticket category field defaults. |
Output
JSON
count- The total number of ticket category field default records matching the specified criteria.
Dependencies
- Requires an API key credential for Autotask PSA REST API authentication.
Troubleshooting
- Common issues include authentication failures due to incorrect API credentials or missing permissions in Autotask.
- Errors may occur if the specified fields to map are invalid or not supported for the count operation.
- Network connectivity issues can prevent successful API calls; ensure the node can reach the Autotask API endpoint.
Links
- Autotask PSA REST API Documentation - Official documentation for the Autotask PSA REST API, providing details on available resources and operations including ticket category field defaults.