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
Billing Code → Get Many (Advanced)
AI-generatedOverview
The node interacts with Kaseya's Autotask PSA REST API to retrieve multiple billing code 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 fields. This operation is useful for scenarios where users need to query billing codes with specific conditions, such as filtering by attributes or retrieving a subset of billing codes for reporting or integration purposes.
Use Case Examples
- Retrieve all billing codes that match a complex filter criteria defined in JSON format.
- Fetch a limited number of billing codes (e.g., max 10) with specific fields selected for integration with another system.
- Use advanced filters to get billing codes with certain attributes and automatically add human-readable labels for picklist and reference fields.
Properties
| Name | Meaning |
|---|---|
| Get All | Whether to return all results or only up to a given limit (maxRecords). |
| Max Records | Maximum number of billing code records to return when 'Get All' is false. Range is 1 to 500. |
| Advanced Filter | A JSON string containing a 'filter' array with Autotask API query criteria to filter billing codes. |
| Add Picklist Labels | Whether to automatically add '_label' fields for picklist fields with human-readable values in the output. |
| Add Reference Labels | Whether to automatically add '_label' fields for reference fields with human-readable values in the output. |
| Select Columns Names or IDs. | Choose which billing code fields 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 billing code object instead of nested in the userDefinedFields array. |
Output
JSON
id- Unique identifier of the billing code record.fieldName_label- Human-readable labels for picklist or reference fields if enabled in input properties.
Dependencies
- Kaseya Autotask PSA REST API
- An API key credential for authentication
Troubleshooting
- Common issues include invalid JSON in the advanced filter causing API query errors. Ensure the filter JSON is correctly formatted and follows Autotask API query criteria.
- If the node returns no data, verify the filter criteria actually match existing billing codes.
- Errors related to authentication indicate missing or incorrect API credentials; verify the API key and integration code are correctly configured.
- Selecting too many fields or requesting too many records may lead to performance issues or API rate limits; adjust maxRecords or filter criteria accordingly.
Links
- Autotask REST API Documentation - Official documentation for the Autotask REST API used by this node.
- n8n Autotask Node GitHub Repository - Source code and additional information about the n8n Autotask integration.