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 Retainer records from the Autotask system. It is useful for scenarios where users need to fetch a list of contract retainers, for example, to analyze contract data, generate reports, or synchronize contract information with other systems. The operation supports fetching all records or limiting the number of records returned, and allows customization of the fields included in the output.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields of the Contract Retainer resource to map and include in the output. Supports defining fields manually or using auto-mapping features. |
| Get All | Determines whether to return all Contract Retainer records or limit the results to a specified maximum number. |
| Max Records | Specifies the maximum number of Contract Retainer 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 human-readable labels for picklist fields in the output, improving readability. |
| Add Reference Labels | If enabled, adds additional fields with human-readable labels for reference fields in the output. |
| Select Columns Names or IDs. | Allows selection of specific fields to include in the response by choosing from a list or specifying field IDs via expressions. 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 brought to the top level of each returned object instead of being nested inside a userDefinedFields array, simplifying access to these fields. |
Output
JSON
id- Unique identifier of the Contract Retainer record.
- Each selected field from the Contract Retainer resource as specified by the 'Fields' and 'Select Columns' properties._label - Human-readable label for picklist or reference fields if 'Add Picklist Labels' or 'Add Reference Labels' is enabled.userDefinedFields- User-defined fields nested or flattened depending on 'Flatten User-Defined Fields' setting.
Dependencies
- Requires an authenticated connection to the Autotask REST API via an API key credential.
Troubleshooting
- If no records are returned, verify that the Contract Retainer resource contains data and that the selected fields are valid.
- If the node throws an error about unsupported resource or operation, ensure the resource is set to 'contractRetainer' and operation to 'getMany'.
- Errors related to API authentication indicate issues with the provided API key or credentials; verify and update credentials as needed.
- If the maximum records limit is exceeded, reduce the 'Max Records' value or enable 'Get All' to fetch all records in batches if supported.