Actions524
- AI Helper Actions
- Tool Actions
- API Threshold Actions
- Appointment Actions
- Billing Code Actions
- Billing Items Actions
- Change Request Link Actions
- Checklist Library Actions
- Checklist Library Item Actions
- Classification Icon Actions
- Company Actions
- Company Alert Actions
- Company Location Actions
- Company Note Actions
- Company Webhook Actions
- Company Site Configuration Actions
- Configuration Item Actions
- Configuration Item Billing Product Association 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
- 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
- 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
- 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
- Department Actions
- Project Phase Actions
- Quote Item Actions
- Quote Location Actions
- Quote Template Actions
- Resource Actions
- Resource Role Actions
- Resource Role Queue Actions
- Search Filter Actions
- Service Actions
- Service Call Actions
- Subscription Actions
- Subscription Period Actions
- Ticket Category Actions
- Ticket Category Field Default Actions
- Ticket History Actions
- Ticket Note Actions
Contract Service Bundle Unit → Get Many (Advanced)
AI-generatedOverview
This node operation retrieves multiple Contract Service Bundle Unit records from the Autotask PSA system using advanced filtering criteria. It is useful for scenarios where users need to query and extract detailed data about contract service bundle units based on complex conditions, such as filtering by specific fields or attributes. For example, a user might want to get all contract service bundle units that meet certain custom criteria for reporting or integration purposes.
Use Case Examples
- Retrieve all contract service bundle units with a specific status or attribute using a JSON filter.
- Fetch a limited number of contract service bundle units matching advanced search criteria for further processing or analysis.
Properties
| Name | Meaning |
|---|---|
| Get All | Whether to return all results or only up to a given limit. |
| Max Records | Maximum number of records to return when not returning all results (range 1-500). |
| Advanced Filter | A JSON string containing a "filter" array with Autotask API query criteria to specify complex search conditions. |
| Add Picklist Labels | Whether to automatically add "_label" fields for picklist fields with human-readable values (no labels added for empty values). |
| Add Reference Labels | Whether to automatically add "_label" fields for reference fields with human-readable values (no labels added for empty values). |
| Select Columns Names or IDs. | Choose which fields to include in the response. If no fields are selected, all fields will be returned. The ID field is always included regardless of selection. |
| Flatten User-Defined Fields | Whether to bring user-defined fields up to the top level of each object, making them accessible as top-level properties instead of nested in the userDefinedFields array. |
Output
JSON
id- Unique identifier of the contract service bundle unit record.name- Name or label of the contract service bundle unit.fields- Other selected fields of the contract service bundle unit as specified by the user in the select columns property._label- Human-readable labels for picklist or reference fields if enabled in the input properties.
Dependencies
- Autotask PSA REST API
- API key credential for authentication
Troubleshooting
- Ensure the advanced filter JSON is correctly formatted and matches the Autotask API query criteria syntax to avoid query errors.
- If the node returns no data, verify that the filter criteria actually match existing contract service bundle units in the Autotask system.
- Check API credentials and permissions to ensure the node can access contract service bundle unit data.
- If the maximum records limit is set too low, increase it or enable 'Get All' to retrieve more records.
Links
- Autotask PSA REST API Documentation - Official API documentation for Autotask PSA, useful for constructing advanced filters and understanding available fields.