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 Unit records from the Autotask system. It allows users to fetch a list of contract service units with options to specify which fields to return, limit the number of records, and include human-readable labels for picklist and reference fields. This is useful for scenarios where you need to analyze, report, or integrate contract service unit data from Autotask into workflows or other systems.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields of the Contract Service Unit resource to retrieve and map in the output. Supports custom mapping and selection of specific fields. |
| Get All | Determines whether to return all available Contract Service Unit records or limit the results to a specified maximum number. |
| Max Records | Specifies the maximum number of Contract Service Unit records to return when 'Get All' is false. The value must be between 1 and 500. |
| Add Picklist Labels | If enabled, adds additional fields with '_label' suffix containing human-readable labels for picklist fields in the returned data. |
| Add Reference Labels | If enabled, adds additional fields with '_label' suffix containing human-readable labels for reference fields in the returned data. |
| Select Columns Names or IDs. | Allows selection of specific fields (columns) to include in the response. If no fields are selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | When 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 Unit record.fields- Values of the selected fields for each Contract Service Unit record._label - Human-readable label for picklist fields if 'Add Picklist Labels' is enabled._label - Human-readable label for reference fields if 'Add Reference Labels' is enabled.userDefinedFields- User-defined fields nested inside userDefinedFields array, unless 'Flatten User-Defined Fields' is enabled.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- If no records are returned, verify that the resource and operation parameters are correctly set to 'contractServiceUnit' and 'getMany'.
- Ensure the API credentials are valid and have sufficient permissions to access Contract Service Unit data.
- If the node returns an error about unsupported resource, confirm that the resource name is exactly 'contractServiceUnit'.
- When selecting specific fields, ensure the field names or IDs are valid and exist in the Contract Service Unit resource schema.
- If the maximum records limit is exceeded, reduce the 'Max Records' value to 500 or less.
- If labels for picklist or reference fields are missing, check that the corresponding 'Add Picklist Labels' and 'Add Reference Labels' options are enabled.