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 → Get Many
AI-generatedOverview
This node operation retrieves multiple ticket categories from the Autotask PSA system. It is useful for scenarios where you need to list or process many ticket categories at once, such as generating reports, syncing data, or filtering tickets by category. For example, a user might want to fetch all ticket categories to display them in a dropdown menu or to analyze ticket distribution across categories.
Use Case Examples
- Fetch all ticket categories to populate a selection list in a customer support dashboard.
- Retrieve a limited number of ticket categories for quick display in an internal tool.
Properties
| Name | Meaning |
|---|---|
| Get All | Whether to return all ticket category results or only up to a given limit. |
| Max Records | Maximum number of ticket category records to return when not returning all. Range is 1 to 500. |
| Add Picklist Labels | Whether to automatically add human-readable label fields for picklist fields in the response. |
| Add Reference Labels | Whether to automatically add human-readable label fields for reference fields in the response. |
| Select Columns Names or IDs. | Choose which fields of the ticket category to include in the response. If none selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | Whether to bring user-defined fields up to the top level of each ticket category object instead of nested in an array. |
Output
JSON
id- Unique identifier of the ticket category.name- Name of the ticket category.description- Description of the ticket category.picklist_label_fields- Human-readable labels for picklist fields if enabled.reference_label_fields- Human-readable labels for reference fields if enabled.userDefinedFields- Array of user-defined fields if not flattened; otherwise, user-defined fields are top-level properties.
Dependencies
- Autotask PSA REST API
- API authentication credentials
Troubleshooting
- Ensure API credentials are correctly configured and have permissions to access ticket categories.
- If no results are returned, verify that ticket categories exist in the Autotask system and that filters (if any) are correct.
- If the node fails with rate limit errors, check API usage limits and consider enabling rate limiting or retry logic.
Links
- Autotask PSA REST API Documentation - Official API documentation for Autotask PSA REST API.