Actions389
- Ticket History Actions
- Ticket Note Actions
- Ticket Note Webhook Actions
- Ticket Webhook Actions
- Time Entry Actions
- Resource Actions
- Resource Role Actions
- Role Actions
- Search Filter Actions
- Service Actions
- Service Call Actions
- Skill Actions
- Survey Actions
- Survey Results Actions
- Ticket Actions
- Invoice Actions
- Notification History Actions
- Opportunity Actions
- Product Actions
- Product Vendor Actions
- Project Actions
- Project Charge Actions
- Project Note Actions
- Project Phase Actions
- Project Task Actions
- Contract Retainer Actions
- Contract Service Actions
- Contract Service Adjustment Actions
- Contract Service Bundle Adjustment Actions
- Contract Service Bundle Actions
- Contract Service Bundle Unit Actions
- Contract Ticket Purchase Actions
- Contract Service Unit Actions
- Domain Registrar Actions
- Holiday Actions
- Holiday Set Actions
- Contract Exclusion Billing Code 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 Rate Actions
- Contract Role Costs Actions
- Contact Actions
- Contact Webhook Actions
- Contact Groups Actions
- Contact Group Contacts Actions
- Contract Actions
- Contract Block Actions
- Contract Block Hour Factor 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
- Billing Code Actions
- Company Actions
- Company Alert Actions
- Company Location Actions
- Company Note Actions
- Company Webhook Actions
- Configuration Item Actions
- Configuration Item Billing Product Association Actions
Contract Service Bundle → Get Many
AI-generatedOverview
The node interacts with the Autotask REST API to retrieve multiple records of Contract Service Bundles. It supports fetching either all available records or a limited number, with options to select specific fields, include human-readable labels for picklist and reference fields, and flatten user-defined fields for easier access. This is useful for users who need to bulk retrieve contract service bundle data for reporting, integration, or automation purposes within their workflows.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields of the Contract Service Bundle resource to retrieve and map in the output, allowing precise control over the data returned. |
| Get All | Determines whether to return all matching Contract Service Bundle records or limit the number of records returned. |
| Max Records | Specifies the maximum number of Contract Service Bundle records to return when 'Get All' is false, with a range from 1 to 500. |
| Add Picklist Labels | If enabled, adds additional fields with human-readable labels for picklist fields in the returned data, improving readability. |
| Add Reference Labels | If enabled, adds additional fields with human-readable labels for reference fields in the returned data, enhancing clarity. |
| Select Columns Names or IDs. | Allows selection of specific fields by name or ID to include in the response. If none are selected, all fields are returned by default. The ID field is always included. |
| Flatten User-Defined Fields | When enabled, user-defined fields (UDFs) are promoted to top-level properties in each returned object instead of being nested, simplifying data access. |
Output
JSON
id- Unique identifier of the Contract Service Bundle record.
- Fields of the Contract Service Bundle as specified by the 'Fields' property, including standard and user-defined fields._label - Human-readable labels for picklist or reference fields if 'Add Picklist Labels' or 'Add Reference Labels' are enabled.
Dependencies
- Requires an API key credential for authenticating with the Autotask REST API.
Troubleshooting
- If no records are returned, verify that the resource and operation parameters are correctly set to 'contractServiceBundle' and 'getMany'.
- Ensure the API credentials are valid and have sufficient permissions to access Contract Service Bundle data.
- If the node returns an error about unsupported resource, confirm that the resource name is exactly 'contractServiceBundle'.
- When selecting specific fields, ensure the field names or IDs are valid and exist in the Contract Service Bundle resource schema.
- If the maximum records limit is set too low, fewer records than expected will be returned; increase 'Max Records' or enable 'Get All' to retrieve more data.