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 Retainer → Get Many
AI-generatedOverview
This node operation retrieves multiple Contract Retainer records from the Autotask PSA system. It supports fetching all records or limiting the number of records returned, with options to include human-readable labels for picklist and reference fields, select specific columns, and flatten user-defined fields for easier access. This operation is useful for scenarios where users need to list or analyze multiple contract retainers, such as generating reports or syncing contract data with other systems.
Use Case Examples
- Fetch all contract retainers to synchronize with an external database.
- Retrieve a limited number of contract retainers with specific fields for a dashboard display.
- Get contract retainers with user-friendly labels for reporting purposes.
Properties
| Name | Meaning |
|---|---|
| Get All | Whether to return all results or only up to a given limit. |
| Max Records | Maximum number of contract retainer records to return when not returning all. |
| Add Picklist Labels | Whether to automatically add '_label' fields for picklist fields with human-readable values. |
| Add Reference Labels | Whether to automatically add '_label' fields for reference fields with human-readable values. |
| Select Columns Names or IDs. | Choose which fields to include in the response; if none selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | Whether to bring user-defined fields up to the top level of each object for easier access. |
| Fields | Mapping of fields to define or customize the data structure for the contract retainer resource. |
Output
JSON
id- Unique identifier of the contract retainer record.contractRetainerField1- Example field representing a property of the contract retainer (actual fields depend on API response).contractRetainerFieldN- Additional fields representing contract retainer properties as returned by the API.
Dependencies
- An API key credential for Autotask PSA REST API authentication.
Troubleshooting
- Common issues include authentication failures due to invalid or missing API credentials. Ensure the API key credential is correctly configured.
- Errors may occur if the resource or operation parameters are incorrect or unsupported; verify that 'Contract Retainer' resource and 'Get Many' operation are selected.
- If the API rate limit is exceeded, the node may fail; consider handling rate limits or retrying after some time.
Links
- Autotask PSA REST API Documentation - Official documentation for the Autotask PSA REST API, useful for understanding available endpoints and data structures.