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 detailed information about a specific Billing Code by its ID. It is useful in scenarios where you need to fetch billing code details for invoicing, reporting, or integration with other systems. For example, you can use it to get the description, rates, or other metadata of a billing code to automate billing workflows or synchronize data with accounting software.
Properties
| Name | Meaning |
|---|---|
| Billing Code ID | The unique identifier of the billing code to retrieve. This is a required input to specify which billing code's details to fetch. |
| Add Picklist Labels | Determines whether to automatically add human-readable "_label" fields for picklist fields in the response. This helps in understanding picklist values without needing to look up codes. |
| Add Reference Labels | Determines whether to automatically add human-readable "_label" fields for reference fields in the response. This makes reference fields easier to interpret. |
| 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 regardless of selection. |
| Flatten User-Defined Fields | When enabled, user-defined fields (UDFs) are brought up to the top level of the returned object instead of being nested inside a userDefinedFields array, simplifying access to these fields. |
Output
JSON
id- The unique identifier of the billing code.name- The name of the billing code.description- Description or details about the billing code.userDefinedFields- An array of user-defined fields associated with the billing code, unless flattened.
_label - Human-readable labels for picklist fields, added if 'Add Picklist Labels' is enabled._label - Human-readable labels for reference fields, added if 'Add Reference Labels' is enabled.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- If the Billing Code ID is invalid or not found, the node will throw an error indicating the resource could not be retrieved. Verify the ID is correct.
- If authentication fails, ensure the Autotask API credentials are correctly configured and have sufficient permissions.
- Selecting invalid or non-existent fields in 'Select Columns' may result in incomplete or error responses. Use the provided dropdown or valid field IDs.
- If picklist or reference labels are not appearing as expected, verify that the corresponding options ('Add Picklist Labels' and 'Add Reference Labels') are enabled.
Links
- Autotask Billing Codes API Documentation - Official Autotask REST API documentation for Billing Codes resource.
- n8n Autotask Node Documentation - General documentation on using the Autotask node within n8n workflows.