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 Contract Service Bundle by its ID. It is useful for users who need to fetch contract service bundle data within their workflows, such as for reporting, auditing, or integration with other systems. For example, a user can input a Contract Service Bundle ID to get all associated details, including user-defined fields and human-readable labels for picklist and reference fields.
Properties
| Name | Meaning |
|---|---|
| Service Bundle ID | The unique identifier of the contract service bundle to retrieve. |
| Add Picklist Labels | Determines whether to automatically add '_label' fields for picklist fields to provide human-readable values. Labels are not added for empty values. |
| Add Reference Labels | Determines whether to automatically add '_label' fields for reference fields to provide human-readable values. Labels are not added for empty values. |
| 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 | Determines whether user-defined fields (UDFs) are brought up to the top level of the returned object instead of being nested inside a userDefinedFields array. |
Output
JSON
id- The unique identifier of the contract service bundle.name- The name of the contract service bundle.description- Description of the contract service bundle.userDefinedFields- Array of user-defined fields associated with the contract service bundle, unless flattened.
_label - Human-readable label for picklist or reference fields, added if enabled. - Other selected fields as specified by the user in 'Select Columns'.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- If the Service Bundle 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 fields that do not exist may result in incomplete data or errors; verify field names or IDs before use.
- If labels are not appearing as expected, check that 'Add Picklist Labels' and 'Add Reference Labels' options are enabled and that the fields have valid values.