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 (Advanced)
AI-generatedOverview
The node interacts with Kaseya's Autotask PSA REST API to retrieve multiple ticket category records based on advanced filtering criteria. It supports fetching all records or limiting the number of records returned, applying complex JSON-based filters, and customizing the output with options like adding human-readable labels for picklist and reference fields, selecting specific columns, and flattening user-defined fields. This operation is useful for scenarios where users need to query and analyze ticket categories with precise filtering and tailored data output, such as generating reports or integrating ticket category data into other systems.
Use Case Examples
- Retrieve all ticket categories that match specific criteria defined in an advanced JSON filter.
- Fetch a limited number of ticket categories with selected fields and include human-readable labels for easier interpretation.
Properties
| Name | Meaning |
|---|---|
| Get All | Whether to return all results or only up to a given limit (returnAll boolean). If false, the number of records returned is limited by Max Records. |
| Max Records | Maximum number of ticket category records to return when Get All is false. Value range is 1 to 500. |
| Advanced Filter | A JSON string containing a "filter" array with Autotask API query criteria to filter the ticket categories returned. This allows complex and precise filtering based on Autotask's API capabilities. |
| Add Picklist Labels | Whether to automatically add "_label" fields for picklist fields with human-readable values in the output. No labels are added for empty values. |
| Add Reference Labels | Whether to automatically add "_label" fields for reference fields with human-readable values in the output. No labels are added for empty values. |
| Select Columns Names or IDs. | Choose which fields to include in the response. If no fields are selected, all fields will be returned. The ID field is always included regardless of selection. |
| Flatten User-Defined Fields | Whether to bring user-defined fields up to the top level of each object instead of nesting them in the userDefinedFields array, making them more accessible. |
Output
JSON
id- Unique identifier of the ticket category record.name- Name of the ticket category.description- Description of the ticket category.userDefinedFields- Array of user-defined fields associated with the ticket category, unless flattened._label- Additional human-readable labels for picklist or reference fields if enabled.
Dependencies
- An API key credential for Autotask PSA REST API authentication.
Troubleshooting
- Common issues include invalid JSON in the Advanced Filter property, which will cause API query errors. Users should validate JSON syntax and structure before use.
- If the API credentials are incorrect or missing, authentication errors will occur. Ensure valid Autotask API credentials are configured.
- Selecting too many records without setting limits may lead to performance issues or API rate limiting. Use the Get All and Max Records properties wisely.
- If human-readable labels are not appearing, verify that the Add Picklist Labels and Add Reference Labels options are enabled and that the fields have corresponding label data.
Links
- Autotask API Basic Query Calls - Official Autotask API documentation for constructing filter queries.
- n8n Autotask Node GitHub Repository - Source code and documentation for the Autotask node in n8n.