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
The 'Contract Service - Get Many' operation in this node retrieves multiple contract service records from the Autotask REST API. It is useful for scenarios where users need to fetch a list of contract services, such as generating reports, synchronizing data, or displaying contract service information in bulk. For example, a user might want to get all contract services related to a specific contract or within a certain date range.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields of the contract service records to retrieve and map. Supports custom mapping and selection of specific fields. |
| Get All | Determines whether to return all matching contract service records or limit the number of records returned. |
| Max Records | Specifies the maximum number of contract service 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 output. |
| Add Reference Labels | If enabled, adds additional fields with '_label' suffix containing human-readable labels for reference fields in the output. |
| 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 brought to the top level of each object instead of being nested inside a userDefinedFields array. |
Output
JSON
id- Unique identifier of the contract service record.fields- Selected fields of the contract service as specified by the 'Fields' property.picklistField_label- Human-readable label for picklist fields if 'Add Picklist Labels' is enabled.referenceField_label- Human-readable label for reference fields if 'Add Reference Labels' is enabled.userDefinedFields- Array of user-defined fields unless 'Flatten User-Defined Fields' is enabled, in which case these fields appear at the top level.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- If no records are returned, verify that the query parameters and field mappings are correct.
- Ensure the API credentials are valid and have sufficient permissions to access contract service data.
- If the node returns an error about unsupported resource or operation, confirm that 'Contract Service' resource and 'Get Many' operation are selected.
- When selecting fields, if an invalid field ID is used, the API may reject the request or return incomplete data.
- If the maximum records limit is exceeded, reduce the 'Max Records' value or enable 'Get All' to fetch all records.