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 operation retrieves multiple Billing Code records from the Autotask system using an advanced filtering mechanism. It allows users to specify complex query criteria in JSON format to filter the billing codes returned. Users can choose to return all matching records or limit the number of records returned. Additionally, the node supports options to include human-readable labels for picklist and reference fields, select specific columns to return, and flatten user-defined fields for easier access. This operation is useful for scenarios where detailed and customized retrieval of billing codes is needed, such as generating reports, syncing billing data, or integrating billing information into other systems.
Properties
| Name | Meaning |
|---|---|
| Get All | Determines whether to return all matching billing code records or limit the results to a specified maximum number. |
| Max Records | Specifies the maximum number of billing code records to return when 'Get All' is set to false. The value must be between 1 and 500. |
| Advanced Filter | A JSON string containing a 'filter' array with Autotask API query criteria to filter billing codes according to complex conditions. |
| Add Picklist Labels | Whether to automatically add '_label' fields for picklist fields to provide human-readable values alongside the raw data. |
| Add Reference Labels | Whether to automatically add '_label' fields for reference fields to provide human-readable values alongside the raw data. |
| Select Columns Names or IDs. | Allows selection of specific fields to include in the response. If no fields are selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | When enabled, user-defined fields (UDFs) are brought to the top level of each object instead of being nested inside a userDefinedFields array. |
Output
JSON
id- Unique identifier of the billing code record.fieldName- Various fields of the billing code as returned by the Autotask API, depending on selected columns.fieldName_label- Human-readable labels for picklist or reference fields if the respective options are enabled.userDefinedFields- Array of user-defined fields associated with the billing code, unless flattened option is enabled.
Dependencies
- Requires an Autotask API credential (API key or token) to authenticate requests.
- Relies on the Autotask REST API for billing code data retrieval.
Troubleshooting
- Invalid JSON in the 'Advanced Filter' property can cause parsing errors. Ensure the JSON string is correctly formatted and contains a 'filter' array as per Autotask API documentation.
- Requesting too many records without pagination or 'Get All' enabled may lead to timeouts or API limits. Use 'Max Records' to limit results or enable 'Get All' cautiously.
- Selecting invalid or unsupported columns in 'Select Columns' may result in errors or missing data. Use the 'Get Field Info' feature to confirm valid field names.
- If labels are not appearing, verify that 'Add Picklist Labels' and 'Add Reference Labels' options are enabled and that the fields have non-empty values.
- API authentication errors may occur if the Autotask API credentials are missing, expired, or incorrect. Verify credentials in the node settings.
Links
- Autotask API Basic Query Calls - Official Autotask API documentation describing how to construct query filters and retrieve data.