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 interacts with the Autotask REST API to retrieve multiple billing code records. It supports fetching a list of billing codes with options to limit the number of records or retrieve all available records. The node allows users to specify which fields to include in the output, and can enrich the data by adding human-readable labels for picklist and reference fields. It also supports flattening user-defined fields for easier access. This is useful for automating workflows that require billing code data, such as financial reporting, invoicing automation, or integration with other business systems.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields of the billing code resource to retrieve and map in the output. Supports custom mapping and auto-mapping of fields. |
| Get All | Determines whether to return all 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 false. Valid range is 1 to 500. |
| Add Picklist Labels | If enabled, adds additional fields with '_label' suffix containing human-readable labels for picklist fields. |
| Add Reference Labels | If enabled, adds additional fields with '_label' suffix containing human-readable labels for reference fields. |
| Select Columns Names or IDs. | Allows selection of specific fields to include in the response. If none selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | If enabled, user-defined fields (UDFs) are moved to the top level of each billing code object instead of being nested. |
Output
JSON
billingCodes - Individual fields of each billing code as specified by the selected or mapped fields.
_label- Optional human-readable labels for picklist or reference fields, appended with '_label' suffix.userDefinedFields- Array of user-defined fields if flattening is disabled; otherwise, UDFs appear as top-level properties.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- If no records are returned, verify that the Autotask API credentials are correct and have sufficient permissions.
- Ensure that the 'Max Records' value is within the allowed range (1-500) when 'Get All' is false.
- If field mapping fails, check that the specified fields exist for the billing code resource and are spelled correctly.
- Network or API errors may occur if the Autotask service is unavailable; retry after some time.
- If labels are not appearing, confirm that 'Add Picklist Labels' and 'Add Reference Labels' options are enabled.