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 Contract Service Bundle Unit records from the Autotask REST API using advanced filtering criteria. It is useful for users who need to query and extract detailed data about contract service bundle units with complex filters, such as specific field values or conditions. For example, a user can fetch all contract service bundle units that meet certain status or date criteria, optionally limiting the number of records returned or retrieving all matching records.
Properties
| Name | Meaning |
|---|---|
| Get All | Determines whether to return all matching records or limit the results to a specified maximum number. |
| Max Records | Specifies the maximum number of records to return when 'Get All' is 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 the contract service bundle units returned. |
| Add Picklist Labels | If enabled, adds additional '_label' fields to the output for picklist fields, providing human-readable values. |
| Add Reference Labels | If enabled, adds additional '_label' fields to the output for reference fields, providing human-readable 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 | If enabled, user-defined fields (UDFs) are moved to the top level of each returned object instead of being nested inside a userDefinedFields array. |
Output
JSON
id- Unique identifier of the contract service bundle unit.fieldName- Various fields representing the contract service bundle unit's properties as returned by the Autotask API, filtered and selected according to input parameters.picklistField_label- Human-readable labels for picklist fields, added if 'Add Picklist Labels' is enabled.referenceField_label- Human-readable labels for reference fields, added if 'Add Reference Labels' is enabled.userDefinedFields- User-defined fields nested inside userDefinedFields array, or flattened to top-level if 'Flatten User-Defined Fields' is enabled.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- Invalid JSON in 'Advanced Filter' property can cause query failures. Ensure the JSON string is well-formed and follows Autotask API filter syntax.
- Requesting more than 500 records when 'Get All' is false will limit results to 500 due to API constraints.
- Selecting invalid or unsupported fields in 'Select Columns' may result in errors or missing data.
- If labels are not appearing, verify that 'Add Picklist Labels' and 'Add Reference Labels' are enabled and that the fields have non-empty values.
- Flattening user-defined fields may cause naming conflicts if UDF names overlap with standard fields.
Links
- Autotask API Basic Query Calls - Official Autotask API documentation describing how to construct filter queries for advanced data retrieval.