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 retrieves detailed information about a specific Contract Service Bundle Unit from the Autotask system using its unique ID. It is useful for workflows that need to fetch and process data related to service bundle units within contracts, such as billing, service management, or contract analysis. For example, it can be used to obtain the details of a service bundle unit to verify its attributes or to integrate contract data into other business systems.
Properties
| Name | Meaning |
|---|---|
| Service Bundle Unit ID | The unique identifier of the service bundle unit to retrieve. This is a required input to specify which unit's details to fetch. |
| Add Picklist Labels | Determines whether to automatically add human-readable '_label' fields for picklist fields in the response. Labels are not added for empty values. |
| Add Reference Labels | Determines whether to automatically add human-readable '_label' fields for reference fields in the response. Labels are not added for empty values. |
| Select Columns Names or IDs. | Specifies which 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 | Determines whether user-defined fields (UDFs) should be brought up to the top level of each object instead of being nested inside the userDefinedFields array. |
Output
JSON
id- The unique identifier of the retrieved Contract Service Bundle Unit.fields*- Various properties of the Contract Service Bundle Unit, including standard and user-defined fields as specified by the selected columns.*_label- Human-readable labels for picklist and reference fields, if enabled.
userDefinedFields- Array of user-defined fields, unless flattened to top-level properties.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- If the Service Bundle Unit 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 API authentication fails, ensure the Autotask API credentials are correctly configured and have sufficient permissions.
- Selecting specific columns that do not exist may result in incomplete data or errors; verify column names or IDs are valid.
- Enabling picklist or reference labels when the fields are empty will not add labels; this is expected behavior.